aboutsummaryrefslogtreecommitdiff
path: root/googletest/docs/V1_6_FAQ.md
diff options
context:
space:
mode:
Diffstat (limited to 'googletest/docs/V1_6_FAQ.md')
-rw-r--r--googletest/docs/V1_6_FAQ.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/googletest/docs/V1_6_FAQ.md b/googletest/docs/V1_6_FAQ.md
index 6d5d128a..2b7f7840 100644
--- a/googletest/docs/V1_6_FAQ.md
+++ b/googletest/docs/V1_6_FAQ.md
@@ -989,7 +989,7 @@ you can use the _horrible_ hack of sniffing your executable name
## Google Test defines a macro that clashes with one defined by another library. How do I deal with that? ##
In C++, macros don't obey namespaces. Therefore two libraries that
-both define a macro of the same name will clash if you #include both
+both define a macro of the same name will clash if you `#include` both
definitions. In case a Google Test macro clashes with another
library, you can force Google Test to rename its macro to avoid the
conflict.