docs update

docs/server.rst

@@ -1096,17 +1096,17 @@ For a production deployment there are a few recommendations to keep your
 application secure.
 
 First of all, the message queue should never be listening on a public network
-interface, to ensure that external clients never connect to it. The use of a
+interface, to ensure that external clients never connect to it. For a single
-private network (VPC), where the communication between servers can happen
+node deployment, the queue should only listen on `localhost`. For a multi-node
-privately is highly recommended.
+system the use of a private network (VPC), where the communication between
-
+servers can happen privately is highly recommended.
-In addition, all message queues support authentication and encryption.
+
-Authentication ensures that only the Socket.IO servers and related processes
+In addition, all message queues support authentication and encryption, which
-have access, while encryption prevents data to be collected by a third-party
+can strenthen the security of the deployment. Authentication ensures that only
-listening on the network.
+the Socket.IO servers and related processes have access, while encryption
-
+prevents data from being collected by a third-party that is listening on the
-Access credentials can be included in the connection URLs that are passed to the
+network. Access credentials can be included in the connection URLs that are
-client managers.
+passed to the client managers.
 
 Horizontal Scaling
 ~~~~~~~~~~~~~~~~~~