diff options
author | Abseil Team <absl-team@google.com> | 2020-06-03 15:19:04 (GMT) |
---|---|---|
committer | Gennadiy Rozental <rogeeff@google.com> | 2020-06-05 07:56:49 (GMT) |
commit | 210aab09deef06e64ab82414697abd0d7cb5978a (patch) | |
tree | 8fe5d3f5c6b5d86e70c12f671a5e61a53e910e43 | |
parent | cb44c86c1aaf31b26797728e93acc950c01dbd5b (diff) | |
download | googletest-210aab09deef06e64ab82414697abd0d7cb5978a.zip googletest-210aab09deef06e64ab82414697abd0d7cb5978a.tar.gz googletest-210aab09deef06e64ab82414697abd0d7cb5978a.tar.bz2 |
Googletest export
gMock Cookbook: Slight rewording
Remove "I" because documentation can have multiple authors. And remove unnecessary "guy".
PiperOrigin-RevId: 314533746
-rw-r--r-- | googlemock/docs/cook_book.md | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/googlemock/docs/cook_book.md b/googlemock/docs/cook_book.md index 42e2906..bffbb3c 100644 --- a/googlemock/docs/cook_book.md +++ b/googlemock/docs/cook_book.md @@ -410,8 +410,8 @@ NOTE: `NiceMock` and `StrictMock` only affects *uninteresting* calls (calls of methods with expectations, but they don't match). See [Understanding Uninteresting vs Unexpected Calls](#uninteresting-vs-unexpected). -There are some caveats though (I dislike them just as much as the next guy, but -sadly they are side effects of C++'s limitations): +There are some caveats though (sadly they are side effects of C++'s +limitations): 1. `NiceMock<MockFoo>` and `StrictMock<MockFoo>` only work for mock methods defined using the `MOCK_METHOD` macro **directly** in the `MockFoo` class. |