fixes

Author: rustagir

source/atlas-vector-search.txt

@@ -63,13 +63,6 @@ The following example shows how to build an aggregation pipeline that uses the
    :language: java
    :dedent:
 
-.. tip:: Query Vector Type
-
-   The preceding example creates an instance of ``BinaryVector`` to
-   serve as the query vector, but you can also create a ``List`` of
-   ``Double`` instances. However, we recommend that you use the
-   ``BinaryVector`` type to improve storage efficiency.
-
 The following example shows how you can run the aggregation and print
 the vector search meta-score from the result of the preceding
 aggregation pipeline:
@@ -103,5 +96,3 @@ guide, see the following API documentation:
 
 - `Projections.metaVectorSearchScore()
   <{+api+}/apidocs/mongodb-driver-core/com/mongodb/client/model/Projections.html#metaVectorSearchScore(java.lang.String)>`__
-
-- `BinaryVector <{+api+}/apidocs/bson/org/bson/BinaryVector.html>`__

source/builders/aggregates.txt

@@ -15,10 +15,6 @@ Aggregates Builders
    :depth: 2
    :class: singlecol
 
-.. toctree::
-
-   Atlas Vector Search </builders/vector-search>
-
 .. _aggregates-builders:
 
 Overview

source/builders/indexes.txt

@@ -29,7 +29,7 @@ following types of indexes:
 
 Indexes store a subset of the collection’s data set. The index stores
 the value of a specific field or set of fields, ordered by the value of
-the field. See our guide on :doc:`Indexes </fundamentals/indexes>` for
+the field. See our guide on :ref:`Indexes <java-fundamentals-indexes>` for
 examples of queries covered by indexes. 
 
 The ``Indexes`` class provides static factory methods for all the MongoDB index types.

source/builders/updates.txt

@@ -1,3 +1,5 @@
+.. _updates-builders:
+
 ================
 Updates Builders
 ================
@@ -8,8 +10,6 @@ Updates Builders
    :depth: 2
    :class: singlecol
 
-.. _updates-builders:
-
 Overview
 --------
 

source/crud/collations.txt

@@ -70,7 +70,7 @@ order as shown below:
 How to Specify Collations
 -------------------------
 
-MongoDB supports collations on most :doc:`CRUD operations </fundamentals/crud>`
+MongoDB supports collations on most :ref:`CRUD operations <java-crud-operations>`
 and aggregations. For a complete list of supported operations, see the
 :manual:`Operations that Support Collations </reference/collation/#operations-that-support-collation>`
 server manual page.

source/crud/read-operations/geo.txt

@@ -194,7 +194,7 @@ Examples
 
 The following examples use the MongoDB Atlas sample dataset. You can learn how
 to  set up your own free-tier Atlas cluster and how to load the sample dataset
-in our :doc:`quick start guide </quick-start>`.
+in the :ref:`java-sync-quickstart` guide.
 
 The examples use the ``theaters`` collection in the ``sample_mflix`` database
 from the sample dataset. The ``theaters`` collection contains a ``2dsphere`` index

source/crud/read-operations/retrieve.txt

@@ -101,7 +101,7 @@ instance of a ``MongoCollection``. This method accepts aggregation
 expressions to run in sequence. To perform aggregations, you can
 define aggregation stages that specify how to match documents, rename
 fields, and group values. For more information, see our
-:doc:`Aggregation </fundamentals/aggregation>` guide.
+:ref:`Aggregation <java-aggregation>` guide.
 
 Example
 ~~~~~~~

source/crud/write-operations/modify.txt

@@ -67,7 +67,10 @@ The ``updateOne()`` and ``updateMany()`` methods both have the following
 parameters:
 
 - ``query`` specifies a query filter with the criteria to match documents to update in your collection
-- ``updateDocument`` specifies the fields and values to modify in the matching document or documents. For this example, we use the :doc:`Updates builder </fundamentals/builders/updates>` to create the update document.
+- ``updateDocument`` specifies the fields and values to modify in the
+  matching document or documents. For this example, we use the
+  :ref:`Updates builder <updates-builders>` to create the
+  update document.
 
 You can create the ``updateDocument`` using an ``Updates`` builder as
 follows:

source/indexes.txt

@@ -204,6 +204,7 @@ Multikey indexes behave differently from other indexes in terms of query coverag
 sort behavior. To learn more about multikey indexes, including a discussion of their behavior and limitations,
 see the :manual:`Multikey Indexes page </core/index-multikey>` in the MongoDB manual.
 
+.. _java-search-indexes:
 .. _search-indexes:
 
 Atlas Search Indexes
@@ -595,4 +596,5 @@ For prior versions of MongoDB, pass "*" as a parameter to your call to
 For more information about the methods in this section, see the following API Documentation:
 
 - `dropIndex() <{+api+}/apidocs/mongodb-driver-sync/com/mongodb/client/MongoCollection.html#dropIndex(java.lang.String)>`__
-- `dropIndexes() <{+api+}/apidocs/mongodb-driver-sync/com/mongodb/client/MongoCollection.html#dropIndexes()>`__
+- `dropIndexes()
+  <{+api+}/apidocs/mongodb-driver-sync/com/mongodb/client/MongoCollection.html#dropIndexes()>`__