diff --git a/components/engine/docs/sources/examples/example_header.inc b/components/engine/docs/sources/examples/example_header.inc
index 607421fc13..7d0feddeb9 100644
--- a/components/engine/docs/sources/examples/example_header.inc
+++ b/components/engine/docs/sources/examples/example_header.inc
@@ -2,3 +2,9 @@
 .. note::
     
     This example assumes you have Docker running in daemon mode. For more information please see :ref:`running_examples`
+
+.. note::
+
+   These examples use ``sudo`` before each ``docker`` command you could also
+   add your current ``<username>`` to docker's group and get rid of ``sudo``.
+   You just need to type: ``$ sudo usermod -a -G docker <username>``
diff --git a/components/engine/docs/sources/examples/running_ssh_service.rst b/components/engine/docs/sources/examples/running_ssh_service.rst
index e0d406bc0e..59a80fbf6e 100644
--- a/components/engine/docs/sources/examples/running_ssh_service.rst
+++ b/components/engine/docs/sources/examples/running_ssh_service.rst
@@ -21,8 +21,7 @@ smooth, but gives you a good idea.
    daemon is unprotected and available via a TCP port. When you run
    through the same steps in a newer version of Docker, you will
    need to add ``sudo`` in front of each ``docker`` command in order
-   to reach the daemon over its protected Unix socket or you can add
-   your user to docker's group: ``sudo usermod -a -G docker <user>``.
+   to reach the daemon over its protected Unix socket.
 
 .. raw:: html