diff --git a/docs/userguide/dockervolumes.md b/docs/userguide/dockervolumes.md
index af106cebb1..1302ed8170 100644
--- a/docs/userguide/dockervolumes.md
+++ b/docs/userguide/dockervolumes.md
@@ -260,7 +260,7 @@ elsewhere. Create a new container.
 
 Then un-tar the backup file in the new container's data volume.
 
-    $ docker run --volumes-from dbstore2 -v $(pwd):/backup ubuntu cd /dbdata && tar xvf /backup/backup.tar
+    $ docker run --volumes-from dbstore2 -v $(pwd):/backup ubuntu bash -c "cd /dbdata && tar xvf /backup/backup.tar"
 
 You can use the techniques above to automate backup, migration and
 restore testing using your preferred tools.
diff --git a/docs/userguide/networkingcontainers.md b/docs/userguide/networkingcontainers.md
index 3a44e3b1d0..0df3f6a7eb 100644
--- a/docs/userguide/networkingcontainers.md
+++ b/docs/userguide/networkingcontainers.md
@@ -218,7 +218,7 @@ After a bit, use CTRL-C to end the `ping` and you'll find the ping failed. That
 
 Docker networking allows you to attach a container to as many networks as you like. You can also attach an already running container. Go ahead and attach your running `web` app to the `my-bridge-network`.
 
-    $ docker network connect my-bridge-network Web
+    $ docker network connect my-bridge-network web
 
 Open a shell into the `db` application again and try the ping command. This time just use the container name `web` rather than the IP Address.