Regen configure

[oota-llvm.git] / docs / CommandGuide / lit.pod

diff --git a/docs/CommandGuide/lit.pod b/docs/CommandGuide/lit.pod
index 246fc66aa6d20051064d146f5825de57640115b5..989a5d7acb51bc54c82b45b54ddce04a57376162 100644 (file)
--- a/docs/CommandGuide/lit.pod
+++ b/docs/CommandGuide/lit.pod
@@ -49,13 +49,13 @@ Show the B<lit> help message.
 
 =item B<-j> I<N>, B<--threads>=I<N>
 
-Run I<N> tests in parallel. By default, this is automatically chose to match the
-number of detected available CPUs.
+Run I<N> tests in parallel. By default, this is automatically chosen to match
+the number of detected available CPUs.
 
 =item B<--config-prefix>=I<NAME>
 
 Search for I<NAME.cfg> and I<NAME.site.cfg> when searching for test suites,
-instead I<lit.cfg> and I<lit.site.cfg>.
+instead of I<lit.cfg> and I<lit.site.cfg>.
 
 =item B<--param> I<NAME>, B<--param> I<NAME>=I<VALUE>
 
@@ -237,7 +237,7 @@ creating a new B<lit> testing implementation, or extending an existing one.
 
 B<lit> proper is primarily an infrastructure for discovering and running
 arbitrary tests, and to expose a single convenient interface to these
-tests. B<lit> itself doesn't contain know how to run tests, rather this logic is
+tests. B<lit> itself doesn't know how to run tests, rather this logic is
 defined by I<test suites>.
 
 =head2 TEST SUITES
@@ -253,8 +253,8 @@ files passed on the command line. You can use B<--show-suites> to display the
 discovered test suites at startup.
 
 Once a test suite is discovered, its config file is loaded. Config files
-themselves are just Python modules which will be executed. When the config file
-is executed, two important global variables are predefined:
+themselves are Python modules which will be executed. When the config file is
+executed, two important global variables are predefined:
 
 =over