diff --git a/docs/reference/configuration.txt b/docs/reference/configuration.txt
index 35b90ab347..93e2581773 100644
--- a/docs/reference/configuration.txt
+++ b/docs/reference/configuration.txt
@@ -396,7 +396,7 @@ for details on driver options.
     driver_options:
       # When this flag is off, an aggregation done on a view will be executed over
       # the documents included in that view, instead of all documents in the
-      # collection. When this flag is on, the view fiter is ignored.
+      # collection. When this flag is on, the view filter is ignored.
       # broken_view_aggregate: true
 
       # When this flag is set to false, the view options will be correctly
@@ -404,7 +404,7 @@ for details on driver options.
       # broken_view_options: true
 
       # When this flag is set to true, the update and replace methods will
-      # validate the paramters and raise an error if they are invalid.
+      # validate the parameters and raise an error if they are invalid.
       # validate_update_replace: false
 
 
diff --git a/docs/reference/fields.txt b/docs/reference/fields.txt
index 6687a6a420..5e29bfeec4 100644
--- a/docs/reference/fields.txt
+++ b/docs/reference/fields.txt
@@ -927,7 +927,7 @@ Reading Uncastable Values
 `````````````````````````
 
 When documents in the database contain values of different types than their
-represenations in Mongoid, if Mongoid cannot coerce them into the correct type,
+representations in Mongoid, if Mongoid cannot coerce them into the correct type,
 it will replace the value with ``nil``. Consider the following model and document in the
 database:
 
@@ -1105,7 +1105,7 @@ used for MongoDB serialization and deserialization as follows:
   end
 
 The instance method ``mongoize`` takes an instance of your custom type object, and
-converts it into a represenation of how it will be stored in the database, i.e. to pass
+converts it into a representation of how it will be stored in the database, i.e. to pass
 to the MongoDB Ruby driver. In our example above, we want to store our ``Point``
 object as an ``Array`` in the form ``[ x, y ]``.
 
@@ -1228,7 +1228,7 @@ which extend its behavior at the your time model classes are loaded.
 
 As an example, we will define a ``:max_length`` option which will add a length
 validator for the field. First, declare the new field option in an initializer,
-specifiying its handler function as a block:
+specifying its handler function as a block:
 
 .. code-block:: ruby
 
diff --git a/docs/reference/rails-integration.txt b/docs/reference/rails-integration.txt
index 4c7181cff0..2f8f02ace7 100644
--- a/docs/reference/rails-integration.txt
+++ b/docs/reference/rails-integration.txt
@@ -24,7 +24,7 @@ other Rails environment specific options by accessing config.mongoid. The
 ``mongoid:config`` generator will create an initializer in
 ``config/initializers/mongoid.rb`` which can also be used for configuring
 Mongoid. Note, though, that options set in your ``config/mongoid.yml`` will
-take precendence over options set elsewhere; it is recommended that whenever
+take precedence over options set elsewhere; it is recommended that whenever
 possible you use ``mongoid.yml`` as the default location for Mongoid
 configuration.