Fix documentation flaw for "Forward" (#5078)

Closes #4973

Author: wesselkranenborg

docs/articles/actors/receive-actor-api.md

@@ -405,10 +405,10 @@ For more information on Tasks, check out the [MSDN documentation](https://msdn.m
 > When using task callbacks inside actors, you need to carefully avoid closing over the containing actor’s reference, i.e. do not call methods or access mutable state on the enclosing actor from within the callback. This would break the actor encapsulation and may introduce synchronization bugs and race conditions because the callback will be scheduled concurrently to the enclosing actor. Unfortunately there is not yet a way to detect these illegal accesses at compile time.
 
 ### Forward message
-You can forward a message from one actor to another. This means that the original sender address/reference is maintained even though the message is going through a 'mediator'. This can be useful when writing actors that work as routers, load-balancers, replicators etc. You need to pass along your context variable as well.
+You can forward a message from one actor to another. This means that the original sender address/reference is maintained even though the message is going through a 'mediator'. This can be useful when writing actors that work as routers, load-balancers, replicators etc.
 
 ```csharp
-target.Forward(result, Context);
+target.Forward(result);
 ```
 
 ## Receive messages