Fix some broken links.

docs/concepts/architecture.md

@@ -31,7 +31,8 @@ and usage policies across the service mesh and collects telemetry data from
 proxies and istio-managed services alike. The Istio proxy extracts request
 level attributes that are then evaluated by the mixer. More info on the
 attribute extraction and policy evaluation can be found
-[here](../reference/attributes.md). The mixer includes a flexible plugin model enabling
+[here]({{site.baseurl}}/docs/reference/attribute-vocabulary.html). The mixer
+includes a flexible plugin model enabling
 it to interface to a variety of host environments and configured backends,
 abstracting the proxy and Istio-managed services from these details.
 
@@ -46,7 +47,7 @@ of the underlying platform. In addition, [traffic management rules](../reference
 (i.e. generic layer-4 rules and layer-7 HTTP/gRPC routing rules)
 can be programmed at runtime via the Istio Manager.
 
-<img src="${{site.baseurl}}/img/arch.svg" alt="The overall architecture of an Istio-based service." />
+<img src="{{site.baseurl}}/img/arch.svg" alt="The overall architecture of an Istio-based service." />
 {% endcapture %}
 
 {% include templates/concept.md %}

docs/concepts/attributes.md

@@ -30,7 +30,7 @@ determined by the set of attribute producers being used in the deployment. The p
 is the proxy, although specialized mixer adapters and services can also introduce attributes.
 
 The common baseline set of attributes available in most Istio deployments is defined
-[here]({{site.baseurl}}/docs/reference/attributes.html). 
+[here]({{site.baseurl}}/docs/reference/attribute-vocabulary.html). 
 
 {% endcapture %}
 

docs/home/contribute/using-page-templates.md

@@ -72,7 +72,7 @@ To use ...
 </pre>
 {% endraw %}
 
-Here's an example of a published topic that uses the concept template: [TBD]({{site.baseurl}}/docs/concepts/TBD.html)
+[Here's]({{site.baseurl}}/docs/concepts/mixer.html) an example of a published topic that uses the concept template.
 
 ## Task template
 
@@ -218,7 +218,7 @@ Here's something interesting about the code you ran in the preceding steps.
 </pre>
 {% endraw %}
 
-Here's an example of a published topic that uses the tutorial template: [TBD]({{site.baseurl}}/docs/tutorials/TBD.html)
+[Here's]({{site.baseurl}}/docs/tutorials/TBD.html) an example of a published topic that uses the tutorial template.
 
 ## Sample template
 

docs/home/contribute/writing-a-new-topic.md

@@ -64,8 +64,9 @@ For example, the topic with title
 has filename `tbd.md`. You don't need to put
 "Istio" in the filename, because "Istio" is already in the
 URL for the topic, for example:
-
-       http://istio.io/docs/tasks/tbd.html
+```
+http://istio.io/docs/tasks/tbd.html
+```
 
 ## Updating the front matter
 

docs/reference/attribute-vocabulary.md

@@ -8,7 +8,7 @@ type: markdown
 ---
 
 Attributes are a central concept used throughout Istio. You can find a description of what attributes are
-and what they are used for [here]({{site.baseurl}}/docs/concepts/attributes.md).
+and what they are used for [here]({{site.baseurl}}/docs/concepts/attributes.html).
 
 A given Istio deployment has a fixed vocabulary of attributes that it understands. The specific vocabulary is
 determined by the set of attribute producers being used in the deployment. The primary attribute producer in Istio