(DOCSP-46385 ) Fix short titles in Atlas (#7248)

* (DOCSP-46385 ) Fix short titles in Atlas
* Undo the change in one file per Sarah L
* copy review
* Added Operator to the compound titles, to be continued
* Fix side TOC to have single words

Author: JuliaMongo

source/atlas-search/accuracy.txt

@@ -140,7 +140,7 @@ To build your query to return optimal results:
   :pipeline:`$searchMeta` if you want to only retrieve metadata. To
   learn more, see :ref:`query-syntax-ref`.
 - Choose an operator that is optimal for retrieving the relevant
-  results. For example, consider :ref:`compound-ref` if you want to
+  results. For example, consider the :ref:`compound operator <compound-ref>` if you want to
   combine multiple clauses such as ``must``, ``should``, ``mustnot`` in
   you query. To learn more, see :ref:`operators-ref`.
 - Apply more processes on your search results by using |fts|

source/atlas-search/aggregation-stages/search.txt

@@ -120,7 +120,7 @@ The ``$search`` stage takes a document with the following fields:
      - Name of the :ref:`operator <operators-ref>` to search with. You 
        can provide a document that contains the operator-specific 
        options as the value for this field. Either this or 
-       ``<collector-name>`` is required. Use the :ref:`compound-ref`
+       ``<collector-name>`` is required. Use the :ref:`compound <compound-ref>`
        operator to run a compound query with multiple operators. 
 
    * - ``returnStoredSource``

source/atlas-search/autocomplete.txt

@@ -4,9 +4,9 @@
 
 .. _autocomplete-ref:
 
-============
-autocomplete
-============
+==========================
+``autocomplete`` Operator
+==========================
 
 .. default-domain:: mongodb
 
@@ -211,7 +211,7 @@ exact matches higher, try the following workaround:
    field is also indexed as a ``string``, thereby increasing the score 
    of exact matches.
 
-#. Query using the :ref:`compound-ref` operator.
+#. Query using the :ref:`compound operator <compound-ref>`.
 
 For a demonstration of this workaround, see 
 :ref:`autocomplete-compound`.

source/atlas-search/compound.txt

@@ -1,8 +1,8 @@
 .. _compound-ref:
 
-========
-compound
-========
+=======================
+``compound`` Operator
+=======================
 
 .. default-domain:: mongodb
 
@@ -157,7 +157,7 @@ You can use any of the clauses with any top-level operator, such as
 :ref:`span <span-ref>`, to specify query criteria. 
 
 To optimize performance, place non-scoring operators such as 
-:ref:`equals-ref`, :ref:`range-ref`, and :ref:`in-ref` in the
+:ref:`equals-ref`, :ref:`range-ref`, and :ref:`in <in-ref>` in the
 :data:`filter` clause to avoid unnecessary scoring operations. If you
 want to run multiple operations that must be evaluated as an ``OR``
 condition, nest a :data:`should` clause within the top-level

source/atlas-search/customize-score.txt

@@ -65,7 +65,7 @@ Example Queries
 .. tabs-selector:: drivers
 
 The sample queries demonstrate how to boost or bury the documents in the
-results. They use the :ref:`compound-ref` operator to combine two or more 
+results. They use the :ref:`compound operator <compound-ref>` to combine two or more 
 operators into a single query. 
 
 ----------

source/atlas-search/define-field-mappings.txt

@@ -204,14 +204,14 @@ query the field value.
      - :ref:`boolean <boolean-ref>`
      - ✓
      - | :ref:`equals <equals-ref>`
-       | :ref:`in-ref`
+       | :ref:`in <in-ref>`
 
    * - Date
      - :ref:`date <bson-data-types-date>`
      - ✓ 
      - | :ref:`equals <equals-ref>`
        | :ref:`facet <fts-facet-ref>`
-       | :ref:`in-ref`
+       | :ref:`in <in-ref>`
        | :ref:`near <near-ref>`
        | :ref:`range <range-ref>`
 
@@ -224,7 +224,7 @@ query the field value.
      - :ref:`number <bson-data-types-number>`
      - ✓ 
      - | :ref:`equals <equals-ref>`
-       | :ref:`in-ref`
+       | :ref:`in <in-ref>`
        | :ref:`near <near-ref>`
        | :ref:`range <range-ref>`
 
@@ -249,7 +249,7 @@ query the field value.
      - :ref:`number <bson-data-types-number>`
      - ✓ 
      - | :ref:`equals <equals-ref>`
-       | :ref:`in-ref`
+       | :ref:`in <in-ref>`
        | :ref:`facet <fts-facet-ref>`
        | :ref:`near <near-ref>`
        | :ref:`range <range-ref>`
@@ -264,7 +264,7 @@ query the field value.
      - ✓ 
      - | :ref:`equals <equals-ref>`
        | :ref:`facet <fts-facet-ref>`
-       | :ref:`in-ref`
+       | :ref:`in <in-ref>`
        | :ref:`near <near-ref>`
        | :ref:`range <range-ref>`
 
@@ -293,7 +293,7 @@ query the field value.
      - :ref:`objectId <objectId-ref>`
      - ✓
      - | :ref:`equals <equals-ref>`
-       | :ref:`in-ref`
+       | :ref:`in <in-ref>`
        | :ref:`range <range-ref>`
 
    * - String 
@@ -328,7 +328,7 @@ query the field value.
      - :ref:`uuid <bson-data-types-uuid>` 
      - ✓
      - | :ref:`equals <equals-ref>`
-       | :ref:`in-ref`
+       | :ref:`in <in-ref>`
 
 :icon-fa5:`star` Some limitations apply. To learn more, see :ref:`fts-array-ref`. 
 

source/atlas-search/embedded-document.txt

@@ -507,7 +507,7 @@ Query for Matching Embedded Documents Only
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
 The following query returns only the nested documents that match the
-query. The query uses |fts| :ref:`compound-ref` operator clauses in the
+query. The query uses |fts| :ref:`compound operator <compound-ref>` clauses in the
 :pipeline:`$search` stage to find matching documents and then the
 :manual:`aggregation operators </reference/operator/aggregation/>` in
 the :pipeline:`$project` stage to return only matching embedded documents.
@@ -518,8 +518,8 @@ Specifically, the query specifies the following pipeline stages:
    :stub-columns: 1
 
    * - :pipeline:`$search` 
-     - Specifies the following criteria in the :ref:`compound-ref`
-       operator ``must`` clause:
+     - Specifies the following criteria in the :ref:`compound operator <compound-ref>`
+       ``must`` clause:
 
        - Check if ``items.price`` field exists in the collection.
        - Search for the items tagged as ``school`` in the ``items.tags``

source/atlas-search/equals.txt

@@ -527,7 +527,7 @@ null value in the ``job_title`` field.
 Compound Example Queries
 ~~~~~~~~~~~~~~~~~~~~~~~~
 
-The following example uses the :ref:`compound <compound-ref>` operator 
+The following example uses the :ref:`compound operator <compound-ref>`
 in conjunction with ``must``, ``mustNot``, and ``equals`` to search for 
 documents in which the ``region`` field is ``Southwest`` and the 
 ``verified_user`` field is not ``false``.

source/atlas-search/exists.txt

@@ -26,8 +26,8 @@ Definition
    The ``exists`` operator tests if a path to a specified indexed field
    name exists in a document. If the specified field exists but is not
    indexed, the document is not included with the result set.
-   ``exists`` is often used as part of a :ref:`compound
-   <compound-ref>` query in conjunction with other search clauses.
+   ``exists`` is often used as part of a :ref:`compound <compound-ref>`
+   query in conjunction with other search clauses.
 
 .. _exists-syntax:
 

source/atlas-search/field-types/boolean-type.txt

@@ -144,4 +144,4 @@ Learn More
 To learn more about the operators you can use to query the ``boolean`` type, see the following operator reference pages:
 
 - :ref:`equals-ref`
-- :ref:`in-ref`
+- :ref:`in <in-ref>`