Standardize arguments

Author: WaVEV

docs/source/ref/models/search.rst

@@ -47,13 +47,11 @@ matches on fields indexed in a MongoDB Atlas Search index.
     >>> Article.objects.annotate(score=SearchEquals(path="headline", value="title"))
     <QuerySet [<Article: headline: title>]>
 
-The ``path`` argument can be either the name of a field (as a string), or a
-:class:`~django.db.models.F` instance.
+**Arguments:**
 
-The ``value`` argument must be a string or a :class:`~django.db.models.Value`.
-
-The optional ``score`` argument is a :class:`SearchScoreOption` that tunes the
-relevance score.
+- ``path``: The document path to the field.
+- ``value``: The value to match.
+- ``score``: A :class:`SearchScoreOption` to tune the relevance score.
 
 ``SearchAutocomplete``
 ----------------------
@@ -75,16 +73,11 @@ in a MongoDB Atlas Search index.
        <Article: title: Harry Potter’s Cultural Impact on Literature>
     ]>
 
-The ``path`` argument specifies the field to search and can be a string or a
-:class:`~django.db.models.F`.
-
-The ``query`` is the user input string to autocomplete and can be passed as a
-string or a :class:`~django.db.models.Value`.
+**Arguments:**
 
-Optional arguments:
-
-- ``fuzzy``: A dictionary with fuzzy matching options such as
-  ``{"maxEdits": 1}``.
+- ``path``: The document path to the field.
+- ``query``: The value to match.
+- ``fuzzy``: Fuzzy matching options, e.g., ``{"maxEdits": 1}``.
 - ``token_order``: Controls token sequence behavior. Accepts values like
   ``"sequential"`` or ``"any"``.
 - ``score``: A :class:`SearchScoreOption` to tune the relevance score.
@@ -109,11 +102,10 @@ documents that include (or exclude) optional fields.
         <Article: title: Indexing Strategies with MongoDB (by Miguel)>
     ]>
 
-The ``path`` argument specifies the document path to check and can be provided
-as a string or a :class:`~django.db.models.F`.
+**Arguments:**
 
-The optional ``score`` argument is a :class:`SearchScoreOption` that tunes the
-relevance score.
+- ``path``: The document path to the field.
+- ``score``: A :class:`SearchScoreOption` to tune the relevance score.
 
 ``SearchIn``
 ------------
@@ -134,12 +126,11 @@ field contains a value from the provided array.
         <Article: title: Boosting Relevance Scores (number=2)>
     ]>
 
-The ``path`` argument can be the name of a field (as a string) or a
-:class:`~django.db.models.F`. The ``value`` must be a list
-of values or a :class:`~django.db.models.Value`.
+**Arguments:**
 
-The optional ``score`` argument is a :class:`SearchScoreOption` that tunes the
-relevance score.
+- ``path``: The document path to the field.
+- ``value``: The value to match.
+- ``score``: A :class:`SearchScoreOption` to tune the relevance score.
 
 ``SearchPhrase``
 ----------------
@@ -163,12 +154,10 @@ synonym mappings defined in the Atlas Search index.
         <Article: title: The Impact of Rapid Change in Climate Systems>
     ]>
 
-The ``path`` argument specifies the field to search and can be a string or a
-:class:`~django.db.models.F`. The ``query`` is the phrase to
-match, passed as a string or a list of strings (terms).
-
-Optional arguments:
+**Arguments:**
 
+- ``path``: The document path to the field.
+- ``query``: The value to match.
 - ``slop``: The maximum number of terms allowed between phrase terms.
 - ``synonyms``: The name of a synonym mapping defined in your Atlas index.
 - ``score``: A :class:`SearchScoreOption` to tune the relevance score.
@@ -195,12 +184,12 @@ supports features like boolean operators, wildcards, and field-specific terms.
         <Article: title: Advanced Query Techniques in Django ORM>
     ]>
 
-The ``path`` argument can be a string or a
-:class:`~django.db.models.F` representing the field to query.
-The ``query`` argument is a Lucene-style query string.
+**Arguments:**
+
+- ``path``: The document path to the field.
+- ``query``: A Lucene-style query string.
+- ``score``: A :class:`SearchScoreOption` to tune the relevance score.
 
-The optional ``score`` argument is a :class:`SearchScoreOption` that tunes the
-relevance score.
 
 ``SearchRange``
 ---------------
@@ -221,11 +210,9 @@ date, or other comparable fields based on upper and/or lower bounds.
         <Article: title: Pre-2020 Web Framework Evolution (number=2015)>
     ]>
 
-The ``path`` argument specifies the field to filter and can be a string or a
-:class:`~django.db.models.F`.
-
-Optional arguments:
+**Arguments:**
 
+- ``path``: The document path to the field.
 - ``lt``: Exclusive upper bound (``<``)
 - ``lte``: Inclusive upper bound (``<=``)
 - ``gt``: Exclusive lower bound (``>``)
@@ -251,22 +238,22 @@ expression pattern to the contents of a specified field.
         <Article: title: Breaking_Changes in Atlas Search API>
     ]>
 
-The ``path`` argument specifies the field to search and can be provided as a
-string or a :class:`~django.db.models.F`. The ``query`` is a
-regular expression string that will be applied to the field contents.
-
-Optional arguments:
+**Arguments:**
 
+- ``path``: The document path to the field.
+- ``query``: Regular expression string that will be applied to the field
+  contents.
 - ``allow_analyzed_field``: Boolean indicating whether to allow matching
-  against analyzed fields (defaults to ``False``).
+  against analyzed fields.
 - ``score``: A :class:`SearchScoreOption` to tune the relevance score.
 
 ``SearchText``
 --------------
 
 .. class:: SearchText(path, query, *, fuzzy=None, match_criteria=None, synonyms=None, score=None)
 
-Performs full-text search using the :doc:`text operator <atlas:atlas-search/text>`.
+Performs full-text search using the :doc:`text operator
+<atlas:atlas-search/text>`.
 
 Matches terms in the specified field and supports fuzzy matching, match
 criteria, and synonym mappings.
@@ -284,12 +271,10 @@ criteria, and synonym mappings.
         <Article: title: Understanding MongoDB Query Optimization>
     ]>
 
-The ``path`` argument specifies the field to search and can be provided as a
-string or a :class:`~django.db.models.F`. The ``query`` argument
-is the search term or phrase.
-
-Optional arguments:
+**Arguments:**
 
+- ``path``: The document path to the field.
+- ``query``: The argument is the search term or phrase.
 - ``fuzzy``: A dictionary of fuzzy matching options, such as
   ``{"maxEdits": 1}``.
 - ``match_criteria``: Whether to match ``"all"`` or ``"any"`` terms (defaults
@@ -319,14 +304,12 @@ single character) wildcards.
         <Article: title: report_2022_final_review>
     ]>
 
-The ``path`` argument specifies the field to search and can be a string or a
-:class:`~django.db.models.F`. The ``query`` is a wildcard string
-that may include ``*`` and ``?``.
-
-Optional arguments:
+**Arguments:**
 
-- ``allow_analyzed_field``: Boolean that allows matching against analyzed
-  fields (defaults to ``False``).
+- ``path``: The document path to the field.
+- ``query``: A wildcard string that may include ``*`` and ``?``.
+- ``allow_analyzed_field``: Boolean indicating whether to allow matching
+  against analyzed fields.
 - ``score``: A :class:`SearchScoreOption` to tune the relevance score.
 
 ``SearchGeoShape``
@@ -337,8 +320,8 @@ Optional arguments:
 Filters documents based on spatial relationships with a geometry.
 
 Uses the :doc:`geoShape operator <atlas:atlas-search/geoShape>` to match
-documents where a geo field has a specified spatial relation to a given GeoJSON
-geometry.
+documents where a geo field has a specified spatial relation to a given
+GeoJSON geometry.
 
 .. code-block:: pycon
 
@@ -352,17 +335,13 @@ geometry.
        <Article: title: Urban Planning in District 5 (location: [1, 2])>
     ]>
 
-The ``path`` argument specifies the field to filter and can be a string or a
-:class:`~django.db.models.F`.
-
-Required arguments:
+**Arguments:**
 
+- ``path``: The document path to the field.
 - ``relation``: The spatial relation to test. Valid values include
   ``"within"``, ``"intersects"``, and ``"disjoint"``.
 - ``geometry``: A GeoJSON geometry object to compare against.
-
-The optional ``score`` argument is a :class:`SearchScoreOption` that tunes the
-relevance score.
+- ``score``: A :class:`SearchScoreOption` to tune the relevance score.
 
 ``SearchGeoWithin``
 -------------------
@@ -387,16 +366,12 @@ geometry.
        <Article: title: Urban Planning in District 5 (location: [1, 2])>
     ]>
 
-The ``path`` argument specifies the geo field to filter and can be a string or
-a :class:`~django.db.models.F`.
-
-Required arguments:
+**Arguments:**
 
+- ``path``: The document path to the field.
 - ``kind``: The GeoJSON geometry type ``circle``, ``box``, or ``geometry``.
 - ``geo_object``: The GeoJSON geometry defining the spatial boundary.
-
-The optional ``score`` argument is a :class:`SearchScoreOption` that tunes the
-relevance score.
+- ``score``: A :class:`SearchScoreOption` to tune the relevance score.
 
 ``SearchMoreLikeThis``
 ----------------------
@@ -422,11 +397,12 @@ retrieve documents that resemble one or more example documents.
         <Article: title: Similar Approaches in Database Design>
     ]>
 
-The ``documents`` argument must be a list of example documents or expressions
-that serve as references for similarity.
+**Arguments:**
+
+- ``documents``: List of example documents or expressions
+  that serve as references for similarity.
+- ``score``: A :class:`SearchScoreOption` to tune the relevance score.
 
-The optional ``score`` argument is a :class:`SearchScoreOption` that tunes the
-relevance score.
 
 ``CompoundExpression``
 ======================
@@ -454,64 +430,21 @@ contribute to document matching and scoring.
     ... )
     <QuerySet [<Article: title: MongoDB Atlas Database Performance Optimization>]>
 
-Arguments:
+**Arguments:**
 
 - ``must``: A list of expressions that **must** match.
 - ``must_not``: A list of expressions that **must not** match.
-- ``should``: A list of optional expressions that **should** match.
-  These can improve scoring.
+- ``should``: A list of optional expressions that **should** match. These can
+  improve scoring.
 - ``filter``: A list of expressions used for filtering without affecting
   relevance scoring.
-- ``minimum_should_match``: The minimum number of ``should`` clauses that
-  must match.
+- ``minimum_should_match``: The minimum number of ``should`` clauses that must
+  match.
 - ``score``: A :class:`SearchScoreOption` to tune the relevance score.
 
-``CompoundExpression`` is useful for building advanced and flexible query
-logic in Atlas Search.
-
-``CombinedSearchExpression``
-============================
-
-.. class:: CombinedSearchExpression(lhs, operator, rhs)
-
-Expression that combines two Atlas Search expressions using a boolean
-operator.
 
-This expression is used internally when combining search expressions with
-Python's bitwise operators (``&``, ``|``, ``~``), corresponding to the logical
-operators such as ``and``, ``or``, and ``not``.
-
-.. admonition:: Typical usage
-
-   This expression is typically created when using the combinable interface
-   (e.g., ``expr1 & expr2``). It can also be constructed manually.
-
-.. code-block:: pycon
-
-    >>> from django_mongodb_backend.expressions import CombinedSearchExpression
-    >>> expr1 = SearchText("headline", "mongodb")
-    >>> expr2 = SearchText("body", "atlas")
-    >>> CombinedSearchExpression(expr1, "and", expr2)
-    CombinedSearchExpression(
-        lhs=SearchText(path='headline', query='mongodb'),
-        operator='and',
-        rhs=SearchText(path='body', query='atlas')
-    )
-
-Args:
-
-- ``lhs``: The left-hand side search expression.
-- ``operator``: A string representing the logical operator (``"and"``,
-  ``"or"``, or ``"not"``).
-- ``rhs``: The right-hand side search expression.
-
-This is the underlying expression used to support operator overloading in
-Atlas Search expressions.
-
-.. _search-operations-combinable:
-
-Combinable expressions
-----------------------
+``Combinable expressions``
+--------------------------
 
 All Atlas Search expressions subclassed from ``SearchExpression``
 can be combined using Python's bitwise operators:
@@ -531,10 +464,6 @@ This allows for more expressive and readable search logic:
         <Article: title: Modern MongoDB Features>
     ]>
 
-Under the hood, these expressions are translated into
-:class:`CombinedSearchExpression` instances, which can be reused and nested
-with other compound expressions.
-
 ``SearchVector``
 ================
 
@@ -543,8 +472,8 @@ with other compound expressions.
 Performs vector similarity search using the :doc:`$vectorSearch stage
 <atlas:atlas-vector-search/vector-search-stage>`.
 
-Retrieves documents whose vector field is most similar to a given query vector,
-using either approximate or exact nearest-neighbor search.
+Retrieves documents whose vector field is most similar to a given query
+vector, using either approximate or exact nearest-neighbor search.
 
 .. code-block:: pycon
 
@@ -560,18 +489,16 @@ using either approximate or exact nearest-neighbor search.
     ... )
     <QuerySet [<Article: Article object (6882f074359a4b191381b2e4)>]>
 
-Arguments:
 
-- ``path``: The document path to the vector field (string or
-  :class:`~django.db.models.F`).
+**Arguments:**
+
+- ``path``: The document path to the field.
 - ``query_vector``: The input vector used for similarity comparison.
 - ``limit``: The maximum number of matching documents to return.
-- ``num_candidates``: (Optional) The number of candidate documents considered
-  during search.
-- ``exact``: (Optional) Whether to enforce exact search instead of approximate
-  (defaults to ``False``).
-- ``filter``: (Optional) A filter expression to restrict the candidate
-  documents.
+- ``num_candidates``: The number of candidate documents considered during
+  search.
+- ``exact``:  A boolean whether to enforce exact search instead of approximate.
+- ``filter``: A MQL filter expression to restrict the candidate documents.
 
 .. warning::