1 files changed, 40 insertions, 40 deletions
diff --git a/www/source.html b/www/source.html
index a92fdb5..86a3bda 100755
--- a/www/source.html
+++ b/www/source.html
@@ -29,53 +29,53 @@
           <p>
             For non-Mac platforms, and for MacOSX building with CMake (not Xcode), you should check out your sources to adhere to
             the following directory structure:
-            <pre><tt>  
-                  llvm
-                  |
-                  `-- tools
-                      |
-                      +-- clang
-                      |
-                      `-- lldb
-                </tt></pre>
+            <pre><tt>  
+                  llvm
+                  |
+                  `-- tools
+                      |
+                      +-- clang
+                      |
+                      `-- lldb
+                </tt></pre>
           </p>
-          <p>
-            For MacOSX building from Xcode, simply checkout LLDB and then build from Xcode.  The Xcode project will
-            automatically detect that it is a fresh checkout, and checkout LLVM and clang automatically.  Unlike other
-            platforms / build systems, it will use the following directory structure.
-            <pre><tt>  
-                  lldb
-                  |
-                  `-- llvm
-                      |
-                      +-- tools
-                          |
-                          `-- clang
-                </tt>
-            </pre>
-            So updating your checkout will consist of updating lldb, llvm, and clang in these locations.
-          </p>
-          <p>
-            Refer to the <a href="build.html">Build Instructions</a> for more detailed instructions on how to build for a particular
-            platform / build system combination.
+          <p>
+            For MacOSX building from Xcode, simply checkout LLDB and then build from Xcode.  The Xcode project will
+            automatically detect that it is a fresh checkout, and checkout LLVM and clang automatically.  Unlike other
+            platforms / build systems, it will use the following directory structure.
+            <pre><tt>  
+                  lldb
+                  |
+                  `-- llvm
+                      |
+                      +-- tools
+                          |
+                          `-- clang
+                </tt>
+            </pre>
+            So updating your checkout will consist of updating lldb, llvm, and clang in these locations.
+          </p>
+          <p>
+            Refer to the <a href="build.html">Build Instructions</a> for more detailed instructions on how to build for a particular
+            platform / build system combination.
           </p>
         </div>
 			</div>
 			<div class="post">
 				<h1 class ="postheader">Contributing to LLDB</h1>
 				<div class="postcontent">
-          <p>
-            Please refer to the <a href="http://llvm.org/docs/DeveloperPolicy.html">LLVM Developer Policy</a>
-            for information about authoring and uploading a patch.  LLDB differs from the LLVM Developer Policy in
-            the following respects.
-            <ul>
-              <li>Coding conventions.  Refer to <a href="lldb-coding-conventions.html">LLDB Coding Conventions</a>.</li>
-              <li>
-                Test infrastructure.  It is still important to submit tests with your patches, but LLDB uses a different
-                system for tests.  Refer to the lldb/test folder on disk for examples of how to write tests.
-              </li>
-            </ul>
-            For anything not explicitly listed here, assume that LLDB follows the LLVM policy.
+          <p>
+            Please refer to the <a href="http://llvm.org/docs/DeveloperPolicy.html">LLVM Developer Policy</a>
+            for information about authoring and uploading a patch.  LLDB differs from the LLVM Developer Policy in
+            the following respects.
+            <ul>
+              <li>Coding conventions.  Refer to <a href="lldb-coding-conventions.html">LLDB Coding Conventions</a>.</li>
+              <li>
+                Test infrastructure.  It is still important to submit tests with your patches, but LLDB uses a different
+                system for tests.  Refer to the lldb/test folder on disk for examples of how to write tests.
+              </li>
+            </ul>
+            For anything not explicitly listed here, assume that LLDB follows the LLVM policy.
           </p>
         </div>
 				<div class="postfooter"></div>