Fix some newly broken links. (#1082)

_blog/2017/adapter-model.md

@@ -67,7 +67,10 @@ by the proxy into individual bundles of data that can be routed to different ada
 
 Creating instances generally requires using [attribute expressions]({{home}}/docs/concepts/policy-and-control/mixer-config.html#attribute-expressions). The point of these expressions is to use any attribute or literal value in order to produce a result that can be assigned to an instance’s field.
 
-Every instance field has a type, as defined in the template, every [attribute has a type](https://github.com/istio/api/blob/master/mixer/v1/config/descriptor/value_type.proto), and every attribute expression has a type. You can only assign type-compatible expressions to any given instance fields. For example, you can’t assign an integer expression to a string field.  This kind of strong typing is designed to minimize the risk of creating bogus configurations.
+Every instance field has a type, as defined in the template, every attribute has a
+[type](https://github.com/istio/api/blob/master/policy/v1beta1/value_type.proto), and every attribute expression has a type.
+You can only assign type-compatible expressions to any given instance fields. For example, you can’t assign an integer expression
+to a string field.  This kind of strong typing is designed to minimize the risk of creating bogus configurations.
 
 ## Rules: delivering data to adapters
 

_docs/concepts/policy-and-control/attributes.md

@@ -44,4 +44,4 @@ separator. For example, `request.size` and `source.ip`.
 ## Attribute types
 
 Istio attributes are strongly typed. The supported attribute types are defined by
-[ValueType](https://github.com/istio/api/blob/master/mixer/v1/config/descriptor/value_type.proto).
+[ValueType](https://github.com/istio/api/blob/master/policy/v1beta1/value_type.proto).

_docs/reference/api/istio.mixer.v1.html

@@ -71,7 +71,7 @@ specialized Mixer adapters and services can also generate attributes.</p>
 <a href="{{site.baseurl}}/docs/reference/config/mixer/attribute-vocabulary.html">here</a>.</p>
 
 <p>Attributes are strongly typed. The supported attribute types are defined by
-<a href="https://github.com/istio/api/blob/master/mixer/v1/config/descriptor/value_type.proto">ValueType</a>.
+<a href="https://github.com/istio/api/blob/master/policy/v1beta1/value_type.proto">ValueType</a>.
 Each type of value is encoded into one of the so-called transport types present
 in this message.</p>
 

_docs/reference/config/istio.mixer.v1.config.client.html

@@ -1283,7 +1283,7 @@ specialized Mixer adapters and services can also generate attributes.</p>
 <a href="{{site.baseurl}}/docs/reference/config/mixer/attribute-vocabulary.html">here</a>.</p>
 
 <p>Attributes are strongly typed. The supported attribute types are defined by
-<a href="https://github.com/istio/api/blob/master/mixer/v1/config/descriptor/value_type.proto">ValueType</a>.
+<a href="https://github.com/istio/api/blob/master/policy/v1beta1/value_type.proto">ValueType</a>.
 Each type of value is encoded into one of the so-called transport types present
 in this message.</p>
 

_docs/reference/config/mixer/expression-language.md

@@ -16,7 +16,8 @@ This page describes how to use the Mixer config expression language (CEXL).
 
 ## Background
 
-Mixer configuration uses an expression language (CEXL) to specify match expressions and [mapping expressions]({{mixerConfig}}#attribute-expressions). CEXL expressions map a set of typed [attributes]({{home}}/docs/concepts/policy-and-control/attributes.html) and constants to a typed [value](https://github.com/istio/api/blob/master/mixer/v1/config/descriptor/value_type.proto#L23).
+Mixer configuration uses an expression language (CEXL) to specify match expressions and [mapping expressions]({{mixerConfig}}#attribute-expressions). CEXL expressions map a set of typed [attributes]({{home}}/docs/concepts/policy-and-control/attributes.html) and constants to a typed
+[value](https://github.com/istio/api/blob/master/policy/v1beta1/value_type.proto).
   
 ## Syntax