edits

Author: Bob Grabar

source/core/replication.txt

@@ -164,11 +164,27 @@ participate in :term:`elections <election>`.
    Do not run arbiter processes on a system that is an active
    :term:`primary` or :term:`secondary` of its replica set.
 
-You must run arbiters only on secure networks. While arbiters do not
-hold database content, they do hold replica-set configuration data,
-which always should be protected. Arbiters use encryption only when
-creating a connection with another replica-set member. All other
-communications are unencrypted.
+Arbiters make the following communications:
+
+- Exchange keyfiles with replica set. Arbiters
+  replica set servers exchange keyfiles, which are the equivalent of a
+  password for the __system "user".
+
+- The arbiter is authenticated when a connection is created between it
+  and another member of the replica set, and is then trusted until the
+  connection ends.
+
+- Only the authentication step is encrypted. Replica set configuration
+  data and voting are unencrypted.
+
+- Data other than the authentication step are not encrypted.
+
+
+
+
+
+
+
 
 You should always run arbiters on secure networks.