Fix, format and reorder documentation

Author: SimplyDanny

clang-tools-extra/clang-tidy/modernize/UseDesignatedInitializersCheck.cpp

@@ -150,7 +150,7 @@ void UseDesignatedInitializersCheck::check(
     return;
   }
 
-  // In case that a only few elements are un-designated (not all as before), the
+  // In case that only a few elements are un-designated (not all as before), the
   // check offers dedicated issues and fix-its for each of them.
   for (const auto *InitExpr : *SyntacticInitList) {
     if (isa<DesignatedInitExpr>(InitExpr))

clang-tools-extra/docs/clang-tidy/checks/modernize/use-designated-initializers.rst

@@ -3,23 +3,16 @@
 modernize-use-designated-initializers
 =====================================
 
-Finds initializer lists for aggregate type that could be written as
-designated initializers instead.
+Finds initializer lists for aggregate types which could be written as designated
+initializers instead.
 
-With plain initializer lists, it is very easy to introduce bugs when adding
-new fields in the middle of a struct or class type. The same confusion might
-arise when changing the order of fields.
+With plain initializer lists, it is very easy to introduce bugs when adding new
+fields in the middle of a struct or class type. The same confusion might arise
+when changing the order of fields.
 
-C++20 supports the designated initializer syntax for aggregate types.
-By applying it, we can always be sure that aggregates are constructed correctly,
-because every variable being initialized is referenced by name.
-
-Even when compiling in a language version older than C++20, depending on your
-compiler, designated initializers are potentially supported. Therefore, the
-check is not restricted to C++20 and older. Check out the options
-``-Wc99-designator`` to get support for mixed designators in
-initializer list in C and ``-Wc++20-designator`` for support of designated
-initializers in older C++ language modes.
+C++20 supports the designated initializer syntax for aggregate types. By
+applying it, we can always be sure that aggregates are constructed correctly,
+because every variable being initialized is referenced by its name.
 
 Example:
 
@@ -42,21 +35,28 @@ instead of
 which could easily become an issue when ``i`` and ``j`` are swapped in the
 declaration of ``S``.
 
+Even when compiling in a language version older than C++20, depending on your
+compiler, designated initializers are potentially supported. Therefore, the
+check is not restricted to C++20 and newer versions. Check out the options
+``-Wc99-designator`` to get support for mixed designators in initializer list in
+C and ``-Wc++20-designator`` for support of designated initializers in older C++
+language modes.
+
 Options
 -------
 
 .. option::  IgnoreMacros
 
-  The value `false` specifies that components of initializer lists expanded
-  from macros are not checked. The default value is `true`.
+  The value `false` specifies that components of initializer lists expanded from
+  macros are not checked. The default value is `true`.
 
 .. option:: IgnoreSingleElementAggregates
 
-    The value `false` specifies that even initializers for aggregate types
-    with only a single element should be checked. The default value is `true`.
+    The value `false` specifies that even initializers for aggregate types with
+    only a single element should be checked. The default value is `true`.
 
 .. option:: RestrictToPODTypes
 
     The value `true` specifies that only Plain Old Data (POD) types shall be
-    checked. This makes the check applicable to even older C++ standards.
-    The default value is `false`.
+    checked. This makes the check applicable to even older C++ standards. The
+    default value is `false`.