diff --git a/nats_server/monitoring.md b/nats_server/monitoring.md
index d259ead..84b8559 100644
--- a/nats_server/monitoring.md
+++ b/nats_server/monitoring.md
@@ -15,10 +15,10 @@ Example:
```sh
$ nats-server -m 8222
-[4528] 2015/08/19 20:09:58.572939 [INF] Starting gnatsd version 0.8.0
-[4528] 2015/08/19 20:09:58.573007 [INF] Starting http monitor on port 8222
-[4528] 2015/08/19 20:09:58.573071 [INF] Listening for client connections on 0.0.0.0:4222
-[4528] 2015/08/19 20:09:58.573090 [INF] gnatsd is ready
+[4528] 2019/06/01 20:09:58.572939 [INF] Starting nats-server version 2.0.0
+[4528] 2019/06/01 20:09:58.573007 [INF] Starting http monitor on port 8222
+[4528] 2019/06/01 20:09:58.573071 [INF] Listening for client connections on 0.0.0.0:4222
+[4528] 2019/06/01 20:09:58.573090 [INF] nats-server is ready
```
To test, run `nats-server -m 8222`, then go to http://localhost:8222/
@@ -29,7 +29,7 @@ The following sections describe each supported monitoring endpoint: `varz`, `con
### /varz
-The endpoint http://localhost:8222/varz reports various general statistics.
+The endpoint http://localhost:8222/varz reports various general statistics.
```json
{
@@ -182,4 +182,4 @@ $.getJSON('http://localhost:8222/connz?callback=?', function(data) {
## Monitoring Tools
-In addition to writing custom monitoring tools, you can monitor nats-server in Prometheus. The [Prometheus NATS Exporter](https://github.com/nats-io/prometheus-nats-exporter) allows you to configure the metrics you want to observe and store in Prometheus. There's a sample [Grafana](https://grafana.com) dashboard that you can use to visualize the server metrics.
\ No newline at end of file
+In addition to writing custom monitoring tools, you can monitor nats-server in Prometheus. The [Prometheus NATS Exporter](https://github.com/nats-io/prometheus-nats-exporter) allows you to configure the metrics you want to observe and store in Prometheus. There's a sample [Grafana](https://grafana.com) dashboard that you can use to visualize the server metrics.