Merge pull request #23 from nats-io/broken_link_updates

update broken links

SUMMARY.md

@@ -3,6 +3,7 @@
 * [Introduction](README.md)
 * [What's New in 2.0](whats_new/whats_new_20.md)
 * [FAQ](faq.md)
+* [nats.io](https://nats.io)
 
 ## Concepts
 

faq.md

@@ -45,7 +45,7 @@ The NATS server \(`nats-server`\) is written in Go. There is client support for
 
 ### Who maintains NATS?
 
-NATS is sponsored and supported by Synadia, a company founded by Derek Collison. The Synadia team maintain the NATS server, as well as the Go, Ruby, Node.js, C, C\#, Java and several other client libraries. Our very active user community also contributes client libraries for several other implementation languages. Please see the [download](https://github.com/nats-io/nats-site/tree/c42c46a7c6b8669e66e28419887d2f8dd29aa502/download/README.md) page for the complete list, and links to the relevant source repositories and documentation.
+NATS is sponsored and supported by Synadia, a company founded by Derek Collison. The Synadia team maintain the NATS server, as well as the Go, Ruby, Node.js, C, C\#, Java and several other client libraries. Our very active user community also contributes client libraries for several other implementation languages. Please see the [download](https://nats.io/download) page for the complete list, and links to the relevant source repositories and documentation.
 
 ### What client support exists for NATS?
 
@@ -83,7 +83,7 @@ This form of distributed queueing is done in real time, and messages are not per
 
 NATS maintains and constantly updates the interest graph \(subjects and their subscribers\) in real time. Do not think of it as a "directory" that is aggregated over time. The interest graph dynamic, and will change constantly as publishers and subscribers come and go.
 
-If you are determined to gather this information, it can be indirectly derived at any instant in time by polling the monitoring endpoint for /connz and /routez. See [Server Monitoring](https://github.com/nats-io/nats-site/tree/c42c46a7c6b8669e66e28419887d2f8dd29aa502/documentation/managing_the_server/monitoring/README.md) for more information.
+If you are determined to gather this information, it can be indirectly derived at any instant in time by polling the monitoring endpoint for /connz and /routez. See [Server Monitoring](/nats-server/monitoring.md/) for more information.
 
 ### Does NATS support subject wildcards?
 

nats_admin/slow_consumers.md

@@ -1,6 +1,6 @@
 ## Slow Consumers
 
-To support resiliency and high availability, NATS provides built-in mechanisms to automatically prune the registered listener interest graph that is used to keep track of subscribers, including slow consumers and lazy listeners. NATS automatically handles a slow consumer. If a client is not processing messages quick enough, the NATS server cuts it off. To support scaling, NATS provides for auto-pruning of client connections. If a subscriber does not respond to ping requests from the server within the [ping-pong interval](/nats-protocol/nats-protocol.md#PINGPONG), the client is cut off (disconnected). The client will need to have reconnect logic to reconnect with the server.
+To support resiliency and high availability, NATS provides built-in mechanisms to automatically prune the registered listener interest graph that is used to keep track of subscribers, including slow consumers and lazy listeners. NATS automatically handles a slow consumer. If a client is not processing messages quick enough, the NATS server cuts it off. To support scaling, NATS provides for auto-pruning of client connections. If a subscriber does not respond to ping requests from the server within the [ping-pong interval](/nats-protocol.md#PINGPONG), the client is cut off (disconnected). The client will need to have reconnect logic to reconnect with the server.
 
 # Slow Consumers
 

nats_protocol/nats-protocol-demo.md

@@ -2,7 +2,7 @@
 
 The virtues of the NATS protocol manifest quickly when you experience how easy it is to use NATS. Because the NATS protocol is text-based, you can use NATS across virtually any platform or language. In the following demo we use [Telnet](https://en.wikipedia.org/wiki/Telnet).
 
-On the wire you can publish and subscribe using a simple [set of protocol commands](/documentation/internals/nats-protocol/).
+On the wire you can publish and subscribe using a simple [set of protocol commands](nats-protocol.md).
 
 ## Instructions
 

nats_server/installation.md

@@ -6,7 +6,7 @@ NATS philosophy is simplicity. Installation is just decompressing a zip file and
 - [Kubernetes](#installing-on-kubernetes-with-nats-operator)
 - [Package Manager](#installing-via-a-package-manager)
 - [Release Zip](#downloading-a-release-build)
-- [Development Build](installing-from-the-source)
+- [Development Build](#installing-from-the-source)
 
 
 ### Installing via Docker

nats_server/monitoring.md

@@ -182,4 +182,4 @@ $.getJSON('http://localhost:8222/connz?callback=?', function(data) {
 
 ## Monitoring Tools
 
-In addition to writing custom monitoring tools, you can nats-server into 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 Prometheous. There's a sample [Grafana](https://grafana.com) dashboard that you can use to visualize the server metrics.
+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.