MONGOID-5050 Fix various typos in documentation (#5028)

* Fix various typos in documentation

* More fixes

Co-authored-by: shields <[email protected]>

Author: johnnyshields

source/ecosystem.txt

@@ -35,7 +35,7 @@ Extension Libraries
 
 - `Mongoid Collection Snapshot <https://github.com/mongoid/mongoid-collection-snapshot>`_
 
-  Easy maintenence of collections of processed data in MongoDB with the Mongoid ODM.
+  Easy maintenance of collections of processed data in MongoDB with the Mongoid ODM.
 
 - `Mongoid Locker <https://github.com/mongoid/mongoid-locker>`_
 

source/reference/associations.txt

@@ -166,7 +166,7 @@ documents and does not query the database:
   band.members.any?
 
 Note that simply calling ``any?`` would *not* load the association
-(since ``any?`` only retrtieves the _id field of the first matching document).
+(since ``any?`` only retrieves the _id field of the first matching document).
 
 ``exists?``
 ~~~~~~~~~~~
@@ -180,7 +180,7 @@ any *persisted* documents in the association. Unlike the ``any?`` method:
 - ``exists?`` does not allow filtering in the application like ``any?`` does,
   and does not take any arguments.
 
-The following examle illustrates the difference between ``exists?`` and
+The following example illustrates the difference between ``exists?`` and
 ``any?``:
 
 .. code-block:: ruby
@@ -919,7 +919,7 @@ is defined:
 - ``:foreign_key`` is the field on the local model which stores the
   ``:primary_key`` values.
 - ``:inverse_primary_key`` is the field on the local model that the remote
-  model uses to look up the local model docuemnts.
+  model uses to look up the local model documents.
 - ``:inverse_foreign_key`` is the field on the remote model storing the
   values in ``:inverse_primary_key``.
 
@@ -1531,7 +1531,7 @@ are supported:
 - `$project <https://docs.mongodb.com/manual/reference/operator/aggregation/project/>`_
 - `$unwind <https://docs.mongodb.com/manual/reference/operator/aggregation/unwind/>`_
 
-To construct a pipeline, call the corresponding aggregation pipeine methods
+To construct a pipeline, call the corresponding aggregation pipeline methods
 on a ``Criteria`` instance. Aggregation pipeline operations are added to the
 ``pipeline`` attribute of the ``Criteria`` instance. To execute the pipeline,
 pass the ``pipeline`` attribute value to ``Collection#aggragegate`` method.
@@ -1592,7 +1592,7 @@ Alternatively, standard MongoDB aggregation pipeline syntax may be used:
 
 .. code-block:: ruby
 
-    criteria = Tour.all.group(_id: 'states', states: {'$addtoSet' => '$states'})
+    criteria = Tour.all.group(_id: 'states', states: {'$addToSet' => '$states'})
 
 project
 ```````
@@ -1616,7 +1616,7 @@ unwind
 The ``unwind`` method adds an `$unwind aggregation pipeline stage
 <https://docs.mongodb.com/manual/reference/operator/aggregation/unwind/>`_.
 
-The argument can be a field name, specifyable as a symbol or a string, or
+The argument can be a field name, specifiable as a symbol or a string, or
 a Hash or a ``BSON::Document`` instance:
 
 .. code-block:: ruby

source/reference/configuration.txt

@@ -605,7 +605,7 @@ When using Mongoid with a forking web server such as Puma, Unicorn or
 Passenger, it is recommended to not perform any operations on Mongoid models
 in the parent process prior to the fork.
 
-When a process forks, Ruby threads are not transfered to the child processes
+When a process forks, Ruby threads are not transferred to the child processes
 and the Ruby driver Client objects lose their background monitoring. The
 application will typically seem to work just fine until the deployment
 state changes (for example due to network errors, a maintenance event) at

source/reference/crud.txt

@@ -707,7 +707,7 @@ Hash Access
 -----------
 
 Mongoid model instances define the ``[]`` and ``[]=`` methods to provide
-``Hash`` style acccess to the attributes. ``[]`` is an alias for
+``Hash`` style access to the attributes. ``[]`` is an alias for
 ``read_attribute`` and ``[]=`` is an alias for ``write_attribute``; see
 the section on :ref:`read_attribute and write_attribute <read-write-attribute>`
 for the detailed description of their behavior.

source/reference/fields.txt

@@ -209,7 +209,7 @@ or else the values will not store properly.
        save
      end
 
-     # all data will fail to save due to the illegal hashkey
+     # all data will fail to save due to the illegal hash key
      def set_vals_fail
        self.first_name = 'Daniel'
        self.url = {'home.page' => 'http://www.homepage.com'}
@@ -323,7 +323,7 @@ the :ref:`default Mongoid time zone <time-zones>` is used:
     ticket.opened_at
     # => Sun, 04 Mar 2018 15:00:00 +0000
 
-If a time zone is specfied, it is respected:
+If a time zone is specified, it is respected:
 
 .. code-block:: ruby
 
@@ -680,7 +680,7 @@ Custom Ids
 ----------
 
 By default, Mongoid defines the ``_id`` field on documents to contain a
-``BSON::ObjcetId`` value which is automatically generated by Mongoid.
+``BSON::ObjectId`` value which is automatically generated by Mongoid.
 
 It is possible to replace the ``_id`` field definition to change the type
 of the ``_id`` values or have different default values:
@@ -816,7 +816,7 @@ defined, and invoking them raises ``NoMethodError``:
   # => "Bob"
 
 Attributes can always be read using mass attribute access or ``read_attribute``
-(this appies to models not using dynamic fields as well):
+(this applies to models not using dynamic fields as well):
 
 .. code-block:: ruby
 

source/reference/queries.txt

@@ -527,8 +527,8 @@ Mongoid provides three merge strategies:
   same field, the values of the existing condition are intersected with the
   values of the new condition and the result is stored as the operator value.
 - **Union**: if there already is a condition using the same operator on the
-  same field, the values of the new condition are aded to the values of the
-  exsting condition and the result is stored as the operator value.
+  same field, the values of the new condition are added to the values of the
+  existing condition and the result is stored as the operator value.
 
 The following snippet demonstrates all of the strategies, using ``in`` as the
 example operator:
@@ -796,7 +796,7 @@ should therefore be avoided.
 
     band = Band.only(:tours, 'tours.year').last
 
-  The most recent projection specification overrided the earlier one.
+  The most recent projection specification overrides the earlier one.
   For example, the above query was equivalent to:
 
   .. code-block:: ruby
@@ -1027,8 +1027,8 @@ The Improved Driver Query Cache
 -------------------------------
 
 The Mongoid query cache has been reimplemented in version 2.14.0 of the MongoDB
-Ruby Driver. The driver query cache is more correct and more effective, and it
-is recmomended that you upgrade to version 2.14.0 of the Ruby driver or newer.
+Ruby Driver. The driver query cache is more correct and more effective, and we
+recommended that you upgrade to version 2.14.0 of the Ruby driver or newer.
 
 For the purposes of this tutorial, the Mongoid query cache will be called "the
 legacy query cache", and the driver query cache will be referred to as "the
@@ -1231,7 +1231,7 @@ Mongoid also has some helpful methods on criteria.
    * - ``Criteria#estimated_count``
 
        *Get an approximate number of documents in the collection using the
-       collection metadta. The* ``estimated_count`` *method does not accept
+       collection metadata. The* ``estimated_count`` *method does not accept
        query conditions; if any are given, it will raise*
        ``Mongoid::Errors::InvalidEstimatedCountCriteria``.
        *If a model defines a default scope,* ``estimated_count`` *must be

source/release-notes/mongoid-7.2.txt

@@ -287,7 +287,7 @@ or globally. To set the discriminator key on the parent class:
    class Rectangle < Shape
    end
 
-To set the discrminator key globally:
+To set the discriminator key globally:
 
 .. code-block:: ruby
 

source/tutorials/getting-started-rails.txt

@@ -65,7 +65,7 @@ Use the ``rails`` command to create the application skeleton, as follows:
     in a moment.
 
 We pass ``--skip-active-record`` to request that ActiveRecord is not added
-as a dependency, because we will be using Mongoid instead. Additionaly
+as a dependency, because we will be using Mongoid instead. Additionally
 we pass ``--skip-bundle`` because we'll be modifying the ``Gemfile`` to
 add the ``mongoid`` dependency.
 
@@ -479,7 +479,7 @@ include ``Mongoid::Document``, and usually define the fields explicitly
 (but :ref:`dynamic fields <dynamic-fields>` may also be used instead of
 explicit field definitions).
 
-For example, a barebones Post model may look like this in ActiveRecord:
+For example, a bare-bones Post model may look like this in ActiveRecord:
 
 .. code-block:: ruby
   :name: app/models/post.rb