DOCSP-28118 STARTUP2 Nodes Not in Voting Majority (#2592) (#2601)

* DOCSP-28118 STARTUP2 Nodes Not in Voting Majority

* fix typo

* move in release notes

* JD edits

* move see also note

* move to compatibility changes and include prior version info

Author: ajhuh-mdb

source/includes/replica-states.rst

@@ -38,14 +38,8 @@
 
    * - 5
      - :replstate:`STARTUP2`
-     - The member has joined the set and is running an initial sync.
-       Eligible to vote.
-
-       .. note::
-
-          Starting in MongoDB 5.0, if the member was newly added to the
-          replica set, it is not eligible to vote and cannot be elected
-          during the initial sync process.
+     - The member has joined the set and is running an initial sync. Not 
+       eligible to vote.
 
    * - 6
      - :replstate:`UNKNOWN`

source/reference/replica-states.txt

@@ -52,21 +52,20 @@ Other States
 
 .. replstate:: STARTUP2
 
+   .. versionchanged:: 5.0
+
    Each data-bearing member of a replica set enters the
    :replstate:`STARTUP2` state as soon as :binary:`~bin.mongod` finishes
-   loading that member's configuration, at which time it becomes an
-   active member of the replica set and is eligible to vote.
+   loading that member's configuration. 
 
    The member then decides whether or not to undertake an initial sync.
    If a member begins an initial sync, the member remains in
    :replstate:`STARTUP2` until all data is copied and all indexes are
    built. Afterwards, the member transitions to :replstate:`RECOVERING`.
 
-   .. note::
-
-      Starting in MongoDB 5.0, if the member was newly added to the
-      replica set, it is not eligible to vote and cannot be elected
-      during the initial sync process.
+   Newly-added members in :replstate:`STARTUP2` are not eligible to vote and 
+   cannot be elected during the initial sync process. Prior to MongoDB 5.0, 
+   members in :replstate:`STARTUP2` were eligible to vote. 
 
 .. replstate:: RECOVERING
 

source/reference/write-concern.txt

@@ -401,7 +401,7 @@ For details, see :ref:`causal-consistency`.
   - Delayed secondaries can return write acknowledgment no earlier
     than the configured :rsconf:`~members[n].secondaryDelaySecs`. 
 
-- Starting in MongoDB 4.4, replica set members in the
+- Starting in MongoDB 5.0, replica set members in the
   :replstate:`STARTUP2` state do not participate in write majorities.
 
 Write Concern not Supported on ``local`` Database

source/release-notes/4.4.txt

@@ -884,16 +884,6 @@ or
 
    db.serverStatus( { mirroredReads: 1 } )
 
-Replica Set Write Acknowledgement
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-
-Starting in MongoDB 4.4, replica set members in the
-:replstate:`STARTUP2` state do not participate in write majorities.
-
-.. seealso::
-
-   :doc:`/core/replica-set-write-concern`
-
 Sharded Clusters
 ----------------
 

source/release-notes/5.0-compatibility.txt

@@ -218,6 +218,16 @@ Removed Customizable Values For getLastErrorDefaults
 
 .. include:: /includes/5.0-changes-getLastErrorDefaults-removed.rst
 
+Replica Set Write Acknowledgement
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+Starting in MongoDB 5.0, replica set members in the
+:replstate:`STARTUP2` state do not participate in write majorities.
+
+.. seealso::
+
+   :ref:`replica-set-write-concern`
+
 
 Read Concern ``snapshot`` on Capped Collections
 -----------------------------------------------