Yet another typo run

source/faq/storage.txt

@@ -183,7 +183,7 @@ inserted into the database. Consider the following possible causes:
 
   To reclaim deleted space, use :dbcommand:`repairDatabase`, which
   rebuilds the database which de-fragments the storage and may release
-  space to the operating systme. :dbcommand:`repairDatabase` requires
+  space to the operating system. :dbcommand:`repairDatabase` requires
   up to 2 gigabytes of extra disk space to run. Do not use
   :dbcommand:`repairDatabase` if you are critically low on disk space.
 

source/reference/command/getLastError.txt

@@ -61,7 +61,7 @@ subset of the fields listed below.
 
 .. data:: getLastError.n
 
-   :data:`getLastErrr.n` reports the number of documents updated or
+   :data:`getLastError.n` reports the number of documents updated or
    removed, if the preceding operation was an update or remove
    operation.
 

source/reference/command/repairDatabase.txt

@@ -51,7 +51,7 @@ Definition
 
    .. note:: :dbcommand:`repairDatabase` requires free disk space equal to the size
       of your current data set plus 2 gigabytes. If the volume that holds dbpath
-      lacks sufficent space, you can mount a separate volume
+      lacks sufficient space, you can mount a separate volume
       and use that for the repair. When mounting a separate volume for
       :dbcommand:`repairDatabase` you must run :dbcommand:`repairDatabase`
       from the command line and use the

source/tutorial/split-chunks-in-sharded-cluster.txt

@@ -66,7 +66,7 @@ document as the lower bound in the new chunk:
 
       sh.splitAt( "records.people", { "zipcode": 63109 } )
 
-.. note:: :method:`~sh.splitAt()` does not nessarily split the chunk
+.. note:: :method:`~sh.splitAt()` does not necessarily split the chunk
    into two equally sized chunks. The split occurs at the location of
    the document matching the query, regardless of where that document is
    in the chunk.