aboutsummaryrefslogtreecommitdiffstats
path: root/googlemock/docs/CookBook.md
diff options
context:
space:
mode:
authorGennadiy Civil <gennadiycivil@users.noreply.github.com>2017-10-03 10:57:19 -0400
committerGitHub <noreply@github.com>2017-10-03 10:57:19 -0400
commit7b6561c56e353100aca8458d7bc49c4e0119bae8 (patch)
treeac98f22d19193c60ceecba1aca0c7d824d32f77f /googlemock/docs/CookBook.md
parentf1a87d73fc604c5ab8fbb0cc6fa9a86ffd845530 (diff)
parentb70cf1a663ad30f77ab9867095a87d3d5429450d (diff)
downloadgoogletest-7b6561c56e353100aca8458d7bc49c4e0119bae8.tar.gz
googletest-7b6561c56e353100aca8458d7bc49c4e0119bae8.tar.bz2
googletest-7b6561c56e353100aca8458d7bc49c4e0119bae8.zip
Merge pull request #1275 from jwakely/pr/1273
Use gender-neutral pronouns in comments and docs
Diffstat (limited to 'googlemock/docs/CookBook.md')
-rw-r--r--googlemock/docs/CookBook.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/googlemock/docs/CookBook.md b/googlemock/docs/CookBook.md
index 753c6dd3..3d07e68b 100644
--- a/googlemock/docs/CookBook.md
+++ b/googlemock/docs/CookBook.md
@@ -227,7 +227,7 @@ If a mock method has no `EXPECT_CALL` spec but is called, Google Mock
will print a warning about the "uninteresting call". The rationale is:
* New methods may be added to an interface after a test is written. We shouldn't fail a test just because a method it doesn't know about is called.
- * However, this may also mean there's a bug in the test, so Google Mock shouldn't be silent either. If the user believes these calls are harmless, he can add an `EXPECT_CALL()` to suppress the warning.
+ * However, this may also mean there's a bug in the test, so Google Mock shouldn't be silent either. If the user believes these calls are harmless, they can add an `EXPECT_CALL()` to suppress the warning.
However, sometimes you may want to suppress all "uninteresting call"
warnings, while sometimes you may want the opposite, i.e. to treat all