From da1e35f39cd60878f32b5446438afdf25d868d7b Mon Sep 17 00:00:00 2001
From: Imran Rashid <irashid@cloudera.com>
Date: Mon, 4 May 2015 21:32:40 -0500
Subject: [PATCH] typos etc.

---
 docs/monitoring.md | 15 ++++++++-------
 1 file changed, 8 insertions(+), 7 deletions(-)

diff --git a/docs/monitoring.md b/docs/monitoring.md
index de187c99f12c8..1e0fc150862fb 100644
--- a/docs/monitoring.md
+++ b/docs/monitoring.md
@@ -178,8 +178,9 @@ Note that the history server only displays completed Spark jobs. One way to sign
 
 In addition to viewing the metrics in the UI, they are also available as JSON.  This gives developers
 an easy way to create new visualizations and monitoring tools for Spark.  The JSON is available for
-both running applications, an in the history server.  The endpoints are mounted at `/json/v1`.  Eg.,
-for the history server, they would typically be accessible at `http://<server-url>:18080/json/v1`.
+both running applications, and in the history server.  The endpoints are mounted at `/json/v1`.  Eg.,
+for the history server, they would typically be accessible at `http://<server-url>:18080/json/v1`, and
+for a running application, at `http://localhost:4040/json/v1`.
 
 <table class="table">
   <tr><th>Endpoint</th><th>Meaning</th></tr>
@@ -193,7 +194,7 @@ for the history server, they would typically be accessible at `http://<server-ur
   </tr>
   <tr>
     <td><code>/applications/[app-id]/jobs/[job-id]</code></td>
-    <td>Details for one job</td>
+    <td>Details for the given job</td>
   </tr>
   <tr>
     <td><code>/applications/[app-id]/stages</code></td>
@@ -201,7 +202,7 @@ for the history server, they would typically be accessible at `http://<server-ur
   </tr>
   <tr>
     <td><code>/applications/[app-id]/stages/[stage-id]</code></td>
-    <td>A list of all attempts for a given stage</td>
+    <td>A list of all attempts for the given stage</td>
   </tr>
   <tr>
     <td><code>/applications/[app-id]/stages/[stage-id]/[stage-attempt-id]</code></td>
@@ -209,11 +210,11 @@ for the history server, they would typically be accessible at `http://<server-ur
   </tr>
   <tr>
     <td><code>/applications/[app-id]/stages/[stage-id]/[stage-attempt-id]/taskSummary</code></td>
-    <td>Summary metrics of all tasks in a stage attempt</td>
+    <td>Summary metrics of all tasks in the given stage attempt</td>
   </tr>
   <tr>
     <td><code>/applications/[app-id]/stages/[stage-id]/[stage-attempt-id]/taskList</code></td>
-    <td>A list of all tasks for a given stage attempt</td>
+    <td>A list of all tasks for the given stage attempt</td>
   </tr>
   <tr>
     <td><code>/applications/[app-id]/executors</code></td>
@@ -240,7 +241,7 @@ These endpoints have been strongly versioned to make it easier to develop applic
 * New endpoints may be added
 * New fields may be added to existing endpoints
 * New versions of the api may be added in the future at a separate endpoint (eg., `json/v2`).  New versions are *not* required to be backwards compatible.
-* Api versions may be dropped, but only after at least one minor release of existing beside a new api version
+* Api versions may be dropped, but only after at least one minor release of co-existing with a new api version
 
 Note that even when examining the UI of a running applications, the `applications/[app-id]` portion is
 still required, though there is only one application available.  Eg. to see the list of jobs for the