[cfe-commits] r99712 - /cfe/trunk/www/analyzer/visual_studio.html

[Kovarththanan Rajaratnam]

Author: krj
Date: Sat Mar 27 03:21:15 2010
New Revision: 99712

URL: http://llvm.org/viewvc/llvm-project?rev=99712&view=rev
Log:
s/Clangify2010.py/clangify2010.py

Modified:
    cfe/trunk/www/analyzer/visual_studio.html

Modified: cfe/trunk/www/analyzer/visual_studio.html
URL: http://llvm.org/viewvc/llvm-project/cfe/trunk/www/analyzer/visual_studio.html?rev=99712&r1=99711&r2=99712&view=diff
==============================================================================
--- cfe/trunk/www/analyzer/visual_studio.html (original)
+++ cfe/trunk/www/analyzer/visual_studio.html Sat Mar 27 03:21:15 2010
@@ -17,7 +17,7 @@
 <h1>clangify2010: Using the Analyzer with Visual Studio 2010</h1>
 
 <p>The Clang Static Analyzer has only limited support right now for Visual
-Studio users. Some users might find the <tt>Clangify2010.py</tt> script useful
+Studio users. Some users might find the <tt>clangify2010.py</tt> script useful
 (described below) for analyzing their projects. It does not provide the same
 functionality as <tt>scan-build</tt> (for example, it does not actually build
 Visual Studio projects to analyze source files nor does it have a UI for viewing
@@ -52,7 +52,7 @@
 href="http://clang.llvm.org/get_started.html">here</a>) in your <tt>PATH</tt>.
 <li>Your project does not have automatically generated intermediate files as
 part of the build step. You can possibly work around this limitation by adding a
-custom pre_analysis function to <tt>Clangify2010.py</tt>.</li>
+custom pre_analysis function to <tt>clangify2010.py</tt>.</li>
 <li>The source files in your project all take the same compiler flags.</li>
 </ul>