diff --git a/review/developer/cl-descriptions.md b/review/developer/cl-descriptions.md
index 2975d7db..702dbd24 100644
--- a/review/developer/cl-descriptions.md
+++ b/review/developer/cl-descriptions.md
@@ -1,6 +1,6 @@
 # Writing good CL descriptions
 
-[TOC]
+
 
 A CL description is a public record of **what** change is being made and **why**
 it was made. It will become a permanent part of our version control history, and
diff --git a/review/developer/handling-comments.md b/review/developer/handling-comments.md
index 9bcc6be2..3f69603e 100644
--- a/review/developer/handling-comments.md
+++ b/review/developer/handling-comments.md
@@ -1,6 +1,6 @@
 # How to handle reviewer comments
 
-[TOC]
+
 
 When you've sent a CL out for review, it's likely that your reviewer will
 respond with several comments on your CL. Here are some useful things to know
diff --git a/review/developer/index.md b/review/developer/index.md
index 6538d365..6f3af553 100644
--- a/review/developer/index.md
+++ b/review/developer/index.md
@@ -1,7 +1,5 @@
 # The CL author's guide to getting through code review
 
-go/cl-author
-
 The pages in this section contain best practices for developers going through
 code review. These guidelines should help you get through reviews faster and
 with higher-quality results. You don't have to read them all, but they are
diff --git a/review/developer/small-cls.md b/review/developer/small-cls.md
index c5ac41ab..d7e5a0e6 100644
--- a/review/developer/small-cls.md
+++ b/review/developer/small-cls.md
@@ -1,6 +1,6 @@
 # Small CLs
 
-[TOC]
+
 
 ## Why Write Small CLs? {#why}
 
diff --git a/review/emergencies.md b/review/emergencies.md
index 580c34ce..582562f9 100644
--- a/review/emergencies.md
+++ b/review/emergencies.md
@@ -4,7 +4,7 @@ Sometimes there are emergency CLs that must pass through the entire code review
 process as quickly as
 possible.
 
-[TOC]
+
 
 ## What Is An Emergency? {#what}
 
diff --git a/review/index.md b/review/index.md
index 658e8f03..86d3823c 100644
--- a/review/index.md
+++ b/review/index.md
@@ -10,7 +10,7 @@ At Google we use code review to maintain the quality of our code and products.
 This documentation is the canonical description of Google's code review
 processes and policies.
 
-[TOC]
+
 
 This page is an overview of our code review process. There are two other large
 documents that are a part of this guide:
diff --git a/review/reviewer/comments.md b/review/reviewer/comments.md
index 1a316c6d..71693d2e 100644
--- a/review/reviewer/comments.md
+++ b/review/reviewer/comments.md
@@ -1,6 +1,6 @@
 # How to write code review comments
 
-[TOC]
+
 
 ## Summary
 
diff --git a/review/reviewer/index.md b/review/reviewer/index.md
index 2ce3d7d0..29f234e7 100644
--- a/review/reviewer/index.md
+++ b/review/reviewer/index.md
@@ -1,7 +1,5 @@
 # How to do a code review
 
-go/code-reviewer
-
 The pages in this section contain recommendations on the best way to do code
 reviews, based on long experience. All together they represent one complete
 document, broken up into many separate sections. You don't have to read them
diff --git a/review/reviewer/looking-for.md b/review/reviewer/looking-for.md
index c42b582e..875d6331 100644
--- a/review/reviewer/looking-for.md
+++ b/review/reviewer/looking-for.md
@@ -1,6 +1,6 @@
 # What to look for in a code review
 
-[TOC]
+
 
 Note: Always make sure to take into account
 [The Standard of Code Review](standard.md) when considering each of these
diff --git a/review/reviewer/navigate.md b/review/reviewer/navigate.md
index 98acf9cd..4517a16d 100644
--- a/review/reviewer/navigate.md
+++ b/review/reviewer/navigate.md
@@ -1,6 +1,6 @@
 # Navigating a CL in review
 
-[TOC]
+
 
 ## Summary
 
diff --git a/review/reviewer/pushback.md b/review/reviewer/pushback.md
index 3cd11c89..54aa6ad4 100644
--- a/review/reviewer/pushback.md
+++ b/review/reviewer/pushback.md
@@ -1,6 +1,6 @@
 # Handling pushback in code reviews
 
-[TOC]
+
 
 Sometimes a developer will push back on a code review. Either they will disagree
 with your suggestion or they will complain that you are being too strict in
diff --git a/review/reviewer/speed.md b/review/reviewer/speed.md
index 47462b17..a4a9242b 100644
--- a/review/reviewer/speed.md
+++ b/review/reviewer/speed.md
@@ -1,6 +1,6 @@
 # Speed of Code Reviews
 
-[TOC]
+
 
 ## Why Should Code Reviews Be Fast? {#why}
 
diff --git a/review/reviewer/standard.md b/review/reviewer/standard.md
index 4e2b8264..81b72fe5 100644
--- a/review/reviewer/standard.md
+++ b/review/reviewer/standard.md
@@ -1,6 +1,6 @@
 # The Standard of Code Review
 
-[TOC]
+
 
 The primary purpose of code review is to make sure that the overall
 code health of Google's code