summaryrefslogtreecommitdiffstats
path: root/llvm/docs/CommandGuide/FileCheck.pod
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
commit75b5d27b84fd062aaa7ee81667c2b579981c107c (patch)
tree584ff280855b7f364f34c84c5611c233e0ea894a /llvm/docs/CommandGuide/FileCheck.pod
parente3dc1707b530dd264417390f1510c99c166eb103 (diff)
downloadbcm5719-llvm-75b5d27b84fd062aaa7ee81667c2b579981c107c.tar.gz
bcm5719-llvm-75b5d27b84fd062aaa7ee81667c2b579981c107c.zip
Spelling fix: consequtive -> consecutive.
llvm-svn: 125563
Diffstat (limited to 'llvm/docs/CommandGuide/FileCheck.pod')
-rw-r--r--llvm/docs/CommandGuide/FileCheck.pod2
1 files changed, 1 insertions, 1 deletions
diff --git a/llvm/docs/CommandGuide/FileCheck.pod b/llvm/docs/CommandGuide/FileCheck.pod
index 8a8eddfde45..3ccaa63e176 100644
--- a/llvm/docs/CommandGuide/FileCheck.pod
+++ b/llvm/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:
OpenPOWER on IntegriCloud