Fix some typos in the doc

git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@279943 91177308-0d34-0410-b5e6-96231b3b80d8

docs/CodeGenerator.rst

@@ -2396,7 +2396,7 @@ the following exceptions.  Callee saved registers are spilled after the frame is
 created.  This allows the llvm epilog/prolog support to be common with other
 targets.  The base pointer callee saved register r31 is saved in the TOC slot of
 linkage area.  This simplifies allocation of space for the base pointer and
-makes it convenient to locate programatically and during debugging.
+makes it convenient to locate programmatically and during debugging.
 
 Dynamic Allocation
 ^^^^^^^^^^^^^^^^^^

docs/MemorySSA.rst

@@ -136,7 +136,7 @@ Going from the top down:
 - ``2 = MemoryDef(6)`` notes that ``store i8 0, i8* %p1`` is a definition,
   and its reaching definition before it is ``6``, or the ``MemoryPhi`` after
   ``while.cond``. (See the `Build-time use optimization`_ and `Precision`_
-  sections below for why this ``MemoryDef`` isn't linked to a seperate,
+  sections below for why this ``MemoryDef`` isn't linked to a separate,
   disambiguated ``MemoryPhi``.)
 - ``3 = MemoryDef(6)`` notes that ``store i8 0, i8* %p2`` is a definition; its
   reaching definition is also ``6``.

docs/_static/llvm.css

@@ -82,7 +82,7 @@ h2+div, h2+p {text-align: left; padding-left: 20pt; padding-right: 10pt;}
 h3+div, h3+p {text-align: left; padding-left: 20pt; padding-right: 10pt;}
 h4+div, h4+p {text-align: left; padding-left: 20pt; padding-right: 10pt;}
 
-/* It is preferrable to use <pre class="doc_code"> everywhere instead of the
+/* It is preferable to use <pre class="doc_code"> everywhere instead of the
  * <div class="doc_code"><pre>...</ptr></div> construct.
  *
  * Once all docs use <pre> for code regions, this style can  be merged with the

docs/conf.py

@@ -249,5 +249,5 @@ for name in os.listdir(command_guide_path):
 # If true, show URL addresses after external links.
 #man_show_urls = False
 
-# FIXME: Define intersphinx configration.
+# FIXME: Define intersphinx configuration.
 intersphinx_mapping = {}

docs/doxygen.cfg.in

@@ -1937,7 +1937,7 @@ PREDEFINED             =
 EXPAND_AS_DEFINED      =
 
 # If the SKIP_FUNCTION_MACROS tag is set to YES then doxygen's preprocessor will
-# remove all refrences to function-like macros that are alone on a line, have an
+# remove all references to function-like macros that are alone on a line, have an
 # all uppercase name, and do not end with a semicolon. Such function macros are
 # typically used for boiler-plate code, and will confuse the parser if not
 # removed.

docs/tutorial/LangImpl06.rst

@@ -32,7 +32,7 @@ User-defined Operators: the Idea
 
 The "operator overloading" that we will add to Kaleidoscope is more
 general than languages like C++. In C++, you are only allowed to
-redefine existing operators: you can't programatically change the
+redefine existing operators: you can't programmatically change the
 grammar, introduce new operators, change precedence levels, etc. In this
 chapter, we will add this capability to Kaleidoscope, which will let the
 user round out the set of operators that are supported.

docs/tutorial/OCamlLangImpl6.rst

@@ -32,7 +32,7 @@ User-defined Operators: the Idea
 
 The "operator overloading" that we will add to Kaleidoscope is more
 general than languages like C++. In C++, you are only allowed to
-redefine existing operators: you can't programatically change the
+redefine existing operators: you can't programmatically change the
 grammar, introduce new operators, change precedence levels, etc. In this
 chapter, we will add this capability to Kaleidoscope, which will let the
 user round out the set of operators that are supported.