DOCS-11071,DOCS-10943 relnotes cleanup and singlesource fcv=3.4 cleanup

Author: kay-kim

source/core/databases-and-collections.txt

@@ -118,10 +118,15 @@ Unique Identifiers
 
 .. versionadded:: 3.6
 
-Collections are assigned a :abbr:`UUID (Universally unique identifier)`
-upon creation. Once assigned, a collection's UUID does not change.
-The collection UUID remains the same across all members of a replica
-set and shards in a sharded cluster.
+.. note::
+
+   The ``featureCompatibilityVersion`` must be set to ``"3.6"``. For
+   more information, see :ref:`view-fcv`.
+
+Collections are assigned an immutable :abbr:`UUID (Universally unique
+identifier)`. The
+collection UUID remains the same across all members of a replica set
+and shards in a sharded cluster.
 
 To retrieve the UUID for a collection, run either the
 :manual:`listCollections </reference/command/listCollections>` command

source/includes/3.6-backwards-incompatible-features.rst

@@ -5,7 +5,7 @@ The following 3.6 features require that
 
 - :query:`$jsonSchema` document validation
 
-- Change Streams
+- :doc:`/changeStreams`
 
 - Chunk aware secondaries
 
@@ -14,4 +14,4 @@ The following 3.6 features require that
 
 - Sessions and retryable writes
 
-- Users with ``authenticationRestrictions``
+- Users and roles with :ref:`authenticationRestrictions <3.6-authentication-restrictions>`

source/includes/remove-3.6-fcv-features.rst

@@ -0,0 +1,5 @@
+Remove all persisted features that are :ref:`incompatible
+<3.6-compatibility-enabled>` with 3.4. For example, if you have defined
+any any view definitions, document validators, and partial index
+filters that use 3.6 query features such as :query:`$jsonSchema` or
+:query:`$expr`, you must remove them.

source/reference/command/setFeatureCompatibilityVersion.txt

@@ -194,11 +194,15 @@ to ``"3.4"`` on the MongoDB 3.6 deployment:
    - ``"3.4"`` featureCompatibilityVersion is supported on MongoDB
      3.6 and MongoDB 3.4 Deployments Only.
 
-
 .. code-block:: javascript
 
    db.adminCommand( { setFeatureCompatibilityVersion: "3.4" } )
 
+If run as part of the downgrade process from MongoDB 3.6 to MongoDB
+3.4, you must also remove all persisted features that are
+:ref:`incompatible <3.6-compatibility-enabled>` with 3.4. See the
+appropriate downgrade procedures.
+
 Set Feature Compatibility Version on MongoDB 3.4 Deployments
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~