[clang-format][doc] Correct typos

[sstwcw]

Summary

I ran the script for dumping the format style options before committing
16ccba51072b just in case. It turned out that the 2 files didn't matchc
any more due to an attempt at fixing typos.

NOTE: Clang-Format Team Automated Review Comment

It looks like your clang-format review does not contain any unit tests, please try to ensure all code changes have a unit test (unless this is an NFC or refactoring, adding documentation etc..)

Add your unit tests in clang/unittests/Format and you can build with ninja FormatTests. We recommend using the verifyFormat(xxx) format of unit tests rather than EXPECT_EQ as this will ensure you change is tolerant to random whitespace changes (see FormatTest.cpp as an example)

For situations where your change is altering the TokenAnnotator.cpp which can happen if you are trying to improve the annotation phase to ensure we are correctly identifying the type of a token, please add a token annotator test in TokenAnnotatorTest.cpp

[owenpan]

clang/docs/ClangFormatStyleOptions.rst

5100

11e2975810acd fixed the typo betwee here while it should have fixed it in Format.h instead.

clang/include/clang/Format/Format.h

4018

Or to be more precise: put a space between a control statement keyword (for/if/while) and the opening parenthesis that follows.

clang/docs/ClangFormatStyleOptions.rst

**AttributeMacros** (``List of Strings``) :versionbadge:`clang-format 12` :ref:`¶ <AttributeMacros>`
   instead of identifiers. This can be useful for language extensions or
   static analyzer annotations.
 
   For example:
 
   .. code-block:: c++
 
     x = (char *__capability)&y;
-    int function(void) __ununsed;
+    int function(void) __unused;
     void only_writes_to_buffer(char *__output buffer);
 
   In the .clang-format configuration file, this can be configured like:
 
   .. code-block:: yaml
 
-    AttributeMacros: ['__capability', '__output', '__ununsed']
+    AttributeMacros: ['__capability', '__output', '__unused']
 
 .. _BinPackArguments:
 
 **BinPackArguments** (``Boolean``) :versionbadge:`clang-format 3.7` :ref:`¶ <BinPackArguments>`
   If ``false``, a function call's arguments will either be all on the
   same line or will have one line each.
 
   .. code-block:: c++
**SpaceBeforeParensOptions** (``SpaceBeforeParensCustom``) :versionbadge:`clang-format 14` :ref:`¶ <SpaceBeforeParensOptions>`
   .. code-block:: c++
 
     # Should be declared this way:
     SpaceBeforeParens: Custom
     SpaceBeforeParensOptions:
       AfterControlStatements: true
       AfterFunctionDefinitionName: true
 
   * ``bool AfterControlStatements`` If ``true``, put space between control statement keywords
     (for/if/while...) and opening parentheses.
 
     .. code-block:: c++
 
        true:                                  false:
        if (...) {}                     vs.    if(...) {}
 
   * ``bool AfterForeachMacros`` If ``true``, put space between foreach macros and opening parentheses.

clang/include/clang/Format/Format.h

struct FormatStyle {
 
   /// A vector of strings that should be interpreted as attributes/qualifiers
   /// instead of identifiers. This can be useful for language extensions or
   /// static analyzer annotations.
   ///
   /// For example:
   /// \code
   ///   x = (char *__capability)&y;
-  ///   int function(void) __ununsed;
+  ///   int function(void) __unused;
   ///   void only_writes_to_buffer(char *__output buffer);
   /// \endcode
   ///
   /// In the .clang-format configuration file, this can be configured like:
   /// \code{.yaml}
-  ///   AttributeMacros: ['__capability', '__output', '__ununsed']
+  ///   AttributeMacros: ['__capability', '__output', '__unused']
   /// \endcode
   ///
   /// \version 12
   std::vector<std::string> AttributeMacros;
 
   /// If ``false``, a function call's arguments will either be all on the
   /// same line or will have one line each.
   /// \code

   /// \code
   ///   # Should be declared this way:
   ///   SpaceBeforeParens: Custom
   ///   SpaceBeforeParensOptions:
   ///     AfterControlStatements: true
   ///     AfterFunctionDefinitionName: true
   /// \endcode
   struct SpaceBeforeParensCustom {
-    /// If ``true``, put space betwee control statement keywords
+    /// If ``true``, put space between control statement keywords
     /// (for/if/while...) and opening parentheses.
     /// \code
     ///    true:                                  false:
     ///    if (...) {}                     vs.    if(...) {}
     /// \endcode
     bool AfterControlStatements;
     /// If ``true``, put space between foreach macros and opening parentheses.
     /// \code