TensorFlow: Upstream changes to git.

Changes:
- Docuementation changes.
- Update URL for protobuf submodule.

Base CL: 107345722

1 files changed, 3 insertions, 3 deletions

diff --git a/tensorflow/g3doc/how_tos/new_data_formats/index.md b/tensorflow/g3doc/how_tos/new_data_formats/index.md
index f48b2464a0..2c019c79ec 100644
--- a/tensorflow/g3doc/how_tos/new_data_formats/index.md
+++ b/tensorflow/g3doc/how_tos/new_data_formats/index.md
@@ -94,7 +94,7 @@ helper functions from
 without modifying any arguments.
 
 Next you will create the actual Reader op.  It will help if you are familiar
-with [the adding an op how-to](../adding_an_op/index.md).  The main steps
+with [the adding an op how-to](../../how_tos/adding_an_op/index.md).  The main steps
 are:
 
 *   Registering the op.
@@ -122,7 +122,7 @@ REGISTER_OP("TextLineReader")
 A Reader that outputs the lines of a file delimited by '\n'.
 )doc");
 ```
-    
+
 To define an `OpKernel`, Readers can use the shortcut of descending from
 `ReaderOpKernel`, defined in
 [tensorflow/core/framework/reader_op_kernel.h](https://tensorflow.googlesource.com/tensorflow/+/master/tensorflow/core/framework/reader_op_kernel.h),
@@ -199,7 +199,7 @@ You can see some examples in
 ## Writing an Op for a record format <a class="md-anchor" id="AUTOGENERATED-writing-an-op-for-a-record-format"></a>
 
 Generally this is an ordinary op that takes a scalar string record as input, and
-so follow [the instructions to add an Op](../adding_an_op/index.md).  You may
+so follow [the instructions to add an Op](../../how_tos/adding_an_op/index.md).  You may
 optionally take a scalar string key as input, and include that in error messages
 reporting improperly formatted data.  That way users can more easily track down
 where the bad data came from.