Spelling and grammar corrections.

llvm-svn: 174268

diff --git a/lld/docs/C++11.rst b/lld/docs/C++11.rst
index 4935362..e47a030 100644 (file)
--- a/lld/docs/C++11.rst
+++ b/lld/docs/C++11.rst
@@ -11,7 +11,7 @@ Allowed Features
 ----------------
 
 Allowed features are based on what these compilers support. Features that are ok
-to ommit (such as final or = delete) may be conditionally used via macros.
+to omit (such as final or = delete) may be conditionally used via macros.
 
 * All of the C++11 standard library, including threading and atomics
 * auto
@@ -30,6 +30,6 @@ to ommit (such as final or = delete) may be conditionally used via macros.
 * Range based for loop
 * final via LLVM_FINAL
 
-Note that some of these features may not be fullly or correctly implemented in
+Note that some of these features may not be fully or correctly implemented in
 all compilers. Issues using these features should be added here as they are
 encountered.

diff --git a/lld/docs/Driver.rst b/lld/docs/Driver.rst
index 9f946ae..b65ff94 100644 (file)
--- a/lld/docs/Driver.rst
+++ b/lld/docs/Driver.rst
@@ -22,8 +22,8 @@ ld64, and Microsoft's link.exe.
 Flavors
 -------
 
-Each of these different interfaces is refered to as a flavor. There is also an
-extra flavor for ``lld -core``. This is eqivilent to ``-cc1`` in clang.
+Each of these different interfaces is referred to as a flavor. There is also an
+extra flavor for ``lld -core``. This is equivalent to ``-cc1`` in clang.
 The current flavors are.
 
 * ld
@@ -68,7 +68,7 @@ Adding an Option
 #. If there is no ``lld -core`` option, add the option to
    :file:`lib/Driver/CoreOptions.td`. All ``lld -core`` start with a single -
    and if they have a value, it is joined with a =. ``lld -core`` options should
-   have sensible, non-abbrivated names and should be shared between flavors
+   have sensible, non-abbreviated names and should be shared between flavors
    where possible.
 
 #. Modify the ``{flavor}Driver::transform`` function to transform the added
@@ -96,7 +96,7 @@ Adding a Flavor
 #. Add a tablegen file called :file:`lib/Driver/{flavor}Options.td` that
    describes the options. If the options are a superset of another driver, that
    driver's td file can simply be included. The :file:`{flavor}Options.td` file
-   must also be added to :file:`lib/Driver/CMakeListst.txt`.
+   must also be added to :file:`lib/Driver/CMakeLists.txt`.
 
 #. Add a ``{flavor}::{flavor}OptTable`` as a subclass of
    :cpp:class:`llvm::opt::OptTable` in :file:`lib/Driver/Drivers.cpp`.

diff --git a/lld/docs/design.rst b/lld/docs/design.rst
index 5ab746e..2a79bd0 100644 (file)
--- a/lld/docs/design.rst
+++ b/lld/docs/design.rst
@@ -63,7 +63,7 @@ There are only four different types of atoms:
        * AbsoluteAtom
                This is for embedded support where some stuff is implemented in ROM at
                some fixed address.  This atom has no content.  It is just an address
-               that the Writer needs to fixup any references to point to.
+               that the Writer needs to fix up any references to point to.
 
 
 File Model
@@ -148,7 +148,7 @@ Reader defines the class ReaderOptionsMachO).  This options class is the
 one-and-only way to control how the Reader operates when parsing an input file
 into an Atom graph.  For instance, you may want the Reader to only accept
 certain architectures.  The options class can be instantiated from command
-line options, or it can be subclassed and the ivars programatically set. 
+line options, or it can be subclassed and the ivars programmatically set. 
 
 
 Resolving
@@ -215,7 +215,7 @@ modify or enhance the current lld::File object. Some example Passes are:
 
   * TLV instantiation (Darwin specific)
 
-  * dtrace probe processing (Darwin specific)
+  * DTrace probe processing (Darwin specific)
 
   * compact unwind encoding (Darwin specific)
 
@@ -241,7 +241,7 @@ object.  The writer's job is to create the executable content file wrapper and
 place the content of the atoms into it.
 
 lld uses a plug-in model for writing output files. All concrete writers (e.g.
-ELF, mach-o, etc) are subclasses of the lld::Writer classs.  
+ELF, mach-o, etc) are subclasses of the lld::Writer class.  
 
 Unlike the Reader class which has just one method to instantiate an lld::File,
 the Writer class has multiple methods.  The crucial method is to generate the 
@@ -264,7 +264,7 @@ one-and-only way to control how the Writer operates when producing an output
 file from an Atom graph.  For instance, you may want the Writer to optimize
 the output for certain OS versions, or strip local symbols, etc. The options 
 class can be instantiated from command line options, or it can be subclassed 
-and the ivars programatically set. 
+and the ivars programmatically set. 
 
 
 lld::File representations

diff --git a/lld/docs/getting_started.rst b/lld/docs/getting_started.rst
index 467d0d5..d1efcc0 100644 (file)
--- a/lld/docs/getting_started.rst
+++ b/lld/docs/getting_started.rst
@@ -103,4 +103,4 @@ More Information
 
 For more information on using CMake see the `LLVM CMake guide`_.
 
-.. _LLVM Cmake guide: http://llvm.org/docs/CMake.html
+.. _LLVM CMake guide: http://llvm.org/docs/CMake.html

diff --git a/lld/docs/sphinx_intro.rst b/lld/docs/sphinx_intro.rst
index d729c2d..6845bc8 100644 (file)
--- a/lld/docs/sphinx_intro.rst
+++ b/lld/docs/sphinx_intro.rst
@@ -40,8 +40,8 @@ If you do not have the ``easy_install`` tool on your system, you should be able
 to install it using:
 
   Linux
-    Use your distributions standard package managament tool to install it, i.e.,
-    ``apt-get install easy_install`` or ``yum install easy_install``.
+    Use your distribution's standard package management tool to install it,
+    i.e., ``apt-get install easy_install`` or ``yum install easy_install``.
 
   Mac OS X
     All modern Mac OS X systems come with ``easy_install`` as part of the base