diff --git a/examples/tcp/README.md b/examples/tcp/README.md
index 97246c4e259430dc256bfb53f922bcd93ca9d946..3edfc0edcd7e5fd53190999a6e7c716706241d7c 100644
--- a/examples/tcp/README.md
+++ b/examples/tcp/README.md
@@ -9,5 +9,5 @@ Identifers in this implementation now behave slightly differently, reflecting th
 - `Connector` may have one or more open sockets with another `Connector` instance, each with a distinct source port number.
 
 When designing your distributed application, you may want to retain some form of unique label for each `Connector` instance on the network:
-- If you can be certain that only one instance of `Connector` is behind each IP address, perhaps on a local network such as Grid5000 (assuming each node has at most one connector) - the IP address with the port stripped out may be suitable for this purpose. 
-- Otherwise, you may want to define some messaging protocol on top of the interface yourself. For instance using public key cryptography to securely and consistently distinguish peers. 
\ No newline at end of file
+- If you can be certain that only one instance of `Connector` is behind each IP address, perhaps on a local network environment such as a Grid5000 cluster (assuming each node has at most one connector) - the IP address with the port stripped out may be suitable for this purpose. 
+- Otherwise, you may want to define some messaging protocol on top of the interface yourself. For instance, using public key cryptography to securely and consistently distinguish peers. 
\ No newline at end of file