aboutsummaryrefslogtreecommitdiffstats
path: root/googlemock/docs
diff options
context:
space:
mode:
authorhyuk.myeong <ant35rookie@gmail.com>2019-10-01 14:24:55 +0900
committerhyuk.myeong <ant35rookie@gmail.com>2019-10-01 14:24:55 +0900
commit51f7396d40585f6d785b7d1218be9319c358092a (patch)
tree648c733af110902e775f2ba0cbace6df8f9ad88f /googlemock/docs
parentdc1ca9ae4c206434e450ed4ff535ca7c20c79e3c (diff)
downloadgoogletest-51f7396d40585f6d785b7d1218be9319c358092a.tar.gz
googletest-51f7396d40585f6d785b7d1218be9319c358092a.tar.bz2
googletest-51f7396d40585f6d785b7d1218be9319c358092a.zip
Fix typo in documents
Diffstat (limited to 'googlemock/docs')
-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 e11c18d9..93cf06f3 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?