diff --git a/docs/runtime/sync.md b/docs/runtime/sync.md
index 53c0cf191436a9ea30471918728bf2a2654a4b0a..dacbb9acb75486d71e8adf1e95bc7d36f9b7b698 100644
--- a/docs/runtime/sync.md
+++ b/docs/runtime/sync.md
@@ -126,4 +126,4 @@ Note that this broadcasting of synchronous messages is essentially a component-t
 
 These port mappings are also sent along when sending data messages. We will not go into details but here the mapping makes sure that messages arrive in the right order, and certain kinds of deadlock or inconsistent protocol behaviour may be detected. This port mapping is checked for consistency by the recipient and, when consistent, the target port is updated with its new mapping.
 
-As we'll send along this mapping we will only consider the ports that are shared between the two components. But in the most general case the transmitting ports of the component do not have knowledge about the peer component. And so the sent port mapping will have to contain the annotation for *all* transmitting ports. Receiving port mappings only have to be sent along if they received a message, and here we can indeed apply filtering.
\ No newline at end of file
+As we'll send along this mapping we will only consider the ports that are shared between the two components. But in the most general case the transmitting ports of the component do not have knowledge about the peer component. And so the sent port mapping will have to contain the annotation for *all* transmitting ports. Receiving port mappings only have to be sent along if they received a message, and here we can indeed apply filtering. Likewise, if the recipient of a port mapping has not yet received anything on its receiving port, then it cannot be sure about the identity of the sender.
\ No newline at end of file