Fix formatting in AdvancedGuide.md
Put occurrences of "#include" in a code span so they are not interpreted as headers. Other documents were not broken because the #include was not at the start of the line, but put them in code spans anyway just in case the text gets refilled in the future.
This commit is contained in:
		@@ -221,7 +221,7 @@ your build script.
 | 
			
		||||
### Avoiding Macro Name Clashes ###
 | 
			
		||||
 | 
			
		||||
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.
 | 
			
		||||
 
 | 
			
		||||
		Reference in New Issue
	
	Block a user