fixing all links for good

docs/guides/mixer.md

@@ -34,6 +34,6 @@ to different backend systems that deliver core control-plane functionality, such
 enable the mixer to expose a single consistent control API, independent of the backends in use. The exact set of adapters
 used at runtime is determined through configuration.
 
-<img src="{{site.baseurl}}/img/adapters.svg" alt="Mixer and its adapters.">
+<img src="../../img/adapters.svg" alt="Mixer and its adapters.">
 
 <div id="toc" class="toc mobile-toc"></div>

docs/guides/model.md

@@ -34,7 +34,7 @@ way to subdivide service instances by versions (`v1`, `v2`) or environment
 versions: they could be iterative changes to the same service, deployed in
 different environments (prod, staging, dev, etc.). Common scenarios where
 this occurs include A/B testing, canary rollouts, etc. Istio
-[routing rules]({{site.baseurl}}/docs/reference/rule-dsl.md) can refer to the service versions, to provide
+[routing rules](../reference/rule-dsl.md) can refer to the service versions, to provide
 additional control over traffic between services.
 
 **Tags** Each version of a service can be differentiated by a unique set of
@@ -71,7 +71,7 @@ The actual choice of the service version is determined dynamically by the
 Istio Proxy based on the routing rules set forth by the operator. This
 model enables the application code to decouple itself from the
 evolution of its dependent services, while providing other benefits as well
-(see [mixer]({{site.baseurl}}/docs/guides/mixer.md)). Routing rules allow the proxy to select a version based on
+(see [mixer](mixer.md)). Routing rules allow the proxy to select a version based on
 criterion such as (headers, url, etc.), tags associated with
 source/destination and/or by weights assigned to each version.
 

docs/reference/istioctl.md

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

docs/reference/rule-dsl.md

@@ -67,7 +67,7 @@ There are two types of rules in Istio, **Route Rules**,
 which control request routing, and **Destination Policies**,
 which specify policies, for example, circuit breakers, that control requests for a destination service.
 
-Istio rules can be set and displayed using the [istioctl CLI]({{site.baseurl}}/docs/reference/istioctl.md).
+Istio rules can be set and displayed using the [istioctl CLI](istioctl.md).
 For example, the above rule can be set using the following command:
 ```bash
 $ cat <<EOF | istioctl create