diff --git a/akka-docs/rst/java/remoting.rst b/akka-docs/rst/java/remoting.rst
index 5d50eae453..7fb1cbc8e4 100644
--- a/akka-docs/rst/java/remoting.rst
+++ b/akka-docs/rst/java/remoting.rst
@@ -88,6 +88,17 @@ the :class:`ActorSelection`, which returns a ``Future`` of the matching
 
   For more details on how actor addresses and paths are formed and used, please refer to :ref:`addressing`.
 
+.. note::
+
+  Message sends to actors that are actually in the sending actor system do not
+  get delivered via the remote actor ref provider. They're delivered directly,
+  by the local actor ref provider.
+
+  Aside from providing better performance, this also means that if the hostname
+  you configure remoting to listen as cannot actually be resolved from within
+  the very same actor system, such messages will (perhaps counterintuitively)
+  be delivered just fine.
+
 Creating Actors Remotely
 ^^^^^^^^^^^^^^^^^^^^^^^^
 
@@ -247,7 +258,7 @@ Serialization
 When using remoting for actors you must ensure that the ``props`` and ``messages`` used for
 those actors are serializable. Failing to do so will cause the system to behave in an unintended way.
 
-For more information please see :ref:`serialization-java`
+For more information please see :ref:`serialization-java`.
 
 Routers with Remote Destinations
 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
@@ -495,4 +506,4 @@ special configuration that sets both the logical and the bind pairs for remoting
         bind-port = 2552              # internal (bind) port
       }
    }
-  }
\ No newline at end of file
+  }
diff --git a/akka-docs/rst/scala/remoting.rst b/akka-docs/rst/scala/remoting.rst
index 12c5c9a916..ea9e449dc9 100644
--- a/akka-docs/rst/scala/remoting.rst
+++ b/akka-docs/rst/scala/remoting.rst
@@ -94,6 +94,17 @@ the :class:`ActorSelection`, which returns a ``Future`` of the matching
 
   For more details on how actor addresses and paths are formed and used, please refer to :ref:`addressing`.
 
+.. note::
+
+  Message sends to actors that are actually in the sending actor system do not
+  get delivered via the remote actor ref provider. They're delivered directly,
+  by the local actor ref provider.
+
+  Aside from providing better performance, this also means that if the hostname
+  you configure remoting to listen as cannot actually be resolved from within
+  the very same actor system, such messages will (perhaps counterintuitively)
+  be delivered just fine.
+
 Creating Actors Remotely
 ^^^^^^^^^^^^^^^^^^^^^^^^
 
@@ -252,7 +263,7 @@ Serialization
 When using remoting for actors you must ensure that the ``props`` and ``messages`` used for
 those actors are serializable. Failing to do so will cause the system to behave in an unintended way.
 
-For more information please see :ref:`serialization-scala`
+For more information please see :ref:`serialization-scala`.
 
 Routers with Remote Destinations
 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^