diff --git a/docs/how-tos/run-custom-commands.md b/docs/how-tos/run-custom-commands.md
index 9afa3c4..d44eb96 100644
--- a/docs/how-tos/run-custom-commands.md
+++ b/docs/how-tos/run-custom-commands.md
@@ -16,6 +16,10 @@ Such commands are defined by specifying the command in a `docker-volume-backup.[
 - `copy` (the tar archive is copied to all configured storages)
 - `prune` (existing backups are pruned based on the defined ruleset - optional)
 
+{: .note }
+So that the `docker-volume-backup` container can access the labels on other containers, it is necessary that the docker socket is mounted into
+the `docker-volume-backup` container as shown in the Quickstart example.
+
 Taking a database dump using `mysqldump` would look like this:
 
 ```yml
@@ -38,7 +42,9 @@ volumes:
 Due to Docker limitations, you currently cannot use any kind of redirection in these commands unless you pass the command to `/bin/sh -c` or similar.
 I.e. instead of using `echo "ok" > ok.txt` you will need to use `/bin/sh -c 'echo "ok" > ok.txt'`.
 
-If you need fine grained control about which container's commands are run, you can use the `EXEC_LABEL` configuration on your `docker-volume-backup` container:
+If you have more than one `docker-volume-backup` container (possibly across several docker-compose environments) to backup or you are using
+multiple backup schedules, you will need to use `EXEC_LABEL` in the configuration and a `docker-volume-backup.exec-label` label on each
+container using custom commands to ensure that the commands are only run by the correct `docker-volume-backup` instance.
 
 ```yml
 version: '3'
diff --git a/docs/index.md b/docs/index.md
index 4c878fc..90c43c0 100644
--- a/docs/index.md
+++ b/docs/index.md
@@ -57,9 +57,11 @@ services:
     volumes:
       - data:/backup/my-app-backup:ro
       # Mounting the Docker socket allows the script to stop and restart
-      # the container during backup. You can omit this if you don't want
-      # to stop the container. In case you need to proxy the socket, you can
-      # also provide a location by setting `DOCKER_HOST` in the container
+      # the container during backup and to access the container labels to
+      # specify custom commands. You can omit this if you don't want to
+      # stop the container or run custom commands. In case you need to
+      # proxy the socket, you can also provide a location by setting
+      # `DOCKER_HOST` in the container
       - /var/run/docker.sock:/var/run/docker.sock:ro
       # If you mount a local directory or volume to `/archive` a local
       # copy of the backup will be stored there. You can override the