Docs: Use fully qualified node names. Closes #3234

docs/userguide/monitoring.rst

@@ -198,9 +198,9 @@ You can specify a single, or a list of workers by using the
 
 .. code-block:: console
 
-    $ celery -A proj inspect -d w1,w2 reserved
+    $ celery -A proj inspect -d w1@e.com,w2@e.com reserved
 
-    $ celery -A proj control -d w1,w2 enable_events
+    $ celery -A proj control -d w1@e.com,w2@e.com enable_events
 
 
 .. _monitoring-flower:

docs/userguide/workers.rst

@@ -601,7 +601,7 @@ If you want to specify a specific worker you can use the
 
 .. code-block:: console
 
-    $ celery -A proj control add_consumer foo -d worker1.local
+    $ celery -A proj control add_consumer foo -d celery@worker1.local
 
 The same can be accomplished dynamically using the :meth:`@control.add_consumer` method:
 
@@ -654,7 +654,7 @@ used to specify a worker, or a list of workers, to act on the command:
 
 .. code-block:: console
 
-    $ celery -A proj control cancel_consumer foo -d worker1.local
+    $ celery -A proj control cancel_consumer foo -d celery@worker1.local
 
 
 You can also cancel consumers programmatically using the
@@ -684,7 +684,7 @@ to specify which workers should reply to the request:
 
 .. code-block:: console
 
-    $ celery -A proj inspect active_queues -d worker1.local
+    $ celery -A proj inspect active_queues -d celery@worker1.local
     [...]