adding in information from the wiki

Author: Andrew Leung

source/administration/replication-architectures.txt

@@ -132,10 +132,10 @@ for these kinds of nodes:
   <replica-set-hidden-members>`.)
 
 - **Voting**: This changes the number of votes that a member of the
-  set node has in elections for primary. In general use priority to
+  replica set has in elections. In general, use priority to
   control the outcome of elections, as weighting votes introduces
-  operational complexities and risks set failure. Only modify the
-  number of votes, if you need to have more than 7 members of a
+  operational complexities and risks. Only modify the
+  number of votes when you need to have more than 7 members in a
   replica set. (:ref:`see also <replica-set-non-voting-members>`.)
 
 .. note::

source/core/replication-internals.txt

@@ -115,7 +115,7 @@ modify the configuration of an existing replica set.
 Elections
 ---------
 
-When you initialize a replica set for the first time, and when any
+When you initialize a replica set for the first time, or when any
 failover occurs, an election takes place to decide which member should
 become :term:`primary`. A primary is the only member in the replica
 set that can accept write commands such as :func:`insert()
@@ -126,7 +126,7 @@ Elections are the process replica set members use to
 select the primary in a cluster. Elections follow two events:
 a primary that "steps down" or a :term:`secondary` that
 loses contact with a :term:`primary` member. All members have one vote
-in an election, and every :program:`mongod` can veto an election. A
+in an election, and any :program:`mongod` can veto an election. A
 single veto will invalidate the election.
 
 An existing primary will step down in response to the
@@ -183,8 +183,10 @@ aware of the following conditions and possible situations:
 
   .. note::
 
-     The only exception is that members with a priority of ``0`` cannot
-     become :term:`primary` and will not seek election.
+     The only exception is that members with a priority of ``0``
+     cannot become :term:`primary` and will not seek election. See
+     :ref:`replica-set-node-priority-configuration` for more
+     information.
 
 - Replica set members cannot become primary *unless* they have the
   highest "optime" of any visible members in the set.
@@ -194,23 +196,11 @@ aware of the following conditions and possible situations:
   :term:`primary` until the member with the highest priority catches up
   to the latest operation.
 
-Each member in a replica set has only one vote, by default. You may
-change the number of votes each member has to allow for larger replica
-sets. Each replica set is limited to 12 total members with 7 voting
-members.
 
-- The number of votes is modifiable in the :data:`replica set configuration <members[n].votes>`
-
-- The number of votes each member has can be any non-negative integer,
-  but it is highly recommended each member has 1 or 0 votes.
-
-- To select a member to be a "preferred primary", modify the member's
-  :ref:`priority value <replica-set-node-priority-configuration>`
-  instead of adjusting the number of votes the member has.
-
-.. TODO verify this. what should one do when >7 members are in a set?
-- When there are more than seven members in a replica set, adjust the
-  number of votes for each active member.
+.. seealso:: ":ref:`Non-voting members in a replica
+             set<replica-set-non-voting-members>`",
+             ":ref:`replica-set-node-priority-configuration`",
+             ":data:`replica configuration <members[n].votes>`
 
 Syncing
 -------

source/core/replication.txt

@@ -170,11 +170,11 @@ participate in :term:`elections <election>`.
 Non-Voting
 ~~~~~~~~~~
 
-You may choose to change the number of votes that each node has in
+You may choose to change the number of votes that each member has in
 :term:`elections <election>` for :term:`primary`. In general, all
-nodes should have only 1 vote to prevent intermittent ties, deadlock,
+members should have only 1 vote to prevent intermittent ties, deadlock,
 or the wrong nodes from becoming :term:`primary`. Use ":ref:`replica
-set priorities <replica-set-node-priority>`" to control which nodes
+set priorities <replica-set-node-priority>`" to control which members
 are more likely to become primary.
 
 .. index:: pair: replica set; failover
@@ -247,8 +247,6 @@ have a single vote in :ref:`elections <replica-set-elections>`.
    :data:`members[n].votes` except to permit more than 7 secondary
    nodes.
 
-.. COMMENT a bit unclear. ALWAYS set, but except to have more than 7 secondary?
-
 .. seealso:: ":ref:`Node Priority Configuration <replica-set-node-priority-configuration>`"
 
 .. index:: pair: replica set; consistency

source/reference/replica-configuration.txt

@@ -174,9 +174,12 @@ Configuration Variables
    **Default**: 1
 
    Controls the number of votes a server has in a :ref:`replica set
-   election <replica-set-elections>`. If you need more than 7 nodes,
-   use this setting to add additional non-voting nodes with a
-   :data:`members[n].votes` value of ``0``.
+   election <replica-set-elections>`. The number of votes each member
+   has can be any non-negative integer, but it is highly recommended
+   each member has 1 or 0 votes.
+
+   If you need more than 7 nodes, use this setting to add additional
+   non-voting nodes with a :data:`members[n].votes` value of ``0``.
 
    For most deployments and most members, use the default value,
    ``1``, for :data:`members[n].votes`.

source/tutorial/expand-replica-set.txt

@@ -126,4 +126,13 @@ Production Notes
     :term:`primary` member's :term:`oplog`. The new secondary must be
     able to become current using operations from the primary's oplog.
 
+- There is a maximum of seven :ref:`voting members
+  <replica-set-election-internals>` in any replica set. When adding
+  more members to a replica set that already has seven votes, you must
+  either:
 
+  - add the new member as a :ref:`non-voting members <replica-set-non-voting-members>`.
+
+  - remove votes from an :data:`existing member <members[n].priority>`
+
+  .. seealso:: :data:`Modifying member votes <members[n].votes>`