summaryrefslogtreecommitdiffstats
path: root/googlemock/docs/for_dummies.md
diff options
context:
space:
mode:
Diffstat (limited to 'googlemock/docs/for_dummies.md')
-rw-r--r--googlemock/docs/for_dummies.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/googlemock/docs/for_dummies.md b/googlemock/docs/for_dummies.md
index e11c18d..93cf06f 100644
--- a/googlemock/docs/for_dummies.md
+++ b/googlemock/docs/for_dummies.md
@@ -213,7 +213,7 @@ specific domain much better than `Foo` does.
Once you have a mock class, using it is easy. The typical work flow is:
1. Import the gMock names from the `testing` namespace such that you can use
- them unqualified (You only have to do it once per file. Remember that
+ them unqualified (You only have to do it once per file). Remember that
namespaces are a good idea.
2. Create some mock objects.
3. Specify your expectations on them (How many times will a method be called?