DOCS-14655 correct newlyAdded downgrade step

Author: andf-mongodb

source/release-notes/5.0-downgrade-replica-set.txt

@@ -96,8 +96,15 @@ First, verify the following:
 
 - Ensure that no nodes have a ``newlyAdded`` field in their
   :doc:`replica set configuration </reference/replica-configuration>`.
-  Use the :method:`rs.conf()` method on each node in your replica set to
-  verify this. The ``newlyAdded`` only appears in a node's replica set
+  Run the following command on each node in your replica set to
+  verify this:
+
+  .. code-block:: javascript
+
+     use local
+     db.system.replset.find( { "members.newlyAdded" : { $exists : true } } );
+  
+  The ``newlyAdded`` field only appears in a node's replica set
   configuration document during and shortly after an initial sync.
 
 - Ensure that no replica set member is in :replstate:`ROLLBACK` or

source/release-notes/5.0-downgrade-sharded-cluster.txt

@@ -103,10 +103,16 @@ First, verify the following:
 
 - Ensure that no nodes have a ``newlyAdded`` field in their
   :doc:`replica set configuration </reference/replica-configuration>`.
-  Use the :method:`rs.conf()` method on each node in your sharded
-  cluster to verify this. The ``newlyAdded`` only appears in a node's
-  replica set configuration document during and shortly after an initial
-  sync.
+  Run the following command on each node in your sharded cluster to
+  verify this:
+
+  .. code-block:: javascript
+
+     use local
+     db.system.replset.find( { "members.newlyAdded" : { $exists : true } } );
+  
+  The ``newlyAdded`` field only appears in a node's replica set
+  configuration document during and shortly after an initial sync.
 
 - Ensure that no replica set member is in :replstate:`ROLLBACK` or
   :replstate:`RECOVERING` state.