Add detail for getting PID to shutdown docs

jasontedor · jasontedor · commit 45501405f25b · 2016-07-07T12:27:05.000-04:00
diff --git a/docs/reference/setup/stopping.asciidoc b/docs/reference/setup/stopping.asciidoc
@@ -11,16 +11,29 @@ functionality provided by your installation.
 
 If you're running Elasticsearch directly, you can stop Elasticsearch by sending control-C if you're
 running Elasticsearch in the console, or by sending `SIGTERM` to the Elasticsearch process on a
-POSIX system. You can obtain the PID to send the signal to via various tools (e.g., `ps` or `jps`),
-from the Elasticsearch statrup logs, or by specifying a location to write a PID file to on startup
-(`-p <path>`).
+POSIX system. You can obtain the PID to send the signal to via various tools (e.g., `ps` or `jps`):
+
+[source,sh]
+--------------------------------------------------
+$ jps | grep Elasticsearch
+14542 Elasticsearch
+--------------------------------------------------
+
+From the Elasticsearch startup logs:
+
+[source,sh]
+--------------------------------------------------
+[2016-07-07 12:26:18,908][INFO ][node                     ] [Reaper] version[5.0.0-alpha4], pid[15399], build[3f5b994/2016-06-27T16:23:46.861Z], OS[Mac OS X/10.11.5/x86_64], JVM[Oracle Corporation/Java HotSpot(TM) 64-Bit Server VM/1.8.0_92/25.92-b14]
+--------------------------------------------------
+
+Or by specifying a location to write a PID file to on startup (`-p <path>`):
 
 [source,sh]
 --------------------------------------------------
 $ ./bin/elasticsearch -p /tmp/elasticsearch-pid -d
 $ cat /tmp/elasticsearch-pid && echo
-7801
-$ kill -SIGTERM 7801
+15516
+$ kill -SIGTERM 15516
 --------------------------------------------------
 
 [[fatal-errors]
