diff options
| author | Jonathan Wakely <jwakely@redhat.com> | 2017-09-27 13:31:13 +0100 |
|---|---|---|
| committer | Jonathan Wakely <jwakely@redhat.com> | 2017-09-27 13:31:13 +0100 |
| commit | b70cf1a663ad30f77ab9867095a87d3d5429450d (patch) | |
| tree | ac98f22d19193c60ceecba1aca0c7d824d32f77f /googletest/docs | |
| parent | f1a87d73fc604c5ab8fbb0cc6fa9a86ffd845530 (diff) | |
| download | googletest-b70cf1a663ad30f77ab9867095a87d3d5429450d.tar.gz googletest-b70cf1a663ad30f77ab9867095a87d3d5429450d.zip | |
Use gender-neutral pronouns in comments and docs
Diffstat (limited to 'googletest/docs')
| -rw-r--r-- | googletest/docs/AdvancedGuide.md | 2 | ||||
| -rw-r--r-- | googletest/docs/FAQ.md | 4 |
2 files changed, 3 insertions, 3 deletions
diff --git a/googletest/docs/AdvancedGuide.md b/googletest/docs/AdvancedGuide.md index 1076496d..e4dd94de 100644 --- a/googletest/docs/AdvancedGuide.md +++ b/googletest/docs/AdvancedGuide.md @@ -1263,7 +1263,7 @@ known as <i>abstract tests</i>. As an example of its application, when you are designing an interface you can write a standard suite of abstract tests (perhaps using a factory function as the test parameter) that all implementations of the interface are expected to pass. When -someone implements the interface, he can instantiate your suite to get +someone implements the interface, they can instantiate your suite to get all the interface-conformance tests for free. To define abstract tests, you should organize your code like this: diff --git a/googletest/docs/FAQ.md b/googletest/docs/FAQ.md index 76c23727..c39b6254 100644 --- a/googletest/docs/FAQ.md +++ b/googletest/docs/FAQ.md @@ -102,9 +102,9 @@ Then every user of your machine can write tests without recompiling Google Test. This seemed like a good idea, but it has a -got-cha: every user needs to compile his tests using the _same_ compiler +got-cha: every user needs to compile their tests using the _same_ compiler flags used to compile the installed Google Test libraries; otherwise -he may run into undefined behaviors (i.e. the tests can behave +they may run into undefined behaviors (i.e. the tests can behave strangely and may even crash for no obvious reasons). Why? Because C++ has this thing called the One-Definition Rule: if |
