rename REG -> REGISTER to make it explicit in the doc. <tt>ify some stuff.

git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@82892 91177308-0d34-0410-b5e6-96231b3b80d8

1 files changed, 8 insertions, 8 deletions

diff --git a/docs/TestingGuide.html b/docs/TestingGuide.html
index 8e1041e..43c414d 100644
--- a/docs/TestingGuide.html
+++ b/docs/TestingGuide.html
@@ -671,17 +671,17 @@ simple example:</p>
 <div class="doc_code">
 <pre>
 ; CHECK: test5:
-; CHECK:    notw	<b>[[REG:%[a-z]+]]</b>
-; CHECK:    andw	{{.*}}<b>[[REG]]</b>
+; CHECK:    notw	<b>[[REGISTER:%[a-z]+]]</b>
+; CHECK:    andw	{{.*}}<b>[[REGISTER]]</b>
 </pre>
 </div>
 
-<p>The first check line matches a regex (%[a-z]+) and captures it into the
-variables "REG".  The second line verifies that whatever is in REG occurs later
-in the file after an "andw".  FileCheck variable references are always contained
-in [[ ]] pairs, are named, and their names can be formed with the regex
-"[a-zA-Z][a-zA-Z0-9]*".  If a colon follows the name, then it is a definition of
-the variable, if not, it is a use.</p>
+<p>The first check line matches a regex (<tt>%[a-z]+</tt>) and captures it into
+the variables "REGISTER".  The second line verifies that whatever is in REGISTER
+occurs later in the file after an "andw".  FileCheck variable references are
+always contained in <tt>[[ ]]</tt> pairs, are named, and their names can be
+formed with the regex "<tt>[a-zA-Z][a-zA-Z0-9]*</tt>".  If a colon follows the
+name, then it is a definition of the variable, if not, it is a use.</p>
 
 <p>FileCheck variables can be defined multiple times, and uses always get the
 latest value.  Note that variables are all read at the start of a "CHECK" line