Fix documentation nits

Just minor spelling and grammar fixes.

Change-Id: I2dc98e4b68ac2df35fe1647cd4af3402cd55d77d
diff --git a/doc/source/admin/installation.rst b/doc/source/admin/installation.rst
index bc61f7e..ae7d571 100644
--- a/doc/source/admin/installation.rst
+++ b/doc/source/admin/installation.rst
@@ -30,7 +30,7 @@
 
 Gearman is a job distribution system that Zuul uses to communicate
 with its distributed components.  The Zuul scheduler distributes work
-to Zuul mergers and executors use Gearman.  You may supply your own
+to Zuul mergers and executors using Gearman.  You may supply your own
 gearman server, but the Zuul scheduler includes a built-in server
 which is recommended.  Ensure that all Zuul hosts can communicate with
 the gearman server.
@@ -56,7 +56,7 @@
 Nodepool uses Zookeeper to communicate internally among its
 components, and also to communicate with Zuul.  You can run a simple
 single-node Zookeeper instance, or a multi-node cluster.  Ensure that
-The host running the Zuul scheduler has access to the cluster.
+the host running the Zuul scheduler has access to the cluster.
 
 Ansible
 ~~~~~~~
diff --git a/doc/source/admin/monitoring.rst b/doc/source/admin/monitoring.rst
index 9c69960..4fed1f9 100644
--- a/doc/source/admin/monitoring.rst
+++ b/doc/source/admin/monitoring.rst
@@ -31,12 +31,12 @@
 Metrics
 ~~~~~~~
 
-The metrics are emitted by the Zuul :ref:`scheduler`:
+These metrics are emitted by the Zuul :ref:`scheduler`:
 
 .. stat:: gerrit.event.<type>
    :type: counter
 
-   Gerrit emits different kind of message over its `stream-events`
+   Gerrit emits different kinds of messages over its `stream-events`
    interface.  Zuul will report counters for each type of event it
    receives from Gerrit.
 
@@ -89,7 +89,7 @@
       .. stat:: total_changes
          :type: counter
 
-         The number of change processed by the pipeline since Zuul
+         The number of changes processed by the pipeline since Zuul
          started.
 
       .. stat:: wait_time
@@ -119,7 +119,7 @@
          .. stat:: total_changes
             :type: counter
 
-            The number of change for this project processed by the
+            The number of changes for this project processed by the
             pipeline since Zuul started.
 
 As an example, given a job named `myjob` triggered by the `gate` pipeline