diff options
author | Duncan Sands <baldrick@free.fr> | 2011-02-15 09:23:02 +0000 |
---|---|---|
committer | Duncan Sands <baldrick@free.fr> | 2011-02-15 09:23:02 +0000 |
commit | ab4c366274a582dd8146b2820c6b999cad5fce36 (patch) | |
tree | e001ba4266c9828f1ef1d35dd1df18f3d1a633fe /docs/CommandGuide | |
parent | ab8f3fd2e1c07231deffba8ea4ecd06ac559afe4 (diff) |
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/CommandGuide')
-rw-r--r-- | docs/CommandGuide/FileCheck.pod | 2 |
1 files changed, 1 insertions, 1 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: |