DOCSP-51973-write-concern-default-value (#12952) (#12976)

* DOCSP-51973-write-concern-default-value

* suggestion

* no monospace

Author: gmiller-mdb

content/manual/manual/source/includes/5.0-default-wc.rst

@@ -1,7 +1,7 @@
 Starting in MongoDB 5.0, the implicit default
 :ref:`write concern <write-concern>` is
-:writeconcern:`w: majority <"majority">`. However, special
-considerations are made for deployments containing
+:writeconcern:`w: majority <"majority">`. However, there is an edge case for 
+replica set deployments containing
 :ref:`arbiters <replica-set-arbiter-configuration>`:
 
 - The voting majority of a replica set is 1 plus half the number of

content/manual/manual/source/reference/write-concern.txt

@@ -34,8 +34,8 @@ instances will pass the write concern on to the shards.
 
 Replica sets and sharded clusters support setting a global default write 
 concern. Operations which do not specify an explicit write concern inherit the 
-global default write concern settings. See :dbcommand:`setDefaultRWConcern` for 
-more information.
+global default write concern settings. The default global write concern is 
+majority. See :dbcommand:`setDefaultRWConcern` for more information.
 
 To learn more about setting the write concern for deployments
 hosted in {+atlas+}, see 

content/manual/rapid/source/includes/5.0-default-wc.rst

@@ -1,7 +1,7 @@
 Starting in MongoDB 5.0, the implicit default
 :ref:`write concern <write-concern>` is
-:writeconcern:`w: majority <"majority">`. However, special
-considerations are made for deployments containing
+:writeconcern:`w: majority <"majority">`. However, there is an edge case for 
+replica set deployments containing
 :ref:`arbiters <replica-set-arbiter-configuration>`:
 
 - The voting majority of a replica set is 1 plus half the number of

content/manual/rapid/source/reference/write-concern.txt

@@ -34,8 +34,8 @@ instances will pass the write concern on to the shards.
 
 Replica sets and sharded clusters support setting a global default write 
 concern. Operations which do not specify an explicit write concern inherit the 
-global default write concern settings. See :dbcommand:`setDefaultRWConcern` for 
-more information.
+global default write concern settings. The default global write concern is 
+majority. See :dbcommand:`setDefaultRWConcern` for more information.
 
 To learn more about setting the write concern for deployments
 hosted in {+atlas+}, see 

content/manual/v6.0/source/includes/5.0-default-wc.rst

@@ -1,7 +1,7 @@
 Starting in MongoDB 5.0, the implicit default
 :ref:`write concern <write-concern>` is
-:writeconcern:`w: majority <"majority">`. However, special
-considerations are made for deployments containing
+:writeconcern:`w: majority <"majority">`. However, there is an edge case for 
+replica set deployments containing
 :ref:`arbiters <replica-set-arbiter-configuration>`:
 
 - The voting majority of a replica set is 1 plus half the number of

content/manual/v6.0/source/reference/write-concern.txt

@@ -34,8 +34,8 @@ instances will pass the write concern on to the shards.
 
 Replica sets and sharded clusters support setting a global default write 
 concern. Operations which do not specify an explicit write concern inherit the 
-global default write concern settings. See :dbcommand:`setDefaultRWConcern` for 
-more information.
+global default write concern settings. The default global write concern is 
+majority. See :dbcommand:`setDefaultRWConcern` for more information.
 
 To learn more about setting the write concern for deployments
 hosted in {+atlas+}, see 

content/manual/v7.0/source/includes/5.0-default-wc.rst

@@ -1,7 +1,7 @@
 Starting in MongoDB 5.0, the implicit default
 :ref:`write concern <write-concern>` is
-:writeconcern:`w: majority <"majority">`. However, special
-considerations are made for deployments containing
+:writeconcern:`w: majority <"majority">`. However, there is an edge case for 
+replica set deployments containing
 :ref:`arbiters <replica-set-arbiter-configuration>`:
 
 - The voting majority of a replica set is 1 plus half the number of

content/manual/v7.0/source/reference/write-concern.txt

@@ -34,8 +34,8 @@ instances will pass the write concern on to the shards.
 
 Replica sets and sharded clusters support setting a global default write 
 concern. Operations which do not specify an explicit write concern inherit the 
-global default write concern settings. See :dbcommand:`setDefaultRWConcern` for 
-more information.
+global default write concern settings. The default global write concern is 
+majority. See :dbcommand:`setDefaultRWConcern` for more information.
 
 To learn more about setting the write concern for deployments
 hosted in {+atlas+}, see