[llvm-commits] [llvm] r167998 - /llvm/trunk/docs/TestingGuide.rst

[Sean Silva]

Author: silvas
Date: Wed Nov 14 17:15:51 2012
New Revision: 167998

URL: http://llvm.org/viewvc/llvm-project?rev=167998&view=rev
Log:
docs: Improve typographical correctness.

Modified:
    llvm/trunk/docs/TestingGuide.rst

Modified: llvm/trunk/docs/TestingGuide.rst
URL: http://llvm.org/viewvc/llvm-project/llvm/trunk/docs/TestingGuide.rst?rev=167998&r1=167997&r2=167998&view=diff
==============================================================================
--- llvm/trunk/docs/TestingGuide.rst (original)
+++ llvm/trunk/docs/TestingGuide.rst Wed Nov 14 17:15:51 2012
@@ -479,7 +479,7 @@
 most uses of FileCheck, fixed string matching is perfectly sufficient.
 For some things, a more flexible form of matching is desired. To support
 this, FileCheck allows you to specify regular expressions in matching
-strings, surrounded by double braces: **{{yourregex}}**. Because we want
+strings, surrounded by double braces: ``{{yourregex}}``. Because we want
 to use fixed string matching for a majority of what we do, FileCheck has
 been designed to support mixing and matching fixed string matching with
 regular expressions. This allows you to write things like this:
@@ -495,7 +495,7 @@
 visually distinct, and you don't need to use escape characters within
 the double braces like you would in C. In the rare case that you want to
 match double braces explicitly from the input, you can use something
-ugly like **{{[{][{]}}** as your pattern.
+ugly like ``{{[{][{]}}`` as your pattern.
 
 FileCheck Variables
 ^^^^^^^^^^^^^^^^^^^