DOCS-578: note about priority change causing election

Author: Sam Kleinman

source/reference/replica-configuration.txt

@@ -124,16 +124,18 @@ Configuration Variables
 
    **Default**: 1
 
-   Specify higher values to make a node *more* eligible to become
-   :term:`primary`, and lower values to make the node *less* eligible
+   Specify higher values to make a member *more* eligible to become
+   :term:`primary`, and lower values to make the member *less* eligible
    to become primary. Priorities are only used in comparison to each
-   other, members of the set will veto elections from nodes when
-   another eligible node has a higher absolute priority value.
+   other, members of the set will veto elections from members when
+   another eligible member has a higher absolute priority
+   value. Changing the balance of priority in a replica set will cause
+   an election.
 
    A :data:`members[n].priority` of ``0`` makes it impossible for a
-   node to become primary.
+   member to become primary.
 
-   .. seealso:: ":ref:`Replica Set Node Priority
+   .. seealso:: ":ref:`Replica Set Member Priority
       <replica-set-node-priority>`" and ":ref:`Replica Set Elections
       <replica-set-elections>`."
 
@@ -145,7 +147,7 @@ Configuration Variables
 
    **Default**: none
 
-   Used to represent arbitrary values for describing or tagging nodes
+   Used to represent arbitrary values for describing or tagging members
    for the purposes of extending :ref:`write concern
    <replica-set-write-concern>` to allow configurable data center
    awareness.
@@ -165,9 +167,9 @@ Configuration Variables
 
    Describes the number of seconds "behind" the master that this
    replica set member should "lag." Use this option to create
-   :ref:`delayed nodes <replica-set-delayed-members>`, that
+   :ref:`delayed members <replica-set-delayed-members>`, that
    maintain a copy of the data that reflects the state of the data set
-   some amount of time (specified in seconds.) Typically these nodes
+   some amount of time (specified in seconds.) Typically these members
    help protect against human error, and provide some measure
    of insurance against the unforeseen consequences of changes and
    updates.
@@ -364,7 +366,7 @@ use the following form:
 
    The :method:`rs.reconfig()` shell command can force the current
    primary to step down and causes an election in some
-   situations. When the primary node steps down, all clients will
+   situations. When the primary steps down, all clients will
    disconnect. This is by design. While this typically takes 10-20
    seconds, attempt to make these changes during scheduled maintenance
    periods.