[2/3] storm git commit: Addressed review comments

[bo...@apache.org]

Addressed review comments


Project: http://git-wip-us.apache.org/repos/asf/storm/repo
Commit: http://git-wip-us.apache.org/repos/asf/storm/commit/617b03a6
Tree: http://git-wip-us.apache.org/repos/asf/storm/tree/617b03a6
Diff: http://git-wip-us.apache.org/repos/asf/storm/diff/617b03a6

Branch: refs/heads/master
Commit: 617b03a6af580c00aaa8d31f4cdde1a8bd7bc5c9
Parents: 46fe41e
Author: Robert (Bobby) Evans <ev...@yahoo-inc.com>
Authored: Tue Oct 23 11:11:55 2018 -0500
Committer: Robert (Bobby) Evans <ev...@yahoo-inc.com>
Committed: Tue Oct 23 11:11:55 2018 -0500

----------------------------------------------------------------------
 docs/Local-mode.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)
----------------------------------------------------------------------


http://git-wip-us.apache.org/repos/asf/storm/blob/617b03a6/docs/Local-mode.md
----------------------------------------------------------------------
diff --git a/docs/Local-mode.md b/docs/Local-mode.md
index 31afcc3..3b83d54 100644
--- a/docs/Local-mode.md
+++ b/docs/Local-mode.md
@@ -9,7 +9,7 @@ To run a topology in local mode you have two options.  The most common option is
 
 This will bring up a local simulated cluster and force all interactions with nimbus to go through the simulated cluster instead of going to a separate process. By default this will run the process for 20 seconds before tearing down the entire cluster.  You can override this by including a `--local-ttl` command line option which sets the number of seconds it should run for.
 
-### Programatic
+### Programmatic
 
 If you want to do some automated testing but without actually launching a storm cluster you can use the same classes internally that `storm local` does.
 
@@ -79,7 +79,7 @@ You can see a full list of configurations [here](javadocs/org/apache/storm/Confi
 1. **Config.TOPOLOGY_MAX_TASK_PARALLELISM**: This config puts a ceiling on the number of threads spawned for a single component. Oftentimes production topologies have a lot of parallelism (hundreds of threads) which places unreasonable load when trying to test the topology in local mode. This config lets you easy control that parallelism.
 2. **Config.TOPOLOGY_DEBUG**: When this is set to true, Storm will log a message every time a tuple is emitted from any spout or bolt. This is extremely useful for debugging.A
 
-These, like all other configs, can be set on the command line when launching your toplogy with the `-c` flag.  The flag is of the form `-c <conf_name>=<JSON_VALUE>`  so to enable debugging when launching your topology in local mode you could run
+These, like all other configs, can be set on the command line when launching your topology with the `-c` flag.  The flag is of the form `-c <conf_name>=<JSON_VALUE>`  so to enable debugging when launching your topology in local mode you could run
 
 ```
 storm local topology.jar <MY_MAIN_CLASS> -c topology.debug=true