From f85a4316dcd0baff1ae210a7a7ea8dc48775fa66 Mon Sep 17 00:00:00 2001
From: David Wells <drwells@vt.edu>
Date: Wed, 26 Aug 2015 09:30:09 -0400
Subject: [PATCH] Fix some typos in the documentation.

---
 doc/developers/cmake-internals.html       | 6 +++---
 doc/developers/porting.html               | 8 ++++----
 doc/developers/testsuite.html             | 6 +++---
 doc/developers/writing-documentation.html | 4 ++--
 doc/users/cmakelists.html                 | 2 +-
 5 files changed, 13 insertions(+), 13 deletions(-)

diff --git a/doc/developers/cmake-internals.html b/doc/developers/cmake-internals.html
index e5ec6c0c26..4c29722b2a 100644
--- a/doc/developers/cmake-internals.html
+++ b/doc/developers/cmake-internals.html
@@ -445,7 +445,7 @@ FEATURE_DEFINITIONS(|_DEBUG|_RELEASE)
 <pre>
 FEATURE_&lt;FEATURE&gt;_DEPENDS              (a variable)
   - a variable which contains an optional list of other features
-    this feature depends on (and which have to be enbled for this feature
+    this feature depends on (and which have to be enabled for this feature
     to work.)
     Features must be given with short name, i.e. without DEAL_II_WITH_
 
@@ -559,7 +559,7 @@ DEAL_II_FORCE_BUNDLED_&lt;FEATURE&gt;        (an option)
         <li> <code>DEAL_II_USER_INCLUDE_DIRS</code>
       </ul>
     <li>
-      Include dirs from bundled packages necessary for the compilation fo
+      Include dirs from bundled packages necessary for the compilation of
       the library and user projects out of the build directory:
       <ul>
         <li> <code>DEAL_II_BUNDLED_INCLUDE_DIRS</code>
@@ -668,7 +668,7 @@ SET(_inst
 #   ${CMAKE_BINARY_DIR}${CMAKE_FILES_DIRECTORY}/deal_ii_objects_(debug/release)
 # so that it is available in global scope.
 #
-# Header files and instatiation files (${_header}, ${_inst}) are added
+# Header files and instantiation files (${_header}, ${_inst}) are added
 # for cosmetic reasons, so that they show up in IDEs.
 #
 DEAL_II_ADD_LIBRARY(obj_dofs OBJECT ${_src} ${_header} ${_inst})
diff --git a/doc/developers/porting.html b/doc/developers/porting.html
index 658b5c7a90..f49b08a049 100644
--- a/doc/developers/porting.html
+++ b/doc/developers/porting.html
@@ -27,7 +27,7 @@
     <h2>Unknown compiler</h2>
 
     <p>
-      Currently, the <acronym>deal.II</acronym> CMake Buildsystem
+      Currently, the <acronym>deal.II</acronym> CMake build system
       recognizes
       <a href="http://gcc.gnu.org/">gcc</a>,
       <a href="http://clang.llvm.org/">clang</a>, as well as
@@ -35,7 +35,7 @@
       sets up reasonable default compiler flags.
       <ul>
         <li>
-          To start porting for an unkown compiler, specify
+          To start porting to an unknown compiler, specify
           <code>-DDEAL_II_SETUP_DEFAULT_COMPILER_FLAGS=OFF</code> and set all
           necessary compiler flags by hand via
 <pre>
@@ -78,7 +78,7 @@ include/deal.II/base/config.h.in
       information might help:
       <ul>
         <li>
-          The buildsystem of <acronym>deal.II</acronym> uses <a
+          The build system of <acronym>deal.II</acronym> uses <a
           href="http://www.cmake.org/" target="_top">CMake</a>.  So,
           in order to port <acronym>deal.II</acronym> to a new platform,
           it is obviously necessary that <a href="http://www.cmake.org/"
@@ -130,7 +130,7 @@ include/deal.II/base/config.h.in
       You have to set up a native deal.II build directory first and run
       <code>make expand_instantiations</code> in it. The executable is
       needed for the build system (and obviously the cross compiled version
-      cannot be used). Locate the <code>expand_instantions</code>
+      cannot be used). Locate the <code>expand_instantiations</code>
       executable and export its location in the <code>PATH</code>
       environment variable.
     </p>
diff --git a/doc/developers/testsuite.html b/doc/developers/testsuite.html
index 4397bd4d3e..1ace25b8fd 100644
--- a/doc/developers/testsuite.html
+++ b/doc/developers/testsuite.html
@@ -274,7 +274,7 @@ xx: ===============================    OUTPUT END   ============================
           category: The test project failed in the configuration stage
         </li>
         <li>
-          <code>BUILD</code>: compilation error occured
+          <code>BUILD</code>: compilation error occurred
         </li>
         <li>
           <code>RUN</code>: the test executable could not be run / aborted
@@ -431,7 +431,7 @@ category/test.[compiler=&lt;regex&gt;=&lt;yes|no&gt;.]*[with_&lt;feature&gt;=&lt
       Normally, a test will be set up so that it runs twice, once in debug and
       once in release configuration.
       If a specific test can only be run in debug or release configurations but
-      not in both it is possible to restrict the setup by prepeding
+      not in both it is possible to restrict the setup by prepending
       <code>.debug</code> or <code>.release</code> directly before
       <code>.output</code>, e.g.:
 <pre>
@@ -652,7 +652,7 @@ $ ctest -V -R "category/my_new_test"
       make sure that the output is what you had expected. (For complex tests,
       it may sometimes be impossible to say whether the output is correct, and
       in this case we sometimes just take it to make
-      sure that future invokations of the test yield the same results.)
+      sure that future invocations of the test yield the same results.)
     </p>
 
     <p>
diff --git a/doc/developers/writing-documentation.html b/doc/developers/writing-documentation.html
index 62c2a45c65..17e6235376 100644
--- a/doc/developers/writing-documentation.html
+++ b/doc/developers/writing-documentation.html
@@ -357,7 +357,7 @@ void foobar ()
       particular C++ constructs). On the other hand, showing code
       snippets in the introduction risks duplicating code in two
       places, which will eventually get out of synch. Consequently,
-      this intrstrument should only be used sparingly.
+      this instrument should only be used sparingly.
     </p>
 
 
@@ -372,7 +372,7 @@ void foobar ()
       create doxygen input that contains the comments of the program as
       text, and the actual code of the programs as code snippets. You
       can see this when you look at the pages for each of the tutorials
-      where the code is indendet relative to the text.
+      where the code is indented relative to the text.
     </p>
 
     <p>
diff --git a/doc/users/cmakelists.html b/doc/users/cmakelists.html
index a03ac2187a..8f7e30a6d7 100644
--- a/doc/users/cmakelists.html
+++ b/doc/users/cmakelists.html
@@ -869,7 +869,7 @@ DEAL_II_WITH_ZLIB
 <h2>  <code>Make.global_options</code> </h2>
 
 <p>
-  Above CMake configuration file <code>deal.IIConfig.cmake</code> is also
+  The above CMake configuration file <code>deal.IIConfig.cmake</code> is also
   available as a Makefile includable file called
   <code>Make.global_options</code>. It resides under
   <code>share/deal.II/Make.global_options</code> in the build and install
-- 
2.39.5