Documentation: PTHInternals: use correct adornments and fix typos
Fixes PR14014
git-svn-id: https://llvm.org/svn/llvm-project/cfe/trunk@171005 91177308-0d34-0410-b5e6-96231b3b80d8
diff --git a/docs/PTHInternals.rst b/docs/PTHInternals.rst
index 55c0192..10dda61 100644
--- a/docs/PTHInternals.rst
+++ b/docs/PTHInternals.rst
@@ -60,7 +60,7 @@
type-checking must be completely redone every time a PTH file is used.
Basic Design Tradeoffs
-~~~~~~~~~~~~~~~~~~~~~~
+----------------------
In the long term there are plans to provide an alternate PCH
implementation for Clang that also caches the work for parsing and type
@@ -89,7 +89,7 @@
**Architecture independence**
In contrast to GCC's PCH files (and
those of several other compilers), Clang's PTH files are architecture
- independent, requiring only a single PTH file when building an
+ independent, requiring only a single PTH file when building a
program for multiple architectures.
For example, on Mac OS X one may wish to compile a "universal binary"
@@ -142,7 +142,7 @@
PTH such as reduced memory pressure (ideal for multi-core builds).
Internal PTH Optimizations
-~~~~~~~~~~~~~~~~~~~~~~~~~~
+--------------------------
While the main optimization employed by PTH is to reduce lexing time of
header files by caching pre-lexed tokens, PTH also employs several other
@@ -154,7 +154,7 @@
involved in context-switching to the kernel to resolve included
files.
-- Fasting skipping of ``#ifdef``... ``#endif`` chains: PTH files
+- Fast skipping of ``#ifdef`` ... ``#endif`` chains: PTH files
record the basic structure of nested preprocessor blocks. When the
condition of the preprocessor block is false, all of its tokens are
immediately skipped instead of requiring them to be handled by