Fix some typos in the doc
llvm-svn: 279943
diff --git a/llvm/docs/CodeGenerator.rst b/llvm/docs/CodeGenerator.rst
index 2f5a27c..9fccaa0 100644
--- a/llvm/docs/CodeGenerator.rst
+++ b/llvm/docs/CodeGenerator.rst
@@ -2396,7 +2396,7 @@
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
^^^^^^^^^^^^^^^^^^
diff --git a/llvm/docs/MemorySSA.rst b/llvm/docs/MemorySSA.rst
index 944df29..0249e70 100644
--- a/llvm/docs/MemorySSA.rst
+++ b/llvm/docs/MemorySSA.rst
@@ -136,7 +136,7 @@
- ``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``.
diff --git a/llvm/docs/_static/llvm.css b/llvm/docs/_static/llvm.css
index d7b5dae..53eeed9 100644
--- a/llvm/docs/_static/llvm.css
+++ b/llvm/docs/_static/llvm.css
@@ -82,7 +82,7 @@
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
diff --git a/llvm/docs/conf.py b/llvm/docs/conf.py
index d7e9e2d..428a513 100644
--- a/llvm/docs/conf.py
+++ b/llvm/docs/conf.py
@@ -249,5 +249,5 @@
# If true, show URL addresses after external links.
#man_show_urls = False
-# FIXME: Define intersphinx configration.
+# FIXME: Define intersphinx configuration.
intersphinx_mapping = {}
diff --git a/llvm/docs/doxygen.cfg.in b/llvm/docs/doxygen.cfg.in
index 7699711..7095dbd 100644
--- a/llvm/docs/doxygen.cfg.in
+++ b/llvm/docs/doxygen.cfg.in
@@ -1937,7 +1937,7 @@
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.
diff --git a/llvm/docs/tutorial/LangImpl06.rst b/llvm/docs/tutorial/LangImpl06.rst
index 7c9a212..f6d2bd9 100644
--- a/llvm/docs/tutorial/LangImpl06.rst
+++ b/llvm/docs/tutorial/LangImpl06.rst
@@ -32,7 +32,7 @@
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.
diff --git a/llvm/docs/tutorial/OCamlLangImpl6.rst b/llvm/docs/tutorial/OCamlLangImpl6.rst
index 2fa25f5..4b3e157 100644
--- a/llvm/docs/tutorial/OCamlLangImpl6.rst
+++ b/llvm/docs/tutorial/OCamlLangImpl6.rst
@@ -32,7 +32,7 @@
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.