aboutsummaryrefslogtreecommitdiffstats
path: root/googlemock/docs/ForDummies.md
diff options
context:
space:
mode:
authorGennadiy Civil <misterg@google.com>2019-04-18 09:44:23 -0400
committerGennadiy Civil <misterg@google.com>2019-04-18 09:44:24 -0400
commita0d60bed4d0ea17c7130cda16776b9bc8a929d7b (patch)
treeb04bb7a474c3b1b61e23896402b4510307657812 /googlemock/docs/ForDummies.md
parent9f893b99598b1f0725dc8b92037f0d9f53095b90 (diff)
parent3829b84e9927a2a77a7634a8e7b010cc57095e1b (diff)
downloadgoogletest-a0d60bed4d0ea17c7130cda16776b9bc8a929d7b.tar.gz
googletest-a0d60bed4d0ea17c7130cda16776b9bc8a929d7b.tar.bz2
googletest-a0d60bed4d0ea17c7130cda16776b9bc8a929d7b.zip
Merge pull request #2170 from ngie-eign:issue-2146-ver2
PiperOrigin-RevId: 244069956
Diffstat (limited to 'googlemock/docs/ForDummies.md')
-rw-r--r--googlemock/docs/ForDummies.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/googlemock/docs/ForDummies.md b/googlemock/docs/ForDummies.md
index f4eba809..e2a430f8 100644
--- a/googlemock/docs/ForDummies.md
+++ b/googlemock/docs/ForDummies.md
@@ -17,7 +17,7 @@ If all this seems too abstract for you, don't worry - the most important thing t
Using Google Mock involves three basic steps:
1. Use some simple macros to describe the interface you want to mock, and they will expand to the implementation of your mock class;
- 1. Create some mock objects and specify their expectations and behavior using an intuitive syntax;
+ 1. Create some mock objects and specify its expectations and behavior using an intuitive syntax;
1. Exercise code that uses the mock objects. Google Mock will catch any violation of the expectations as soon as it arises.
# Why Google Mock? #