DOCSP-26900 Fixed wording around using the projection operator with arrays (#2358) (#4370)

* Fixed wording around using the projection operator with arrays

* Per internal review, cleaned up wording for consistency

* Fixed pluralization and table list rendering

* Incorporated internal review feedback

* Changed new paragraph back to bullet to address build issues

* Moved line up into preceding bullet to test build errors

* Testing output

* fixed indentation

Author: nvillahermosa-mdb

source/includes/extracts-projection.yaml

@@ -142,61 +142,63 @@ content: |
 
       * - ``<field>: <1 or true>``
 
-        - Specifies the inclusion of a field. Non-zero integers are also
-          treated as ``true``.
+        - Specifies the inclusion of a field. If you specify a non-zero 
+          integer for the projection value, the operation treats the 
+          value as ``true``.
 
       * - ``<field>: <0 or false>``
 
         - Specifies the exclusion of a field.
 
       * - ``"<field>.$": <1 or true>``
 
-        - With the use of the :projection:`$` array projection operator,
-          you can specify the projection to return the **first** element
-          that match the query condition on the array field; e.g.
-          ``"arrayField.$" : 1``. (Not available for :doc:`views
-          </core/views>`.)  Non-zero integers are also treated as 
-          ``true``.
+        - Uses the :projection:`$` array projection operator to return 
+          the first element that matches the query condition on the
+          array field. If you specify a non-zero integer for the 
+          projection value, the operation treats the value as ``true``. 
+          
+          Not available for :ref:`views <views-landing-page>`.
 
       * - ``<field>: <array projection>``
 
-        - Using the array projection operators :projection:`$elemMatch`,
-          :projection:`$slice`, specifies the array element(s) to include,
-          thereby excluding those elements that do not meet the
-          expressions. (Not available for :doc:`views </core/views>`.)
+        - Uses the array projection operators (:projection:`$elemMatch`,
+          :projection:`$slice`) to specify the array elements to
+          include. 
+          
+          Not available for :ref:`views <views-landing-page>`.
 
       * - ``<field>: <$meta expression>``
 
-        - Using the :expression:`$meta` operator expression, specifies the
-          inclusion of available :expression:`per-document metadata
-          <$meta>`. (Not available for :doc:`views </core/views>`.)
+        - Uses the :expression:`$meta` operator expression to specify 
+          the inclusion of available :expression:`per-document metadata
+          <$meta>`. 
+          
+          Not available for :ref:`views <views-landing-page>`.
 
 
       * - ``<field>: <aggregation expression>``
 
         - Specifies the value of the projected field.
 
           Starting in MongoDB 4.4, with the use of :ref:`aggregation
-          expressions and syntax <aggregation-expressions>`, including the
-          use of literals and aggregation variables, you can project new
-          fields or project existing fields with new values. For example,
+          expressions and syntax <aggregation-expressions>`, including
+          the use of literals and aggregation variables, you can project
+          new fields or project existing fields with new values.
        
           - If you specify a non-numeric, non-boolean literal (such as a
-            literal string or an array or an operator expression) for the
-            projection value, the field is projected with the new value;
-            e.g.:
+            literal string or an array or an operator expression) for
+            the projection value, the field is projected with the new
+            value, for example:
 
             - ``{ field: [ 1, 2, 3, "$someExistingField" ] }``
             - ``{ field: "New String Value" }``
             - ``{ field: { status: "Active", total: { $sum: "$existingArray" } } }``
 
-          - To project a literal value for a field, use the :expression:`$literal`
-            aggregation expression; e.g.:
+          - To project a literal value for a field, use the
+            :expression:`$literal` aggregation expression; for example:
 
             - ``{ field: { $literal: 5 } }``
-         
             - ``{ field: { $literal: true } }``
-
             - ``{ field: { $literal: { fieldWithValue0: 0, fieldWithValue1: 1 } } }`` 
             
           In versions 4.2 and earlier, any specification value (with
@@ -219,28 +221,30 @@ content: |
 
       * - ``<field>: <1 or true>``
 
-        - Specifies the inclusion of a field. Non-zero integers are also
-          treated as ``true``.
+        - Specifies the inclusion of a field. If you specify a non-zero 
+          integer for the projection value, the operation treats the 
+          value as ``true``.
 
       * - ``<field>: <0 or false>``
 
         - Specifies the exclusion of a field.
 
       * - ``"<field>.$": <1 or true>``
 
-        - With the use of the :projection:`$` array projection operator,
-          you can specify the projection to return the **first** element
-          that match the query condition on the array field; e.g.
-          ``"arrayField.$" : 1``. (Not available for :doc:`views
-          </core/views>`.) Non-zero integers are also treated as 
-          ``true``.
+        - Uses the :projection:`$` array projection operator to return 
+          the first element that matches the query condition on the
+          array field. If you specify a non-zero integer for the 
+          projection value, the operation treats the value as ``true``.
+          
+          Not available for :ref:`views <views-landing-page>`.
 
       * - ``<field>: <array projection>``
 
-        - Using the array projection operators :projection:`$elemMatch`,
-          :projection:`$slice`, specifies the array element(s) to include,
-          thereby excluding those elements that do not meet the
-          expressions. (Not available for :doc:`views </core/views>`.)
+        - Uses the array projection operators (:projection:`$elemMatch`,
+          :projection:`$slice`) to specify the array elements to
+          include. 
+          
+          Not available for :ref:`views <views-landing-page>`.
 
       * - ``<field>: <aggregation expression>``
 
@@ -249,24 +253,22 @@ content: |
           Starting in MongoDB 4.4, with the use of :ref:`aggregation
           expressions and syntax <aggregation-expressions>`, including the
           use of literals and aggregation variables, you can project new
-          fields or project existing fields with new values. For example,
+          fields or project existing fields with new values.
        
           - If you specify a non-numeric, non-boolean literal (such as a
-            literal string or an array or an operator expression) for the
-            projection value, the field is projected with the new value;
-            e.g.:
+            literal string or an array or an operator expression) for
+            the projection value, the field is projected with the new
+            value, for example:
 
             - ``{ field: [ 1, 2, 3, "$someExistingField" ] }``
             - ``{ field: "New String Value" }``
             - ``{ field: { status: "Active", total: { $sum: "$existingArray" } } }``
 
-          - To project a literal value for a field, use the :expression:`$literal`
-            aggregation expression; e.g.:
+          - To project a literal value for a field, use the
+            :expression:`$literal` aggregation expression, for example:
 
             - ``{ field: { $literal: 5 } }``
-         
             - ``{ field: { $literal: true } }``
-
             - ``{ field: { $literal: { fieldWithValue0: 0, fieldWithValue1: 1 } } }`` 
             
           In versions 4.2 and earlier, any specification value (with
@@ -282,9 +284,9 @@ content: |
    For fields in an embedded documents, you can specify the field using
    either:
 
-   - :ref:`dot notation <document-dot-notation-embedded-fields>`; e.g. ``"field.nestedfield": <value>``
+   - :ref:`dot notation <document-dot-notation-embedded-fields>`, for example ``"field.nestedfield": <value>``
 
-   - nested form; e.g. ``{ field: { nestedfield: <value> } }`` (*Starting in
+   - nested form, for example ``{ field: { nestedfield: <value> } }`` (*Starting in
      MongoDB 4.4*)
 
 ---
@@ -364,7 +366,7 @@ ref: projection-positional-operator-path
 content: |
 
    Starting in MongoDB 4.4, the :projection:`$` projection operator can
-   only appear at the end of the field path; e.g. ``"field.$"``
+   only appear at the end of the field path, for example ``"field.$"``
    or ``"fieldA.fieldB.$"``.
    
    For example, starting in MongoDB 4.4, the following operation is

source/reference/method/db.collection.find.txt

@@ -518,10 +518,9 @@ For a list of array specific query operators, see :ref:`operator-query-array`.
 Projections
 ~~~~~~~~~~~
 
-The :ref:`projection <find-projection>` parameter specifies
-which fields to return. The parameter contains either include or
-exclude specifications, not both, unless the exclude is for the ``_id``
-field.
+The :ref:`projection <find-projection>` parameter specifies which fields
+to return. The parameter contains either include or exclude
+specifications, not both, unless the exclude is for the ``_id`` field.
 
 .. note::
 
@@ -593,7 +592,7 @@ array:
       { _id: 0, 'name.last': 1, contribs: { $slice: 2 } } )
 
 Starting in MongoDB 4.4, you can also specify embedded fields using the
-nested form, e.g.
+nested form, for example:
 
 .. code-block:: javascript