summaryrefslogtreecommitdiffstats
path: root/googlemock/docs
diff options
context:
space:
mode:
authorAbseil Team <absl-team@google.com>2019-07-29 18:54:32 (GMT)
committerGennadiy Civil <misterg@google.com>2019-07-29 19:36:36 (GMT)
commit3821ecd5733a58990d4c1ebf962218088746e9e4 (patch)
tree1e1cc0fa053e00fe3f3bfda7ad8aba2514ed2598 /googlemock/docs
parenta45c24ac1878932e0dc5fbc0d78a699befd386d3 (diff)
downloadgoogletest-3821ecd5733a58990d4c1ebf962218088746e9e4.zip
googletest-3821ecd5733a58990d4c1ebf962218088746e9e4.tar.gz
googletest-3821ecd5733a58990d4c1ebf962218088746e9e4.tar.bz2
Googletest export
Fix broken link. PiperOrigin-RevId: 260548004
Diffstat (limited to 'googlemock/docs')
-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 b39a0c8..5551cd8 100644
--- a/googlemock/docs/for_dummies.md
+++ b/googlemock/docs/for_dummies.md
@@ -595,8 +595,8 @@ In this example, we test that `Foo()` calls the three expected functions in the
order as written. If a call is made out-of-order, it will be an error.
(What if you care about the relative order of some of the calls, but not all of
-them? Can you specify an arbitrary partial order? The answer is ... yes! If you
-are impatient, the details can be found [here](#PartialOrder).)
+them? Can you specify an arbitrary partial order? The answer is ... yes! The
+details can be found [here](cook_book.md#OrderedCalls).)
#### All Expectations Are Sticky (Unless Said Otherwise) {#StickyExpectations}