Tweaks to get_started.html, especially for Windows developers

[amccarth]

Summary

1. Add note about preserving FL line endings on Windows. Failure to do so causes about 30 tests to fail.
2. Check out is two words when used as a verb.

[yaron.keren]

AFAIK the eol type is decided by svn based the svn:eol-style property, so as long the files were checked in correctly and you do not override it specifically while svn checkout, it just works.
Did you encounter problems with eol ?

[amccarth]

Like many folks, I use git-svn, and I had git's core.autocrlf config set to
true, which worked fine when working on LLDB (which I've been doing for
about a year). The first time I tried to run Clang tests, however, I got
about 30 failures because of the CR+LFs.

My opinion is that the tests are too fragile if they can't handle platform
native line separators, but until we fix that, the note seems useful.

Aid.

[yaron.keren]

Ah, OK, I am using regular svn and thus did not counter this problem.
Could you detail this exactly, the problem happens when using git-svn with core.autocrlf config=true but not with svn?
LGTM with this addition.

cfe/trunk/www/get_started.html

<ul>
     <li>Note also that Python is needed for running the test suite.
       Get it at: <a href="http://www.python.org/download">
       http://www.python.org/download</a></li>
     <li>Standard build process uses CMake. Get it at:
       <a href="http://www.cmake.org/download">
       http://www.cmake.org/download</a></li>
   </ul>
 
-  <li>Checkout LLVM:
+  <li>Check out LLVM:
   <ul>
     <li>Change directory to where you want the llvm directory placed.</li>
     <li><tt>svn co http://llvm.org/svn/llvm-project/llvm/trunk llvm</tt></li>
   </ul>
   </li>
-  <li>Checkout Clang:
+  <li>Check out Clang:
   <ul>
     <li><tt>cd llvm/tools</tt></li>
     <li><tt>svn co http://llvm.org/svn/llvm-project/cfe/trunk clang</tt></li>
     <li><tt>cd ../..</tt></li>
   </ul>
   </li>
-  <li>Checkout extra Clang Tools: (optional)
+  <li>Check out extra Clang tools: (optional)
   <ul>
     <li><tt>cd llvm/tools/clang/tools</tt></li>
     <li><tt>svn co http://llvm.org/svn/llvm-project/clang-tools-extra/trunk
         extra</tt></li>
     <li><tt>cd ../../../..</tt></li>
   </ul>
   </li>
-  <li>Checkout Compiler-RT (optional):
+  <li>Check out Compiler-RT (optional):
   <ul>
     <li><tt>cd llvm/projects</tt></li>
     <li><tt>svn co http://llvm.org/svn/llvm-project/compiler-rt/trunk
         compiler-rt</tt></li>
     <li><tt>cd ../..</tt></li>
   </ul>
   </li>
-  <li>Checkout libcxx: (only required to build and run Compiler-RT tests on OS X, optional otherwise)
+  <li>Check out libcxx: (only required to build and run Compiler-RT tests on OS X, optional otherwise)
   <ul>
     <li><tt>cd llvm/projects</tt></li>
     <li><tt>svn co http://llvm.org/svn/llvm-project/libcxx/trunk
         libcxx</tt></li>
     <li><tt>cd ../..</tt></li>
   </ul>
   </li>
   <li>Build LLVM and Clang:
<ol>
   </ul>
   </li>
 </ol>
 
 <p>If you encounter problems while building Clang, make sure that your LLVM
 checkout is at the same revision as your Clang checkout. LLVM's interfaces
 change over time, and mismatched revisions are not expected to work
 together.</p>
-  
 <h3>Simultaneously Building Clang and LLVM:</h3>
 
 <p>Once you have checked out Clang into the llvm source tree it will build along
 with the rest of <tt>llvm</tt>. To build all of LLVM and Clang together all at
 once simply run <tt>make</tt> from the root LLVM directory.</p>
-    
 <p><em>Note:</em> Observe that Clang is technically part of a separate
 Subversion repository. As mentioned above, the latest Clang sources are tied to
 the latest sources in the LLVM tree. You can update your toplevel LLVM project
 and all (possibly unrelated) projects inside it with <tt><b>make
 update</b></tt>. This will run <tt>svn update</tt> on all subdirectories related
 to subversion. </p>
 
 <h3 id="buildWindows">Using Visual Studio</h3>
<li><b>GnuWin32 tools</b>
         (Note that the grep from MSYS or Cygwin doesn't work with the tests
         because of embedded double-quotes in the search strings.  The GNU
         grep does work in this case.)
         Get them from <a href="http://getgnuwin32.sourceforge.net/">
         http://getgnuwin32.sourceforge.net/</a>.</li>
   </ul>
   </li>
 
-  <li>Checkout LLVM:
+  <li>Check out LLVM:
   <ul>
     <li><tt>svn co http://llvm.org/svn/llvm-project/llvm/trunk llvm</tt></li>
   </ul>
   </li>
-  <li>Checkout Clang:
+  <li>Check out Clang:
   <ul>
      <li><tt>cd llvm\tools</tt>
      <li><tt>svn co http://llvm.org/svn/llvm-project/cfe/trunk clang</tt></li>
   </ul>
+  <p><em>Note</em>:  Some Clang tests are sensitive to the line endings.  Ensure
+     that checking out the files does not convert LF line endings to CR+LF.
+     If you use git-svn, make sure your <tt>core.autocrlf</tt> setting is false.</p>
   </li>
   <li>Run CMake to generate the Visual Studio solution and project files:
   <ul>
     <li><tt>cd ..\..</tt>  (back to where you started)</li>
     <li><tt>mkdir build</tt> (for building without polluting the source dir)</li>
     <li><tt>cd build</tt></li>
     <li>If you are using Visual Studio 2013:  <tt>cmake -G "Visual Studio 12" ..\llvm</tt></li>
     <li>See the <a href="http://www.llvm.org/docs/CMake.html">LLVM CMake guide</a> for