style(monitoring): fix up monitoring doc

Author: slack

src/managing-workflow/platform-monitoring.md

@@ -1,6 +1,7 @@
 # Platform Monitoring
 
 ## Description
+
 With the release of Workflow Beta4 we now include a monitoring stack for introspection on a running Kubernetes cluster. The stack includes 4 components:
 
 * [Telegraf](https://docs.influxdata.com/telegraf/v0.12/) - Metrics collection daemon written by team behind InfluxDB.
@@ -36,21 +37,22 @@ With the release of Workflow Beta4 we now include a monitoring stack for introsp
 
 ### Grafana
 
-We expose Grafana through the router using [service annotations](https://github.com/deis/router#how-it-works). This
-allows users to access the Grafana UI by accessing `grafana.mydomain.com`. While  we provide a default username/password
-of `admin/admin` this can be overridden at any time by setting the following environment variables in
+Deis Workflow exposes Grafana through the router using [service annotations](https://github.com/deis/router#how-it-works). This
+allows users to access the Grafana UI at `http://grafana.mydomain.com`. The default username/password of
+`admin/admin` can be overridden at any time by setting the following environment variables in
 `$CHART_HOME/workspace/workflow-$WORKFLOW_RELEASE/manifests/deis-monitor-grafana-rc.yaml`: `GRAFANA_USER` and
 `GRAFANA_PASSWD`.
 
-It will preload several dashboards that we've created to help operators get started with monitoring their Kubernetes and
-Workflow installations. Each dashboard is meant to be a starting place for the operator and is not representative of all
-the dashboards needed to monitor a production installation.
+Grafana will preload several dashboards to help operators get started with monitoring Kubernetes and Deis Workflow.
+These dashboards are meant as starting points and don't include every item that might be desirable to monitor in a
+production installation.
 
-We are currently not writing the data to the host file system or to long term storage. Therefore, if the Grafana
-instance dies you will lose all custom and modified dashboards. It is recommended that you export your dashboards and
-store them in version control until a solution is implemented for long term storage.
+Deis Workflow monitoring does not currently write data to the host filesystem or to long-term storage. If the Grafana
+instance fails, modified dashboards are lost. Until there is a solution to persist this, export dashboards and store
+them separately in version control.
 
 ### InfluxDB
+
 As of the Beta4 release InfluxDB is writing data to the host disk, however, if the InfluxDB pod dies and comes back on
 another host the data will not be recovered. We intend to fix this in a future release. The InfluxDB Admin UI is also
 exposed through the router allowing users to access the query engine by going to `influx.mydomain.com`. You will need to
@@ -65,6 +67,7 @@ You can choose to not expose the Influx UI and API to the world by updating
 following line - `router.deis.io/routable: "true"`.
 
 ### Telegraf
+
 Telegraf is the metrics collection daemon used within the monitoring stack. It will collect and send the following metrics to InfluxDB:
 
 * System level metrics such as CPU, Load Average, Memory, Disk, and Network stats
@@ -74,9 +77,11 @@ Telegraf is the metrics collection daemon used within the monitoring stack. It w
 It is possible to send these metrics to other endpoints besides InfluxDB. For more information please consult the following [file](https://github.com/deis/monitor/blob/master/telegraf/rootfs/config.toml.tpl)
 
 ### Stdout-Metrics
+
 Stdout-Metrics is a custom tool built by the Deis team to provide metrics that are reported via standard out - like Nginx. It consumes the log stream from FluentD filtering out messages that are not from the [Deis Router](https://github.com/deis/router). Once it finds a message it can parse it will turn that into a metric and send it directly to InfluxDB.
 
 ### Customizing
+
 Each of these components allows for customization via environment variables. If you would like to learn more please visit the following github repositories:
 
 * [stdout-metrics](https://github.com/deis/stdout-metrics)