summaryrefslogtreecommitdiff
path: root/docs
diff options
context:
space:
mode:
authorDuncan Sands <baldrick@free.fr>2011-02-15 09:23:02 +0000
committerDuncan Sands <baldrick@free.fr>2011-02-15 09:23:02 +0000
commitab4c366274a582dd8146b2820c6b999cad5fce36 (patch)
treee001ba4266c9828f1ef1d35dd1df18f3d1a633fe /docs
parentab8f3fd2e1c07231deffba8ea4ecd06ac559afe4 (diff)
downloadllvm-ab4c366274a582dd8146b2820c6b999cad5fce36.tar.gz
llvm-ab4c366274a582dd8146b2820c6b999cad5fce36.tar.bz2
llvm-ab4c366274a582dd8146b2820c6b999cad5fce36.tar.xz
Spelling fix: consequtive -> consecutive.
git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@125563 91177308-0d34-0410-b5e6-96231b3b80d8
Diffstat (limited to 'docs')
-rw-r--r--docs/CommandGuide/FileCheck.pod2
-rw-r--r--docs/TestingGuide.html2
-rw-r--r--docs/WritingAnLLVMPass.html2
3 files changed, 3 insertions, 3 deletions
diff --git a/docs/CommandGuide/FileCheck.pod b/docs/CommandGuide/FileCheck.pod
index 8a8eddfde4..3ccaa63e17 100644
--- a/docs/CommandGuide/FileCheck.pod
+++ b/docs/CommandGuide/FileCheck.pod
@@ -133,7 +133,7 @@ both 32-bit and 64-bit code generation.
=head2 The "CHECK-NEXT:" directive
Sometimes you want to match lines and would like to verify that matches
-happen on exactly consequtive lines with no other lines in between them. In
+happen on exactly consecutive lines with no other lines in between them. In
this case, you can use CHECK: and CHECK-NEXT: directives to specify this. If
you specified a custom check prefix, just use "<PREFIX>-NEXT:". For
example, something like this works as you'd expect:
diff --git a/docs/TestingGuide.html b/docs/TestingGuide.html
index 4d14fe4a8c..b048b72485 100644
--- a/docs/TestingGuide.html
+++ b/docs/TestingGuide.html
@@ -604,7 +604,7 @@ name="FileCheck-CHECK-NEXT">The "CHECK-NEXT:" directive</a></div>
<div class="doc_text">
<p>Sometimes you want to match lines and would like to verify that matches
-happen on exactly consequtive lines with no other lines in between them. In
+happen on exactly consecutive lines with no other lines in between them. In
this case, you can use CHECK: and CHECK-NEXT: directives to specify this. If
you specified a custom check prefix, just use "&lt;PREFIX&gt;-NEXT:". For
example, something like this works as you'd expect:</p>
diff --git a/docs/WritingAnLLVMPass.html b/docs/WritingAnLLVMPass.html
index 10668b365f..edc8631d0a 100644
--- a/docs/WritingAnLLVMPass.html
+++ b/docs/WritingAnLLVMPass.html
@@ -1474,7 +1474,7 @@ results as soon as they are no longer needed.</li>
<li><b>Pipeline the execution of passes on the program</b> - The
<tt>PassManager</tt> attempts to get better cache and memory usage behavior out
of a series of passes by pipelining the passes together. This means that, given
-a series of consequtive <a href="#FunctionPass"><tt>FunctionPass</tt></a>'s, it
+a series of consecutive <a href="#FunctionPass"><tt>FunctionPass</tt></a>'s, it
will execute all of the <a href="#FunctionPass"><tt>FunctionPass</tt></a>'s on
the first function, then all of the <a
href="#FunctionPass"><tt>FunctionPass</tt></a>es on the second function,