Fix doc linksrefs/pull/1809/head

4 files changed, 5 insertions, 5 deletions

diff --git a/googletest/docs/advanced.md b/googletest/docs/advanced.md
index 8065d19..b8bb5cd 100644
--- a/googletest/docs/advanced.md
+++ b/googletest/docs/advanced.md
@@ -150,7 +150,7 @@ c is 10
 >
 > 1.  If you see a compiler error "no matching function to call" when using
 >     `ASSERT_PRED*` or `EXPECT_PRED*`, please see
->     [this](faq.md#OverloadedPredicate) for how to resolve it.
+>     [this](faq.md#the-compiler-complains-no-matching-function-to-call-when-i-use-assert_pred-how-do-i-fix-it) for how to resolve it.
 > 1.  Currently we only provide predicate assertions of arity <= 5. If you need
 >     a higher-arity assertion, let [us](https://github.com/google/googletest/issues) know.
 
@@ -423,7 +423,7 @@ and you're ready to go.
 
 ### More String Assertions
 
-(Please read the [previous](#AssertThat) section first if you haven't.)
+(Please read the [previous](#asserting-using-gmock-matchers) section first if you haven't.)
 
 You can use the gMock [string matchers](../../googlemock/docs/CheatSheet.md#string-matchers)
 with `EXPECT_THAT()` or `ASSERT_THAT()` to do more string comparison tricks
diff --git a/googletest/docs/faq.md b/googletest/docs/faq.md
index 7d42ff7..5458454 100644
--- a/googletest/docs/faq.md
+++ b/googletest/docs/faq.md
@@ -131,7 +131,7 @@ In August 2008 we had to switch the default death test style from `fast` to
 default. This caused many death tests to slow down. Unfortunately this change
 was necessary.
 
-Please read [Fixing Failing Death Tests](death_test_styles.md) for what you can
+Please read [Fixing Failing Death Tests](advanced.md#death-test-styles) for what you can
 do.
 
 ## I got some run-time errors about invalid proto descriptors when using `ProtocolMessageEquals`. Help!
diff --git a/googletest/docs/primer.md b/googletest/docs/primer.md
index 7ddd00e..a7d4f90 100644
--- a/googletest/docs/primer.md
+++ b/googletest/docs/primer.md
@@ -198,7 +198,7 @@ objects, you should use `ASSERT_EQ`.
 
 When doing pointer comparisons use `*_EQ(ptr, nullptr)` and `*_NE(ptr, nullptr)`
 instead of `*_EQ(ptr, NULL)` and `*_NE(ptr, NULL)`. This is because `nullptr` is
-typed while `NULL` is not. See [FAQ](faq.md#why-does-google-test-support-expect_eqnull-ptr-and-assert_eqnull-ptr-but-not-expect_nenull-ptr-and-assert_nenull-ptr)
+typed while `NULL` is not. See [FAQ](faq.md#why-does-googletest-support-expect_eqnull-ptr-and-assert_eqnull-ptr-but-not-expect_nenull-ptr-and-assert_nenull-ptr)
 for more details.
 
 If you're working with floating point numbers, you may want to use the floating
diff --git a/googletest/docs/samples.md b/googletest/docs/samples.md
index 18dcca3..eebdf37 100644
--- a/googletest/docs/samples.md
+++ b/googletest/docs/samples.md
@@ -1,4 +1,4 @@
-# Googletest Samples {#samples}
+# Googletest Samples
 
 If you're like us, you'd like to look at [googletest
 samples.](https://github.com/google/googletest/tree/master/googletest/samples)