Merge pull request #193 from nats-io/fix-broken-links

Fix broken links (found using this method: http://bit.ly/2gv62GN)

content/documentation/faq.md

@@ -48,7 +48,7 @@ The NATS server (`gnatsd`) is written in Go. There is client support for a wide
 
 ### <a name="maintainer"></a>Who maintains NATS?
 
-NATS is sponsored and supported by Apcera, the trusted application platform company founded by Derek Collison. The Apcera 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](/documentation/download/) page for the complete list, and links to the relevant source repositories and documentation.
+NATS is sponsored and supported by Apcera, the trusted application platform company founded by Derek Collison. The Apcera 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](/download/) page for the complete list, and links to the relevant source repositories and documentation.
 
 ### <a name="clients"></a>What client support exists for NATS?
 

content/documentation/index.md

@@ -24,7 +24,7 @@ There are several [client libraries](/download/) for NATS. Apcera actively maint
 
 You can write your own client in any language you choose. NATS provides a simple, [text-based protocol](/documentation/internals/nats-protocol/) that makes [writing clients](/documentation/internals/nats-guide) a breeze.
 
-## NATS design goals
+## <a name="design-goals"></a>NATS design goals
 
 The core principles underlying NATS are performance, scalability, and ease-of-use. Based on these principles, NATS is designed around the following core features:
 

content/documentation/server/gnatsd-intro.md

@@ -32,7 +32,7 @@ A fully configured NATS server is provided as a [Docker image](/documentation/se
 
 ## Clustering
 
-One of the [design goals](/documentation/index/) of NATS is that it be always on and available like a dial tone. To implement this design goal, NATS provides mechanisms for [clustering servers](/documentation/server/gnatsd-cluster/) to achieve resiliency and high availability.
+One of the [design goals](/documentation/#design-goals) of NATS is that it be always on and available like a dial tone. To implement this design goal, NATS provides mechanisms for [clustering servers](/documentation/server/gnatsd-cluster/) to achieve resiliency and high availability.
 
 ## Auto-Pruning
 

content/documentation/server/gnatsd-usage.md

@@ -24,7 +24,7 @@ To install the NATS server:
 go get github.com/nats-io/gnatsd
 ```
 
-Refer to the [NATS installation tutorial](/documentation/tutorials/nats-gnatsd) for more detailed instructions.
+Refer to the [NATS installation tutorial](/documentation/tutorials/gnatsd-install/) for more detailed instructions.
 
 ## Start up
 

content/documentation/streaming/nats-streaming-protocol.md

@@ -11,7 +11,7 @@ category = "internals"
 
 # NATS streaming protocol
 
-The NATS streaming protocol sits atop the core [NATS protocol](../nats-protocol) and uses [Google's protocol buffers](https://developers.google.com/protocol-buffers/).  Protocol buffer messages are marshalled into bytes and published as NATS messages on specific subjects described below.  In communicating with the NATS Streaming Server, The NATS [request/reply](../../concepts/nats-req-rep) pattern is used for all protocol messages that have a corresponding reply.
+The NATS streaming protocol sits atop the core [NATS protocol](/documentation/internals/nats-protocol) and uses [Google's protocol buffers](https://developers.google.com/protocol-buffers/).  Protocol buffer messages are marshalled into bytes and published as NATS messages on specific subjects described below.  In communicating with the NATS Streaming Server, The NATS [request/reply](/documentation/concepts/nats-req-rep) pattern is used for all protocol messages that have a corresponding reply.
 
 ## NATS streaming protocol conventions
 

content/documentation/tutorials/gnatsd-docker.md

@@ -12,7 +12,7 @@ category = "tutorials"
 
 # Run NATS Server Docker Image
 
-In this tutorial you run the [NATS server Docker image](https://hub.docker.com/_/nats/). The Docker image provides an instance of the [NATS Server](/server/gnatsd-intro/). Apcera actively maintains and supports the gnatsd Docker image. The NATS image is only 3 MB in size.
+In this tutorial you run the [NATS server Docker image](https://hub.docker.com/_/nats/). The Docker image provides an instance of the [NATS Server](/documentation/server/gnatsd-intro/). Apcera actively maintains and supports the gnatsd Docker image. The NATS image is only 3 MB in size.
 
 ## Prerequisite