[www] Typo fixes.

Reviewers: clayborg, ki.stfu

Subscribers: tberghammer, danalbert, srhines, lldb-commits

Differential Revision: http://reviews.llvm.org/D12668

llvm-svn: 246969

lldb/www/build.html

@@ -16,7 +16,7 @@
       <!--#include virtual="sidebar.incl"-->
 
       <div id="middle">
-        <h1 class="postheader">Continuous Integraton</h1>
+        <h1 class="postheader">Continuous Integration</h1>
         <div class="postcontent">
           <p>
             The following LLVM buildbots build and test LLDB trunk:
@@ -362,7 +362,7 @@
               In order to debug remote targets running different architectures than your host, you
               will need to compile LLDB (or at least the server component) for the target. While
               the easiest solution is to just compile it locally on the target, this is often not
-              feasable, and in these cases you will need to cross-compile LLDB on your host.
+              feasible, and in these cases you will need to cross-compile LLDB on your host.
             </p>
 
             <p>
@@ -453,7 +453,7 @@
 
             <p>
               Ubuntu already provides the packages necessary to cross-compile LLDB for arm64. It
-              is sufficient to install pacakges gcc-aarch64-linux-gnu, g++-aarch64-linux-gnu,
+              is sufficient to install packages gcc-aarch64-linux-gnu, g++-aarch64-linux-gnu,
               binutils-aarch64-linux-gnu. Then it is possible to prepare the cmake build with the
               following parameters:
             </p>
@@ -485,7 +485,7 @@
             <p>
               If you wanted to build a full version of LLDB and avoid passing
               -DLLDB_DISABLE_PYTHON and other options, you would need to obtain the target
-              versions of the respective libraries. The easiest way to achive this is to use the
+              versions of the respective libraries. The easiest way to achieve this is to use the
               <code>qemu-debootstrap</code> utility, which can prepare a system image using qemu
               and chroot to simulate the target environment. Then you can install the necessary
               packages in this environment (python-dev, libedit-dev, etc.) and point your
@@ -524,7 +524,7 @@
             </code>
 
             <p>
-              Note that the full LLVM build is not functional on android yet, so simply runing
+              Note that the full LLVM build is not functional on android yet, so simply running
               <code>ninja</code> will not work. You will need to manually specify the target you
               want to build: <code>lldb</code>, <code>lldb-server</code>, etc.
             </p>

lldb/www/index.html

@@ -61,7 +61,7 @@
 				   	<ul>
 					   	<li>Up to date language support for C, C++, Objective C</li>
 					   	<li>Multi-line expressions that can declare local variables and types</li>
-					   	<li>Utilitize the JIT for expressions when supported</li>
+					   	<li>Utilize the JIT for expressions when supported</li>
 					   	<li>Evaluate expression Intermediate Representation (IR) when JIT can't be used</li>
 				    </ul>
 				</div>

lldb/www/test.html

@@ -81,7 +81,7 @@
               additional <code>--test-subdir SUBDIR</code> arg.  When
               specified, SUBDIR is relative to the root test directory
               and will limit all parallel test running to that
-              sudirectory's tree of tests.
+              subdirectory's tree of tests.
             </p>
             <p>
               The parallel test runner will run all tests within a
@@ -117,7 +117,7 @@
             <p>
               Currently, running the remote test suite is supported only with
               <code>dotest.py</code> (or <code>dosep.py</code> with a single thread), but we
-              expect this issue to be adressed in the near future.
+              expect this issue to be addressed in the near future.
             </p>
 
           </div>

lldb/www/varformats.html

@@ -990,7 +990,7 @@ def function (valobj,internal_dict):<br/>
                   (i_am_cool) one = x=3<br>
                 </code> </p>
 
-			<p>When defining a named summmary, binding it to one or more types becomes optional.
+			<p>When defining a named summary, binding it to one or more types becomes optional.
 			Even if you bind the named summary to a type, and later change the summary string
 			for that type, the named summary will not be changed by that. You can delete
 			named summaries by using the <code>type summary delete</code> command, as if the