[docs] Remove doubled spaces

[aaron.ballman]

LGTM!

docs/ModularizeUsage.rst

 ================
 Modularize Usage
 ================
 
 ``modularize [<modularize-options>] [<module-map>|<include-files-list>]*
 [<front-end-options>...]``
 
 ``<modularize-options>`` is a place-holder for options
 specific to modularize, which are described below in
 `Modularize Command Line Options`.
 
 ``<module-map>`` specifies the path of a file name for an
-existing module map.  The module map must be well-formed in
-terms of syntax.  Modularize will extract the header file names
-from the map.  Only normal headers are checked, assuming headers
+existing module map. The module map must be well-formed in
+terms of syntax. Modularize will extract the header file names
+from the map. Only normal headers are checked, assuming headers
 marked "private", "textual", or "exclude" are not to be checked
 as a top-level include, assuming they either are included by
 other headers which are checked, or they are not suitable for
 modules.
 
 ``<include-files-list>`` specifies the path of a file name for a
 file containing the newline-separated list of headers to check
 with respect to each other. Lines beginning with '#' and empty
 lines are ignored. Header file names followed by a colon and
 other space-separated file names will include those extra files
 as dependencies. The file names can be relative or full paths,
 but must be on the same line. For example::
 
   header1.h
   header2.h
   header3.h: header1.h header2.h
 
 Note that unless a ``-prefix (header path)`` option is specified,
 non-absolute file paths in the header list file will be relative
-to the header list file directory.  Use -prefix to specify a different
+to the header list file directory. Use -prefix to specify a different
 directory.
 
 ``<front-end-options>`` is a place-holder for regular Clang
 front-end arguments, which must follow the <include-files-list>.
 Note that by default, modularize assumes .h files
 contain C++ source, so if you are using a different language,
 you might need to use a ``-x`` option to tell Clang that the
 header contains another language, i.e.:  ``-x c``
 
 Note also that because modularize does not use the clang driver,
 you will likely need to pass in additional compiler front-end
 arguments to match those passed in by default by the driver.
 
 Modularize Command Line Options
 ===============================
 
 .. option:: -prefix=<header-path>
 
   Prepend the given path to non-absolute file paths in the header list file.
   By default, headers are assumed to be relative to the header list file
-  directory.  Use ``-prefix`` to specify a different directory.
+  directory. Use ``-prefix`` to specify a different directory.
 
 .. option:: -module-map-path=<module-map-path>
 
-  Generate a module map and output it to the given file.  See the description
+  Generate a module map and output it to the given file. See the description
   in :ref:`module-map-generation`.
   
 .. option:: -problem-files-list=<problem-files-list-file-name>
 
-  For use only with module map assistant.  Input list of files that
-  have problems with respect to modules.  These will still be
+  For use only with module map assistant. Input list of files that
+  have problems with respect to modules. These will still be
   included in the generated module map, but will be marked as
   "excluded" headers.
 
 .. option:: -root-module=<root-name>
 
   Put modules generated by the -module-map-path option in an enclosing
-  module with the given name.  See the description in :ref:`module-map-generation`.
+  module with the given name. See the description in :ref:`module-map-generation`.
 
 .. option:: -block-check-header-list-only
 
   Limit the #include-inside-extern-or-namespace-block
   check to only those headers explicitly listed in the header list.
   This is a work-around for avoiding error messages for private includes that
   purposefully get included inside blocks.
 
 .. option:: -no-coverage-check
 
   Don't do the coverage check for a module map.
 
 .. option:: -coverage-check-only
 
   Only do the coverage check for a module map.
 
 .. option:: -display-file-lists
 
   Display lists of good files (no compile errors), problem files,
   and a combined list with problem files preceded by a '#'.
   This can be used to quickly determine which files have problems.
   The latter combined list might be useful in starting to modularize
-  a set of headers.  You can start with a full list of headers,
+  a set of headers. You can start with a full list of headers,
   use -display-file-lists option, and then use the combined list as
   your intermediate list, uncommenting-out headers as you fix them.

docs/clang-tidy/checks/cppcoreguidelines-pro-type-cstyle-cast.rst

 .. title:: clang-tidy - cppcoreguidelines-pro-type-cstyle-cast
 
 cppcoreguidelines-pro-type-cstyle-cast
 ======================================
 
 This check flags all use of C-style casts that perform a ``static_cast``
 downcast, ``const_cast``, or ``reinterpret_cast``.
 
 Use of these casts can violate type safety and cause the program to access a
 variable that is actually of type X to be accessed as if it were of an unrelated
 type Z. Note that a C-style ``(T)expression`` cast means to perform the first of
 the following that is possible: a ``const_cast``, a ``static_cast``, a
 ``static_cast`` followed by a ``const_cast``, a ``reinterpret_cast``, or a
-``reinterpret_cast`` followed by a ``const_cast``.  This rule bans
+``reinterpret_cast`` followed by a ``const_cast``. This rule bans
 ``(T)expression`` only when used to perform an unsafe cast.
 
 This rule is part of the "Type safety" profile of the C++ Core Guidelines, see
 https://github.com/isocpp/CppCoreGuidelines/blob/master/CppCoreGuidelines.md#Pro-type-cstylecast.

docs/clang-tidy/checks/cppcoreguidelines-pro-type-member-init.rst

 
 Options
 -------
 
 .. option:: IgnoreArrays
 
    If set to non-zero, the check will not warn about array members that are not
    zero-initialized during construction. For performance critical code, it may
-   be important to not initialize fixed-size array members.  Default is `0`.
+   be important to not initialize fixed-size array members. Default is `0`.
 
 This rule is part of the "Type safety" profile of the C++ Core
 Guidelines, corresponding to rule Type.6. See
 https://github.com/isocpp/CppCoreGuidelines/blob/master/CppCoreGuidelines.md#Pro-type-memberinit.

docs/clang-tidy/checks/misc-sizeof-expression.rst

.. code-block:: c++
   }
 
 Options
 -------
 
 .. option:: WarnOnSizeOfConstant
 
    When non-zero, the check will warn on an expression like
-   ``sizeof(CONSTANT)``.  Default is `1`.
+   ``sizeof(CONSTANT)``. Default is `1`.
 
 .. option:: WarnOnSizeOfThis
 
    When non-zero, the check will warn on an expression like ``sizeof(this)``.
    Default is `1`.
 
 .. option:: WarnOnSizeOfCompareToConstant
 
    When non-zero, the check will warn on an expression like
    ``sizeof(epxr) <= k`` for a suspicious constant `k` while `k` is `0` or
    greater than `0x8000`. Default is `1`.

docs/clang-tidy/checks/modernize-raw-string-literal.rst

.. code-block:: c++
   const char *const Path{R"(C:\Program Files\Vendor\Application.exe)"};
   const char *const RegEx{R"(\w\([a-z]\))"};
 
 The presence of any of the following escapes can cause the string to be
 converted to a raw string literal: ``\\``, ``\'``, ``\"``, ``\?``,
 and octal or hexadecimal escapes for printable ASCII characters.
 
 A string literal containing only escaped newlines is a common way of
-writing lines of text output.  Introducing physical newlines with raw
-string literals in this case is likely to impede readability.  These
+writing lines of text output. Introducing physical newlines with raw
+string literals in this case is likely to impede readability. These
 string literals are left unchanged.
 
 An escaped horizontal tab, form feed, or vertical tab prevents the string
-literal from being converted.  The presence of a horizontal tab, form feed or
+literal from being converted. The presence of a horizontal tab, form feed or
 vertical tab in source code is not visually obvious.

docs/clang-tidy/checks/modernize-use-auto.rst

 .. title:: clang-tidy - modernize-use-auto
 
 modernize-use-auto
 ==================
 
 This check is responsible for using the ``auto`` type specifier for variable
-declarations to *improve code readability and maintainability*.  For example:
+declarations to *improve code readability and maintainability*. For example:
 
 .. code-block:: c++
 
   std::vector<int>::iterator I = my_container.begin();
 
   // transforms to:
 
   auto I = my_container.begin();

docs/clang-tidy/checks/modernize-use-default.rst

 .. title:: clang-tidy - modernize-use-default
 
 modernize-use-default
 =====================
 
 This check replaces default bodies of special member functions with ``=
-default;``.  The explicitly defaulted function declarations enable more
+default;``. The explicitly defaulted function declarations enable more
 opportunities in optimization, because the compiler might treat explicitly
 defaulted functions as trivial.
 
 .. code-block:: c++
 
   struct A {
     A() {}
     ~A();

docs/clang-tidy/checks/modernize-use-emplace.rst

 This is because replacing it with ``emplace_back`` could cause a leak of this
 pointer if ``emplace_back`` would throw exception before emplacement (e.g. not
 enough memory to add new element).
 
 For more info read item 42 - "Consider emplacement instead of insertion." of
 Scott Meyers "Effective Modern C++".
 
 The default smart pointers that are considered are ``std::unique_ptr``,
-``std::shared_ptr``, ``std::auto_ptr``.  To specify other smart pointers or
+``std::shared_ptr``, ``std::auto_ptr``. To specify other smart pointers or
 other classes use the :option:`SmartPointers` option.
 
 
 Check also fires if any argument of constructor call would be:
 
   - bitfield (bitfields can't bind to rvalue/universal reference)
 
   - ``new`` expression (to avoid leak) or if the argument would be converted via

docs/clang-tidy/checks/performance-faster-string-find.rst

 .. title:: clang-tidy - performance-faster-string-find
 
 performance-faster-string-find
 ==============================
 
 Optimize calls to ``std::string::find()`` and friends when the needle passed is
-a single character string literal.  The character literal overload is more
+a single character string literal. The character literal overload is more
 efficient.
 
 Examples:
 
 .. code-block:: c++
 
   str.find("A");
 

docs/clang-tidy/checks/readability-braces-around-statements.rst

 -------
 
 .. option:: ShortStatementLines
 
    Defines the minimal number of lines that the statement should have in order
    to trigger this check.
 
    The number of lines is counted from the end of condition or initial keyword
-   (``do``/``else``) until the last line of the inner statement.  Default value
+   (``do``/``else``) until the last line of the inner statement. Default value
    `0` means that braces will be added to all statements (not having them
    already).

docs/clang-tidy/index.rst

-analyze-temporary-dtors     -
                                    .clang-tidy file.
     -checks=<string>             - 
                                    Comma-separated list of globs with optional '-'
                                    prefix. Globs are processed in order of
                                    appearance in the list. Globs without '-'
                                    prefix add checks with matching names to the
                                    set, globs with the '-' prefix remove checks
                                    with matching names from the set of enabled
-                                   checks.  This option's value is appended to the
+                                   checks. This option's value is appended to the
                                    value of the 'Checks' option in .clang-tidy
                                    file, if any.
     -config=<string>             - 
                                    Specifies a configuration in YAML/JSON format:
                                      -config="{Checks: '*',
                                                CheckOptions: [{key: x,
                                                                value: y}]}"
                                    When the value is empty, clang-tidy will

 with strict checks. `Lit`_ tests allow using partial text matching and regular
 expressions which makes them more suitable for writing compact tests for
 diagnostic messages.
 
 The ``check_clang_tidy.py`` script provides an easy way to test both
 diagnostic messages and fix-its. It filters out ``CHECK`` lines from the test
 file, runs :program:`clang-tidy` and verifies messages and fixes with two
 separate `FileCheck`_ invocations. To use the script, put a .cpp file with the
-appropriate ``RUN`` line in the ``test/clang-tidy`` directory.  Use
+appropriate ``RUN`` line in the ``test/clang-tidy`` directory. Use
 ``CHECK-MESSAGES:`` and ``CHECK-FIXES:`` lines to write checks against
 diagnostic messages and fixed code.
 
 It's advised to make the checks as specific as possible to avoid checks matching
 to incorrect parts of the input. Use ``[[@LINE+X]]``/``[[@LINE-X]]``
 substitutions and distinct function and variable names in the test code.
 
 Here's an example of a test using the ``check_clang_tidy.py`` script (the full

docs/include-fixer.rst

 in your ``.emacs``:
 
 .. code-block:: console
 
  (add-to-list 'load-path "path/to/llvm/source/tools/clang/tools/extra/include-fixer/tool/"
  (require 'clang-include-fixer)
 
 Within Emacs the tool can be invoked with the command
-``M-x clang-include-fixer``.  This will insert the header that defines the
+``M-x clang-include-fixer``. This will insert the header that defines the
 first undefined symbol; if there is more than one header that would define the
 symbol, the user is prompted to select one.
 
 To include the header that defines the symbol at point, run
 ``M-x clang-include-fixer-at-point``.
 
 Make sure Emacs can find :program:`clang-include-fixer`:
 

docs/index.rst

 documentation contains no instructions about how to use the tools, only the APIs
 that make up the software. For usage instructions, please see the user's guide
 or reference manual for each tool.
 
 * `Doxygen documentation`_
 
 .. _`Doxygen documentation`: doxygen/annotated.html
 
-..  note::
+.. note::
     This documentation is generated directly from the source code with doxygen.
     Since the tools of clang-tools-extra are constantly under active
     development, what you're about to read is out of date!
 
 
 Indices and tables
 ==================
 
 * :ref:`genindex`
 * :ref:`search`

docs/modularize.rst

 provides the consistent definitions required to use modules. For example, it
 detects whether the same entity (say, a NULL macro or size_t typedef) is
 defined in multiple headers or whether a header produces different definitions
 under different circumstances. These conditions cause modules built from the
 headers to behave poorly, and should be fixed before introducing a module
 map.
 
 :program:`modularize` also has an assistant mode option for generating
-a module map file based on the provided header list.  The generated file
+a module map file based on the provided header list. The generated file
 is a functional module map that can be used as a starting point for a
 module.map file.
 
 Getting Started
 ===============
 
 To build from source:
 
and can produce error message like the following::
   The "extern "C" {}" block is here.
 
 .. _module-map-coverage:
 
 Module Map Coverage Check
 =========================
 
 The coverage check uses the Clang library to read and parse the
-module map file.  Starting at the module map file directory, or just the
+module map file. Starting at the module map file directory, or just the
 include paths, if specified, it will collect the names of all the files it
 considers headers (no extension, .h, or .inc--if you need more, modify the
-isHeader function).  It then compares the headers against those referenced
+isHeader function). It then compares the headers against those referenced
 in the module map, either explicitly named, or implicitly named via an
 umbrella directory or umbrella file, as parsed by the ModuleMap object.
 If headers are found which are not referenced or covered by an umbrella
 directory or file, warning messages will be produced, and this program
 will return an error code of 1. If no problems are found, an error code of
 0 is returned.
 
 Note that in the case of umbrella headers, this tool invokes the compiler
 to preprocess the file, and uses a callback to collect the header files
-included by the umbrella header or any of its nested includes.  If any
+included by the umbrella header or any of its nested includes. If any
 front end options are needed for these compiler invocations, these
 can be included on the command line after the module map file argument.
 
 Warning message have the form:
 
   warning: module.modulemap does not account for file: Level3A.h
 
 Note that for the case of the module map referencing a file that does

 
 .. _module-map-generation:
 
 Module Map Generation
 =====================
 
 If you specify the ``-module-map-path=<module map file>``,
 :program:`modularize` will output a module map based on the input header list.
-A module will be created for each header.  Also, if the header in the header
+A module will be created for each header. Also, if the header in the header
 list is a partial path, a nested module hierarchy will be created in which a
 module will be created for each subdirectory component in the header path,
-with the header itself represented by the innermost module.  If other headers
+with the header itself represented by the innermost module. If other headers
 use the same subdirectories, they will be enclosed in these same modules also.
 
 For example, for the header list::
 
   SomeTypes.h
   SomeDecls.h
   SubModule1/Header1.h
   SubModule1/Header2.h
module Root {
     }
   }
 
 Note that headers with dependents will be ignored with a warning, as the
 Clang module mechanism doesn't support headers the rely on other headers
 to be included first.
 
 The module map format defines some keywords which can't be used in module
-names.  If a header has one of these names, an underscore ('_') will be
-prepended to the name.  For example, if the header name is ``header.h``,
+names. If a header has one of these names, an underscore ('_') will be
+prepended to the name. For example, if the header name is ``header.h``,
 because ``header`` is a keyword, the module name will be ``_header``.
 For a list of the module map keywords, please see:
 `Lexical structure <http://clang.llvm.org/docs/Modules.html#lexical-structure>`_

docs/pp-trace.rst

 .. index:: pp-trace
 
 ==================================
 pp-trace User's Manual
 ==================================
 
 .. toctree::
    :hidden:
 
 :program:`pp-trace` is a standalone tool that traces preprocessor
-activity.  It's also used as a test of Clang's PPCallbacks interface.
+activity. It's also used as a test of Clang's PPCallbacks interface.
 It runs a given source file through the Clang preprocessor, displaying
 selected information from callback functions overridden in a
 `PPCallbacks <http://clang.llvm.org/doxygen/classclang_1_1PPCallbacks.html>`_
-derivation.  The output is in a high-level YAML format, described in
+derivation. The output is in a high-level YAML format, described in
 :ref:`OutputFormat`.
 
 .. _Usage:
 
 pp-trace Usage
 ==============
 
 Command Line Format

 .. _CommandLineOptions:
 
 Command Line Options
 --------------------
 
 .. option:: -ignore <callback-name-list>
 
   This option specifies a comma-separated list of names of callbacks
-  that shouldn't be traced.  It can be used to eliminate unwanted
-  trace output.  The callback names are the name of the actual
+  that shouldn't be traced. It can be used to eliminate unwanted
+  trace output. The callback names are the name of the actual
   callback function names in the PPCallbacks class:
 
   * FileChanged
   * FileSkipped
   * FileNotFound
   * InclusionDirective
   * moduleImport
   * EndOfMainFile
.. option:: -ignore <callback-name-list>
   * Elif
   * Ifdef
   * Ifndef
   * Else
   * Endif
 
 .. option:: -output <output-file>
 
-  By default, pp-trace outputs the trace information to stdout.  Use this
+  By default, pp-trace outputs the trace information to stdout. Use this
   option to output the trace information to a file.
 
 .. _OutputFormat:
 
 pp-trace Output Format
 ======================
 
-The pp-trace output is formatted as YAML.  See http://yaml.org/ for general
-YAML information.  It's arranged as a sequence of information about the
+The pp-trace output is formatted as YAML. See http://yaml.org/ for general
+YAML information. It's arranged as a sequence of information about the
 callback call, including the callback name and argument information, for
 example:::
 
   ---
   - Callback: Name
     Argument1: Value1
     Argument2: Value2
   (etc.)

 
 The argument descriptions table describes the callback argument information
 displayed.
 
 The Argument Name field in most (but not all) cases is the same name as the
 callback function parameter.
 
 The Argument Value Syntax field describes the values that will be displayed
-for the argument value.  It uses an ad hoc representation that mixes literal
-and symbolic representations.  Enumeration member symbols are shown as the
-actual enum member in a (member1|member2|...) form.  A name in parentheses
+for the argument value. It uses an ad hoc representation that mixes literal
+and symbolic representations. Enumeration member symbols are shown as the
+actual enum member in a (member1|member2|...) form. A name in parentheses
 can either represent a place holder for the described value, or confusingly,
 it might be a literal, such as (null), for a null pointer.
 Locations are shown as quoted only to avoid confusing the documentation generator.
 
 The Clang C++ Type field is the type from the callback function declaration.
 
 The description describes the argument or what is displayed for it.
 
 Note that in some cases, such as when a structure pointer is an argument
 value, only some key member or members are shown to represent the value,
 instead of trying to display all members of the structure.
 
 `FileChanged <http://clang.llvm.org/doxygen/classclang_1_1PPCallbacks.html#a7cc8cfaf34114fc65e92af621cd6464e>`_ Callback
 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
 
 FileChanged is called when the preprocessor enters or exits a file, both the
-top level file being compiled, as well as any #include directives.  It will
+top level file being compiled, as well as any #include directives. It will
 also be called as a result of a system header pragma or in internal renaming
 of a file.
 
 Argument descriptions:
 
 ==============   ==================================================   ============================== ==============================
 Argument Name    Argument Value Syntax                                Clang C++ Type                 Description           
 ==============   ==================================================   ============================== ==============================
-Loc              "(file):(line):(col)"                                SourceLocation                 The location of the directive.    
-Reason           (EnterFile|ExitFile|SystemHeaderPragma|RenameFile)   PPCallbacks::FileChangeReason  Reason for change.    
-FileType         (C_User|C_System|C_ExternCSystem)                    SrcMgr::CharacteristicKind     Include type.         
+Loc              "(file):(line):(col)"                                SourceLocation                 The location of the directive.
+Reason           (EnterFile|ExitFile|SystemHeaderPragma|RenameFile)   PPCallbacks::FileChangeReason  Reason for change.
+FileType         (C_User|C_System|C_ExternCSystem)                    SrcMgr::CharacteristicKind     Include type.
 PrevFID          ((file)|(invalid))                                   FileID                         Previous file, if any.
 ==============   ==================================================   ============================== ==============================
 
 Example:::
 
   - Callback: FileChanged
     Loc: "D:/Clang/llvm/tools/clang/tools/extra/test/pp-trace/pp-trace-include.cpp:1:1"
     Reason: EnterFile
     FileType: C_User
     PrevFID: (invalid)
 
 `FileSkipped <http://clang.llvm.org/doxygen/classclang_1_1PPCallbacks.html#ab5b338a0670188eb05fa7685bbfb5128>`_ Callback
 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
 
 FileSkipped is called when a source file is skipped as the result of header
 guard optimization.
 
 Argument descriptions:
 
 ==============   ==================================================   ============================== ========================================================
 Argument Name    Argument Value Syntax                                Clang C++ Type                 Description           
 ==============   ==================================================   ============================== ========================================================
 ParentFile       ("(file)" or (null))                                 const FileEntry                The file that #included the skipped file.
-FilenameTok      (token)                                              const Token                    The token in ParentFile that indicates the skipped file. 
+FilenameTok      (token)                                              const Token                    The token in ParentFile that indicates the skipped file.
 FileType         (C_User|C_System|C_ExternCSystem)                    SrcMgr::CharacteristicKind     The file type.
 ==============   ==================================================   ============================== ========================================================
 
 Example:::
 
   - Callback: FileSkipped
     ParentFile: "/path/filename.h"
     FilenameTok: "filename.h"

 HashLoc          "(file):(line):(col)"                                SourceLocation                 The location of the '#' that starts the inclusion directive.
 IncludeTok       (token)                                              const Token                    The token that indicates the kind of inclusion directive, e.g., 'include' or 'import'.
 FileName         "(file)"                                             StringRef                      The name of the file being included, as written in the source code.
 IsAngled         (true|false)                                         bool                           Whether the file name was enclosed in angle brackets; otherwise, it was enclosed in quotes.
 FilenameRange    "(file)"                                             CharSourceRange                The character range of the quotes or angle brackets for the written file name.
 File             "(file)"                                             const FileEntry                The actual file that may be included by this inclusion directive.
 SearchPath       "(path)"                                             StringRef                      Contains the search path which was used to find the file in the file system.
 RelativePath     "(path)"                                             StringRef                      The path relative to SearchPath, at which the include file was found.
-Imported         ((module name)|(null))                               const Module                   The module, whenever an inclusion directive was automatically turned into a module import or null otherwise. 
+Imported         ((module name)|(null))                               const Module                   The module, whenever an inclusion directive was automatically turned into a module import or null otherwise.
 ==============   ==================================================   ============================== ============================================================================================================
 
 Example:::
 
   - Callback: InclusionDirective
     IncludeTok: include
     FileName: "Input/Level1B.h"
     IsAngled: false

 
 Argument descriptions:
 
 ==============   ==================================================   ============================== ===========================================================
 Argument Name    Argument Value Syntax                                Clang C++ Type                 Description           
 ==============   ==================================================   ============================== ===========================================================
 ImportLoc        "(file):(line):(col)"                                SourceLocation                 The location of import directive token.
 Path             "(path)"                                             ModuleIdPath                   The identifiers (and their locations) of the module "path".
-Imported         ((module name)|(null))                               const Module                   The imported module; can be null if importing failed. 
+Imported         ((module name)|(null))                               const Module                   The imported module; can be null if importing failed.
 ==============   ==================================================   ============================== ===========================================================
 
 Example:::
 
   - Callback: moduleImport
     ImportLoc: "d:/Clang/llvm/tools/clang/tools/extra/test/pp-trace/pp-trace-modules.cpp:4:2"
     Path: [{Name: Level1B, Loc: "d:/Clang/llvmnewmod/tools/clang/tools/extra/test/pp-trace/pp-trace-modules.cpp:4:9"}, {Name: Level2B, Loc: "d:/Clang/llvmnewmod/tools/clang/tools/extra/test/pp-trace/pp-trace-modules.cpp:4:17"}]
     Imported: Level2B

 
 Ident is called when a #ident or #sccs directive is read.
 
 Argument descriptions:
 
 ==============   ==================================================   ============================== ==============================
 Argument Name    Argument Value Syntax                                Clang C++ Type                 Description           
 ==============   ==================================================   ============================== ==============================
-Loc              "(file):(line):(col)"                                SourceLocation                 The location of the directive. 
-str              (name)                                               const std::string              The text of the directive. 
+Loc              "(file):(line):(col)"                                SourceLocation                 The location of the directive.
+str              (name)                                               const std::string              The text of the directive.
 ==============   ==================================================   ============================== ==============================
 
 Example:::
 
   - Callback: Ident
     Loc: "D:/Clang/llvm/tools/clang/tools/extra/test/pp-trace/pp-trace-ident.cpp:3:1"
     str: "$Id$"
 
 `PragmaDirective <http://clang.llvm.org/doxygen/classclang_1_1PPCallbacks.html#a0a2d7a72c62184b3cbde31fb62c6f2f7>`_ Callback
 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
 
 PragmaDirective is called when start reading any pragma directive.
 
 Argument descriptions:
 
 ==============   ==================================================   ============================== =================================
 Argument Name    Argument Value Syntax                                Clang C++ Type                 Description           
 ==============   ==================================================   ============================== =================================
-Loc              "(file):(line):(col)"                                SourceLocation                 The location of the directive. 
+Loc              "(file):(line):(col)"                                SourceLocation                 The location of the directive.
 Introducer       (PIK_HashPragma|PIK__Pragma|PIK___pragma)            PragmaIntroducerKind           The type of the pragma directive.
 ==============   ==================================================   ============================== =================================
 
 Example:::
 
   - Callback: PragmaDirective
     Loc: "D:/Clang/llvm/tools/clang/tools/extra/test/pp-trace/pp-trace-pragma.cpp:3:1"
     Introducer: PIK_HashPragma

 PragmaMessage is called when a #pragma message directive is read.
 
 Argument descriptions:
 
 ==============   ==================================================   ============================== =======================================
 Argument Name    Argument Value Syntax                                Clang C++ Type                 Description           
 ==============   ==================================================   ============================== =======================================
 Loc              "(file):(line):(col)"                                SourceLocation                 The location of the directive.
-Namespace        (name)                                               StringRef                      The namespace of the message directive. 
-Kind             (PMK_Message|PMK_Warning|PMK_Error)                  PPCallbacks::PragmaMessageKind The type of the message directive. 
-Str              (string)                                             StringRef                      The text of the message directive. 
+Namespace        (name)                                               StringRef                      The namespace of the message directive.
+Kind             (PMK_Message|PMK_Warning|PMK_Error)                  PPCallbacks::PragmaMessageKind The type of the message directive.
+Str              (string)                                             StringRef                      The text of the message directive.
 ==============   ==================================================   ============================== =======================================
 
 Example:::
 
   - Callback: PragmaMessage
     Loc: "D:/Clang/llvm/tools/clang/tools/extra/test/pp-trace/pp-trace-pragma.cpp:3:1"
     Namespace: "GCC"
     Kind: PMK_Message

 Argument descriptions:
 
 ==============   ==================================================   ============================== ======================================================================================================
 Argument Name    Argument Value Syntax                                Clang C++ Type                 Description           
 ==============   ==================================================   ============================== ======================================================================================================
 MacroNameTok     (token)                                              const Token                    The macro name token.
 MacroDirective   (MD_Define|MD_Undefine|MD_Visibility)                const MacroDirective           The kind of macro directive from the MacroDirective structure.
 Range            ["(file):(line):(col)", "(file):(line):(col)"]       SourceRange                    The source range for the expansion.
-Args             [(name)|(number)|<(token name)>[, ...]]              const MacroArgs                The argument tokens.  Names and numbers are literal, everything else is of the form '<' tokenName '>'.
+Args             [(name)|(number)|<(token name)>[, ...]]              const MacroArgs                The argument tokens. Names and numbers are literal, everything else is of the form '<' tokenName '>'.
 ==============   ==================================================   ============================== ======================================================================================================
 
 Example:::
 
   - Callback: MacroExpands
     MacroNameTok: X_IMPL
     MacroDirective: MD_Define
     Range: [(nonfile), (nonfile)]