summaryrefslogtreecommitdiff
path: root/docs/TestingGuide.rst
diff options
context:
space:
mode:
authorEli Bendersky <eliben@google.com>2013-03-22 16:09:06 +0000
committerEli Bendersky <eliben@google.com>2013-03-22 16:09:06 +0000
commitbe67aa52a8fca4ea33dd59512d8bea9e2a45be2e (patch)
treee33fd0b9c69d64667c3a1e032ab694fe8644d132 /docs/TestingGuide.rst
parent21675c8ab0e2ec788caed6c0d88b20f6e5ebdbda (diff)
downloadllvm-be67aa52a8fca4ea33dd59512d8bea9e2a45be2e.tar.gz
llvm-be67aa52a8fca4ea33dd59512d8bea9e2a45be2e.tar.bz2
llvm-be67aa52a8fca4ea33dd59512d8bea9e2a45be2e.tar.xz
fix small doc typo
git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@177737 91177308-0d34-0410-b5e6-96231b3b80d8
Diffstat (limited to 'docs/TestingGuide.rst')
-rw-r--r--docs/TestingGuide.rst2
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/TestingGuide.rst b/docs/TestingGuide.rst
index 1fddaa3326..79cedee764 100644
--- a/docs/TestingGuide.rst
+++ b/docs/TestingGuide.rst
@@ -234,7 +234,7 @@ everything enclosed as one value.
In general, you should strive to keep your RUN lines as simple as possible,
using them only to run tools that generate textual output you can then examine.
-The recommended way to examine output to figure out if the test passes it using
+The recommended way to examine output to figure out if the test passes is using
the :doc:`FileCheck tool <CommandGuide/FileCheck>`. *[The usage of grep in RUN
lines is deprecated - please do not send or commit patches that use it.]*