Correct a few more errors.

_docs/concepts/mixer-config.md

@@ -48,7 +48,7 @@ can be added to Istio and be fully manipulated using the same general mechanisms
 
 ## Concepts
 
-Mixer is an attribute processing machine. Requests arrive at Mixer with a set of [*attributes*]({{site.baseurl}}/docs/attributes.html),
+Mixer is an attribute processing machine. Requests arrive at Mixer with a set of [*attributes*]({{site.baseurl}}/docs/concepts/attributes.html),
 and based on these attributes, Mixer generates calls to a variety of backend systems. The set of
 attributes determines which backend systems Mixer calls for a given request and what parameters
 each is given. In order to hide the details of individual backend systems, Mixer uses modules
@@ -354,7 +354,7 @@ Istio can provide a number of strong correctness guarantees of the system's conf
 configuration is accepted into the Istio system, it means the configuration passes a minimum correctness bar. Again, this
 plays the same role as types in a programming language.
 
-- It enables Istio to provide a strongly-typed scripting environment as discussed [here](./mixer.md#scripting)
+- It enables Istio to provide a strongly-typed scripting environment as discussed [here](./mixer.html#scripting)
 
 The different descriptor types are detailed in *TBD*
 
@@ -399,7 +399,7 @@ operator can manipulate which scope.
 
 #### Resolution
 
-When a request arrives, Mixer goes through a number of [request processing phases](./mixer.md#request-phases).
+When a request arrives, Mixer goes through a number of [request processing phases](./mixer.html#request-phases).
 The Resolution phase is concerned with identifying the exact configuration blocks to use in order to
 process the incoming request. For example, a request arriving at Mixer for service A likely has some configuration differences
 with requests arriving for service B. Resolution is about deciding which config to use for a request.

_docs/concepts/mixer.md

@@ -97,7 +97,7 @@ subsequent phases.
 
 - **Attribute Processing**. The third phase takes the total set of attributes
 and produces a set of *adapter parameters*. Attribute processing is initially
-configured through a simple declarative form as described [here]({{site.baseurl}}/docs/mixer-config.html).
+configured through a simple declarative form as described [here](./mixer-config.html).
 
 - **Adapter Dispatching**. The Resolution phase establishes the set of available aspects and the Attribute
 Processing phase creates a set of adapter parameters. The Adapter Dispatching phase invokes the adapters

_docs/reference/contribute/creating-a-pull-request.md

@@ -39,9 +39,9 @@ documentation repository in your GitHub account. The copy is called a *fork*.
 a new branch to use for your contribution.
 
 1. In your new branch, make your changes and commit them. If you want to
-[write a new topic]({{site.baseurl}}/docs/home/contribute/writing-a-new-topic.html),
+[write a new topic]({{site.baseurl}}/docs/reference/contribute/writing-a-new-topic.html),
 choose the
-[page type]({{ site.baseurl }}/docs/home/contribute/using-page-templates.html)
+[page type]({{ site.baseurl }}/docs/reference/contribute/using-page-templates.html)
 that is the best fit for your content.
 
 ## Submitting a pull request

_docs/reference/contribute/index.md

@@ -1,17 +1,13 @@
 ---
 category: Reference
-title: Overview
-index: true
-
-parent: Contributing to the Docs
-order: 0
+title: Contributing to the Docs
 
 bodyclass: docs
 layout: docs
 type: markdown
 ---
 
-# Contributing
+# Contributing to the Istio Docs
 
 This section teaches you how to contribute to the Istio documentation effort.
 

_docs/reference/contribute/staging-your-changes.md

@@ -16,7 +16,7 @@ to the Istio documentation.
 ## Before you begin
 
 Create a fork of the Istio documentation repository as described in
-[Creating a Doc Pull Request]({{site.baseurl}}/docs/home/contribute/creating-a-pull-request.html).
+[Creating a Doc Pull Request]({{site.baseurl}}/docs/reference/contribute/creating-a-pull-request.html).
 
 ## Staging from your GitHub account
 

_docs/reference/contribute/style-guide.md

@@ -18,8 +18,8 @@ propose changes to this document in a pull request.
 
 For additional information on creating new content for the Istio
 docs, follow the instructions on
-[Using Page Templates]({{site.baseurl}}/docs/home/contribute/using-page-templates.html) and
-[Creating a Doc Pull Request]({{site.baseurl}}/docs/home/contribute/creating-a-pull-request.html).
+[Using Page Templates]({{site.baseurl}}/docs/reference/contribute/using-page-templates.html) and
+[Creating a Doc Pull Request]({{site.baseurl}}/docs/reference/contribute/creating-a-pull-request.html).
 
 ## Formatting standards
 

_docs/reference/contribute/writing-a-new-topic.md

@@ -15,7 +15,7 @@ This page shows how to create a new Istio documentation topic.
 ## Before you begin
 
 You first need to create a fork of the Istio documentation repository as described in
-[Creating a Doc Pull Request]({{site.baseurl}}/docs/home/contribute/creating-a-pull-request.html).
+[Creating a Doc Pull Request]({{site.baseurl}}/docs/reference/contribute/creating-a-pull-request.html).
 
 ## Choosing a page type
 
@@ -53,7 +53,7 @@ is the best fit for your content:
   </tr>
 </table>
 
-Each page type has a [template]({{site.baseurl}}/docs/home/contribute/using-page-templates.html)
+Each page type has a [template]({{site.baseurl}}/docs/reference/contribute/using-page-templates.html)
 that you can use as you write your topic. Using templates helps ensure consistency among topics of a given type.
 
 ## Naming a topic

_docs/reference/istioctl.md

@@ -42,8 +42,8 @@ _kubernetes specific_
 
 # Policy and Rule types
 
-* **route-rule** Describes a rule for routing network traffic.  See [Route Rules](rule-dsl.md#route-rules) for details on routing rules.
-* **destination-policy** Describes a policy for traffic destinations.  See [Destination Policies](rule-dsl.md#destination-policies) for details on destination policies.
+* **route-rule** Describes a rule for routing network traffic.  See [Route Rules]({{site.baseurl}}/docs/reference/rules-and-traffic-management.html#route-rules) for details on routing rules.
+* **destination-policy** Describes a policy for traffic destinations. See [Destination Policies]({{site.baseurl}}/docs/reference/rules-and-traffic-management.html#destination-policies) for details on destination policies.
 
 # Examples of common operations
 

_docs/samples/bookinfo.md

@@ -113,7 +113,7 @@ _Note: The following instructions assume that you have access to a kubernetes cl
 
    Notice that the `istioctl kube-inject` command is used to modify the `bookinfo.yaml`
    file before creating the deployments. This injects the istio runtime proxy
-   into kubernetes resources as documented [here](../reference/istioctl.md#kube-inject).
+   into kubernetes resources as documented [here](../reference/istioctl.html#kube-inject).
    Consequently, all of the microservices are now packaged with an Istio sidecar
    that manages incoming and outgoing calls for the service. The updated diagram looks
    like this:

_sass/modules/_doc-nav.scss

@@ -76,6 +76,7 @@
 	// Add caret to current page
 	.current:before{
 		content: '> ';
+		color: $popBrandColor;
 	}
 
 	.doc-side-nav-title {

faq/index.html

@@ -61,7 +61,7 @@ bodyclass: faq
                     <li class="submenu">
                         <h6 class="arrow-r">What is the roadmap?</h6>
                         <div class="submenu-content">
-                            <p>See <a href="{{site.baseurl}}/docs/home/roadmap.html">here</a> for info on our release roadmap.
+                            <p>See <a href="{{site.baseurl}}/docs/reference/roadmap.html">here</a> for info on our release roadmap.
                         </div>
                     </li>
                 </ul>