message: Updating hyperlinks.
diff: @@ -524,7 +524,7 @@ REGISTER\_OP("ZeroOut")
  </code></pre>
  (Note that the set of [attribute types](#attr-types) is different from the
  -@{$dims_types$tensor types} used for inputs and outputs.)
  +@{tf.DType$tensor types} used for inputs and outputs.)
  Your kernel can then access this attr in its constructor via the `context`
  parameter:
  @@ -599,7 +599,7 @@ define an attr with constraints, you can use the following `<attr-type-expr>`s:
  * `{<type1>, <type2>}`: The value is of type `type`, and must be one of
  `<type1>` or `<type2>`, where `<type1>` and `<type2>` are supported
  - @{$dims_types#data-types$tensor types}. You don't specify
  + @{tf.DType$tensor types}. You don't specify
  that the type of the attr is `type`. This is implied when you have a list of
  types in `{...}`. For example, in this case the attr `t` is a type that must
  be an `int32`, a `float`, or a `bool`:
  @@ -681,7 +681,8 @@ REGISTER_OP("AttrDefaultExampleForAllTypes")
  .Attr("l_int: list(int) = [2, 3, 5, 7]");
  ```
  -Note in particular that the values of type `type` use @{$dims_types#data-types$the `DT_*` names for the types}.
  +Note in particular that the values of type `type`
  +use @{tf.DType$the `DT_*` names for the types}.
  #### Polymorphism {#polymorphism}
  @@ -1011,7 +1012,7 @@ expressions:
  `string`). This specifies a single tensor of the given type.
  See
  - @{$dims_types#data-types$the list of supported Tensor types}.
  + @{tf.DType$the list of supported Tensor types}.
  ```c++
  REGISTER_OP("BuiltInTypesExample")
  @@ -1054,7 +1055,7 @@ expressions:
  * For a sequence of tensors with the same type: `<number> * <type>`, where
  `<number>` is the name of an [Attr](#attrs) with type `int`. The `<type>` can
  either be
  - @{$dims_types#data-types$a specific type like `int32` or `float`},
  + @{tf.DType$a specific type like `int32` or `float`},
  or the name of an attr with type `type`. As an example of the first, this
  op accepts a list of `int32` tensors:
  