DOCS-15521 sh.status.partitioned not valid (#2050)

* DOCS-15521 sh.status.partitioned not valid

* DOCS-15521 sh.status.partitioned not valid

* DOCS-15521 sh.status.partitioned not valid

* Review Feedback

* Review feedback

Author: Dave Cuthbert

source/includes/steps-reshard-a-collection.yaml

@@ -122,7 +122,7 @@ content: |
            database: {
            _id: '<database>',
            primary: '<shard>',
-           partitioned: true,
+           partitioned: false,
            version: {
              uuid: <uuid>,
              timestamp: <timestamp>,

source/reference/method/sh.status.txt

@@ -140,9 +140,8 @@ unbalanced sharded cluster.
                 1 : Failed with error 'aborted', from shardA to shardB
 
 The :ref:`sharding-status-databases-fields` section lists information
-on the database(s). For each database, the section displays the name,
-whether the database has sharding enabled, and the :term:`primary
-shard` for the database.
+on the database(s). It displays the database name and the :term:`primary
+shard` for each database.
 
 .. code-block:: javascript
 
@@ -335,9 +334,10 @@ Databases
 
 .. data:: sh.status.databases.partitioned
 
-   The :data:`~sh.status.databases.partitioned` displays whether
-   the database has sharding enabled. If ``true``, the database has
-   sharding enabled.
+   Starting in MongoDB 6.0 and :ref:`feature compatibility version (FCV)
+   <view-fcv>` 6.0, the ``partitioned`` flag only maintains backward
+   compatibility with previous versions. By default, all databases are
+   enabled for sharding regardless of the ``partitioned`` value.
 
 .. data:: sh.status.databases.primary