aboutsummaryrefslogtreecommitdiff
path: root/docs/monitoring.md
diff options
context:
space:
mode:
authorkballou <kballou@devnulllabs.io>2014-07-31 14:58:52 -0700
committerJosh Rosen <joshrosen@apache.org>2014-07-31 14:58:52 -0700
commitcc820502fb08f71b03237103153c34487b2600b4 (patch)
tree8aa448dfafaf0bebd6578cee46626b4693cbd0a9 /docs/monitoring.md
parente02136214a6c2635e88c36b1f530a97e975d83e3 (diff)
downloadspark-cc820502fb08f71b03237103153c34487b2600b4.tar.gz
spark-cc820502fb08f71b03237103153c34487b2600b4.tar.bz2
spark-cc820502fb08f71b03237103153c34487b2600b4.zip
Docs: monitoring, streaming programming guide
Fix several awkward wordings and grammatical issues in the following documents: * docs/monitoring.md * docs/streaming-programming-guide.md Author: kballou <kballou@devnulllabs.io> Closes #1662 from kennyballou/grammar_fixes and squashes the following commits: e1b8ad6 [kballou] Docs: monitoring, streaming programming guide
Diffstat (limited to 'docs/monitoring.md')
-rw-r--r--docs/monitoring.md4
1 files changed, 2 insertions, 2 deletions
diff --git a/docs/monitoring.md b/docs/monitoring.md
index 84073fe4d9..d07ec4a57a 100644
--- a/docs/monitoring.md
+++ b/docs/monitoring.md
@@ -33,7 +33,7 @@ application's UI after the application has finished.
If Spark is run on Mesos or YARN, it is still possible to reconstruct the UI of a finished
application through Spark's history server, provided that the application's event logs exist.
-You can start a the history server by executing:
+You can start the history server by executing:
./sbin/start-history-server.sh
@@ -106,7 +106,7 @@ follows:
<td>
Indicates whether the history server should use kerberos to login. This is useful
if the history server is accessing HDFS files on a secure Hadoop cluster. If this is
- true it looks uses the configs <code>spark.history.kerberos.principal</code> and
+ true, it uses the configs <code>spark.history.kerberos.principal</code> and
<code>spark.history.kerberos.keytab</code>.
</td>
</tr>