diff --git a/akka-docs/java/typed-actors.rst b/akka-docs/java/typed-actors.rst
index 8d5a13b8b2..9c4c3fb377 100644
--- a/akka-docs/java/typed-actors.rst
+++ b/akka-docs/java/typed-actors.rst
@@ -180,3 +180,9 @@ By having your Typed Actor implementation class implement any and all of the fol
     * ``TypedActor.PostRestart``
 
  You can hook into the lifecycle of your Typed Actor.
+
+ Proxying
+ --------
+
+ You can use the ``typedActorOf`` that takes a TypedProps and an ActorRef to proxy the given ActorRef as a TypedActor.
+ This is usable if you want to communicate remotely with TypedActors on otehr machines, just look them up with ``actorFor`` and pass the ``ActorRef`` to ``typedActorOf``.
diff --git a/akka-docs/scala/typed-actors.rst b/akka-docs/scala/typed-actors.rst
index 2d47063664..77d2ed24f7 100644
--- a/akka-docs/scala/typed-actors.rst
+++ b/akka-docs/scala/typed-actors.rst
@@ -181,6 +181,16 @@ all messages that are not ``MethodCall``s will be passed into the ``onReceive``-
 This allows you to react to DeathWatch ``Terminated``-messages and other types of messages,
 e.g. when interfacing with untyped actors.
 
+Proxying
+--------
+
+You can use the ``typedActorOf`` that takes a TypedProps and an ActorRef to proxy the given ActorRef as a TypedActor.
+This is usable if you want to communicate remotely with TypedActors on otehr machines, just look them up with ``actorFor`` and pass the ``ActorRef`` to ``typedActorOf``.
+
+.. note::
+
+  The ActorRef needs to accept ``MethodCall`` messages.
+
 Supercharging
 -------------