aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorChris Lattner <sabre@nondot.org>2008-07-20 04:22:06 +0000
committerChris Lattner <sabre@nondot.org>2008-07-20 04:22:06 +0000
commitd9069d1cbb28b4aa76cd0b0f7879885470429612 (patch)
tree10b591688d379a3e89e50736d312a5b1e8298bdb
parent9039a69ab9b44f9e5431c050c22f01164b85fcfa (diff)
Add a space, ted apparently has philosophical problems with spaces ;-)
git-svn-id: https://llvm.org/svn/llvm-project/cfe/trunk@53808 91177308-0d34-0410-b5e6-96231b3b80d8
-rw-r--r--www/StaticAnalysisUsage.html6
1 files changed, 3 insertions, 3 deletions
diff --git a/www/StaticAnalysisUsage.html b/www/StaticAnalysisUsage.html
index d050012f73..2d97a9b9b3 100644
--- a/www/StaticAnalysisUsage.html
+++ b/www/StaticAnalysisUsage.html
@@ -92,7 +92,7 @@ during a project build.</p>
</pre>
<p> In the first case <tt>scan-build</tt> analyzes the code of a project built
-with <tt>make</tt>, andin the second case <tt>scan-build</tt> analyzes a project
+with <tt>make</tt>, and in the second case <tt>scan-build</tt> analyzes a project
built using <tt>xcodebuild</tt>. In general, the format is: </p>
<pre>
@@ -100,7 +100,7 @@ built using <tt>xcodebuild</tt>. In general, the format is: </p>
</pre>
<p> Operationally, <tt>scan-build</tt> literally runs <command> with all of the
-subsequent options passed to it. For example</p>
+subsequent options passed to it. For example:</p>
<pre>
$ scan-build make <b>-j4</b>
@@ -225,7 +225,7 @@ what it's doing; two <b>-v</b> options emit more information. Redirecting the
output of <tt>scan-build</tt> to a text file (make sure to redirect standard
error) is useful for filing bug reports against <tt>scan-build</tt> or the
analyzer, as we can see the exact options (and files) passed to the analyzer.
-For more comprehendible logs, don't perform a parallel build.</p>
+For more comprehensible logs, don't perform a parallel build.</p>
<h2 id="Debugging">Debugging the Analyzer</h2>