From 791ebec45bcdcdf07a85de0a3f671cdb7a576bc7 Mon Sep 17 00:00:00 2001 From: Sean Silva Date: Wed, 14 Nov 2012 23:15:51 +0000 Subject: docs: Improve typographical correctness. git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@167998 91177308-0d34-0410-b5e6-96231b3b80d8 --- docs/TestingGuide.rst | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) (limited to 'docs') diff --git a/docs/TestingGuide.rst b/docs/TestingGuide.rst index 7ca49ceac0..ad78d0f4e0 100644 --- a/docs/TestingGuide.rst +++ b/docs/TestingGuide.rst @@ -479,7 +479,7 @@ The CHECK: and CHECK-NOT: directives both take a pattern to match. For 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 @@ Because regular expressions are enclosed with double braces, they are 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 ^^^^^^^^^^^^^^^^^^^ -- cgit v1.2.3