summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorAbseil Team <absl-team@google.com>2019-08-20 12:59:37 -0400
committerXiaoyi Zhang <zhangxy@google.com>2019-08-21 17:13:26 -0400
commitd1ad644db4b9f5c89a12be6265282cd622c23b5a (patch)
treef3798e378aa2e7ff3136494d47ad365580ac91e5
parentc9ccac7cb7345901884aabf5d1a786cfa6e2f397 (diff)
downloadgoogletest-git-d1ad644db4b9f5c89a12be6265282cd622c23b5a.tar.gz
Googletest export
Update broken links. PiperOrigin-RevId: 264405918
-rw-r--r--googlemock/docs/for_dummies.md4
1 files changed, 2 insertions, 2 deletions
diff --git a/googlemock/docs/for_dummies.md b/googlemock/docs/for_dummies.md
index 0e7db8df..e11c18d9 100644
--- a/googlemock/docs/for_dummies.md
+++ b/googlemock/docs/for_dummies.md
@@ -483,7 +483,7 @@ the *default* action for the function every time (unless, of course, you have a
What can we do inside `WillOnce()` besides `Return()`? You can return a
reference using `ReturnRef(*variable*)`, or invoke a pre-defined function, among
-[others](#ActionList).
+[others](cook_book.md#using-actions).
**Important note:** The `EXPECT_CALL()` statement evaluates the action clause
only once, even though the action may be performed many times. Therefore you
@@ -561,7 +561,7 @@ overloaded). This makes any calls to the method expected. This is not necessary
for methods that are not mentioned at all (these are "uninteresting"), but is
useful for methods that have some expectations, but for which other calls are
ok. See
-[Understanding Uninteresting vs Unexpected Calls](#uninteresting-vs-unexpected).
+[Understanding Uninteresting vs Unexpected Calls](cook_book.md#uninteresting-vs-unexpected).
#### Ordered vs Unordered Calls {#OrderedCalls}