diff options
| author | Carlos O'Ryan <coryan@google.com> | 2017-07-01 19:26:42 (GMT) |
|---|---|---|
| committer | Carlos O'Ryan <coryan@google.com> | 2017-07-01 19:26:42 (GMT) |
| commit | 1dde1eed381a68af1e1a2ea477c26b3b1ead716b (patch) | |
| tree | 763120d57d5f31e0e4e30a95ccb7c3d55d486a61 /googlemock/docs | |
| parent | 280b22708c014bd29a51eee5982e941231c7925f (diff) | |
| download | googletest-1dde1eed381a68af1e1a2ea477c26b3b1ead716b.zip googletest-1dde1eed381a68af1e1a2ea477c26b3b1ead716b.tar.gz googletest-1dde1eed381a68af1e1a2ea477c26b3b1ead716b.tar.bz2 | |
Fix typos too s/destoyed/destroyed/
Diffstat (limited to 'googlemock/docs')
| -rw-r--r-- | googlemock/docs/v1_5/CookBook.md | 4 | ||||
| -rw-r--r-- | googlemock/docs/v1_6/CookBook.md | 4 | ||||
| -rw-r--r-- | googlemock/docs/v1_7/CookBook.md | 4 |
3 files changed, 6 insertions, 6 deletions
diff --git a/googlemock/docs/v1_5/CookBook.md b/googlemock/docs/v1_5/CookBook.md index 6da89fc..f85bc3b 100644 --- a/googlemock/docs/v1_5/CookBook.md +++ b/googlemock/docs/v1_5/CookBook.md @@ -2081,12 +2081,12 @@ versus ## Forcing a Verification ## -When it's being destoyed, your friendly mock object will automatically +When it's being destroyed, your friendly mock object will automatically verify that all expectations on it have been satisfied, and will generate [Google Test](http://code.google.com/p/googletest/) failures if not. This is convenient as it leaves you with one less thing to worry about. That is, unless you are not sure if your mock object will -be destoyed. +be destroyed. How could it be that your mock object won't eventually be destroyed? Well, it might be created on the heap and owned by the code you are diff --git a/googlemock/docs/v1_6/CookBook.md b/googlemock/docs/v1_6/CookBook.md index 46a2ea1..5224661 100644 --- a/googlemock/docs/v1_6/CookBook.md +++ b/googlemock/docs/v1_6/CookBook.md @@ -2212,12 +2212,12 @@ MockFoo::~MockFoo() {} ## Forcing a Verification ## -When it's being destoyed, your friendly mock object will automatically +When it's being destroyed, your friendly mock object will automatically verify that all expectations on it have been satisfied, and will generate [Google Test](http://code.google.com/p/googletest/) failures if not. This is convenient as it leaves you with one less thing to worry about. That is, unless you are not sure if your mock object will -be destoyed. +be destroyed. How could it be that your mock object won't eventually be destroyed? Well, it might be created on the heap and owned by the code you are diff --git a/googlemock/docs/v1_7/CookBook.md b/googlemock/docs/v1_7/CookBook.md index 6002407..94a9a48 100644 --- a/googlemock/docs/v1_7/CookBook.md +++ b/googlemock/docs/v1_7/CookBook.md @@ -2240,12 +2240,12 @@ MockFoo::~MockFoo() {} ## Forcing a Verification ## -When it's being destoyed, your friendly mock object will automatically +When it's being destroyed, your friendly mock object will automatically verify that all expectations on it have been satisfied, and will generate [Google Test](http://code.google.com/p/googletest/) failures if not. This is convenient as it leaves you with one less thing to worry about. That is, unless you are not sure if your mock object will -be destoyed. +be destroyed. How could it be that your mock object won't eventually be destroyed? Well, it might be created on the heap and owned by the code you are |