[NFC] Fix typos in release notes

[STL_MSFT]

Summary

This fixes a few typos in release notes throughout the monorepo.

[MaskRay]

Thanks!

[ldionne]

Thank you!

[Mordante]

Thanks!

clang-tools-extra/docs/ReleaseNotes.rst

 
 The improvements are...
 
 Improvements to pp-trace
 ------------------------
 
 The improvements are...
 
-Clang-tidy visual studio plugin
+Clang-tidy Visual Studio plugin
 -------------------------------

clang/docs/ReleaseNotes.rst

 - The default setting of FP contraction (FMA) is now -ffp-contract=on (for
   languages other than CUDA/HIP) even when optimization is off. Previously,
   the default behavior was equivalent to -ffp-contract=off (-ffp-contract
   was not set).
   Related to this, the switch -ffp-model=precise now implies -ffp-contract=on
   rather than -ffp-contract=fast, and the documentation of these features has
   been clarified. Previously, the documentation claimed that -ffp-model=precise
   was the default, but this was incorrect because the precise model implied
-  -ffp-contract=fast, wheras the (now corrected) default behavior is
+  -ffp-contract=fast, whereas the (now corrected) default behavior is
   -ffp-contract=on.
   -ffp-model=precise is now exactly the default mode of the compiler.
 
 Internal API Changes
 --------------------
 
 - ...
 
- The ``hasAnyCapture`` matcher now only accepts an inner matcher of type
   of type ``Matcher<CXXThisExpr>`` or ``Matcher<VarDecl>``.
 
 clang-format
 ------------
 
 - Option ``AllowShortEnumsOnASingleLine: false`` has been improved, it now
   correctly places the opening brace according to ``BraceWrapping.AfterEnum``.
 
-- Option ``QualifierAligment`` has been added in order to auto-arrange the
+- Option ``QualifierAlignment`` has been added in order to auto-arrange the
   positioning of specifiers/qualifiers
   `const` `volatile` `static` `inline` `constexpr` `restrict`
   in variable and parameter declarations to be either ``Right`` aligned
   or ``Left`` aligned or ``Custom`` using ``QualifierOrder``.
 
 - Option ``QualifierOrder`` has been added to allow the order
   `const` `volatile` `static` `inline` `constexpr` `restrict`
   to be controlled relative to the `type`.

libcxx/docs/ReleaseNotes.rst

- Support for building libc++ on top of a C Standard Library that does not support ``wchar_t`` was
   added. This is useful for building libc++ in an embedded setting, and it adds itself to the various
   freestanding-friendly options provided by libc++.
 
 - ``_LIBCPP_DEBUG`` equals to ``1`` enables the randomization of unspecified
   behavior of standard algorithms (e.g. equal elements in ``std::sort`` or
   randomization of both sides of partition for ``std::nth_element``)
 
 - Floating-point support for ``std::to_chars`` support has been added.
-  Thanks to Stephan T. Lavavej and Microsoft for providing their implemention
+  Thanks to Stephan T. Lavavej and Microsoft for providing their implementation
   to libc++.
 
 API Changes
 -----------
 
 - The functions ``std::atomic<T*>::fetch_(add|sub)`` and
   ``std::atomic_fetch_(add|sub)`` no longer accept a function pointer. While
   this is technically an API break, the invalid syntax isn't supported by
-  libstc++ and MSVC STL.  See https://godbolt.org/z/49fvzz98d.
+  libstdc++ and MSVC STL.  See https://godbolt.org/z/49fvzz98d.
 
 - The call of the functions ``std::atomic_(add|sub)(std::atomic<T*>*, ...)``
   with the explicit template argument ``T`` are now ill-formed. While this is
-  technically an API break, the invalid syntax isn't supported by libstc++ and
+  technically an API break, the invalid syntax isn't supported by libstdc++ and
   MSVC STL. See https://godbolt.org/z/v9959re3v.
 
   Due to this change it's now possible to call these functions with the
   explicit template argument ``T*``. This allows using the same syntax on the
   major Standard library implementations.
   See https://godbolt.org/z/oEfzPhTTb.
 
   Calls to these functions where the template argument was deduced by the

 - Building the libc++ shared or static library requires a C++ 20 capable compiler.
   Consider using a Bootstrapping build to build libc++ with a fresh Clang if you
   can't use the system compiler to build libc++ anymore.
 
 - Historically, there has been numerous ways of building libc++ and libc++abi. This has
   culminated in over 5 different ways to build the runtimes, which made it impossible to
   maintain with a good level of support. Starting with this release, the runtimes support
   exactly two ways of being built, which should cater to all use-cases. Furthermore,
-  these builds are as lightweight as possible and will work consistently even when targetting
+  these builds are as lightweight as possible and will work consistently even when targeting
   embedded platforms, which used not to be the case. Please see the documentation on building
   libc++ to see those two ways of building and migrate over to the appropriate build instructions
   as soon as possible.
 
   All other ways to build are deprecated and will not be supported in the next release.
   We understand that making these changes can be daunting. For that reason, here's a
   summary of how to migrate from the two most common ways to build:
 

lld/docs/ReleaseNotes.rst

 
 * ``--export-dynamic-symbol-list`` has been added.
   (`D107317 <https://reviews.llvm.org/D107317>`_)
 * ``--why-extract`` has been added to query why archive members/lazy object files are extracted.
   (`D109572 <https://reviews.llvm.org/D109572>`_)
 * ``e_entry`` no longer falls back to the address of ``.text`` if the entry symbol does not exist.
   Instead, a value of 0 will be written.
   (`D110014 <https://reviews.llvm.org/D110014>`_)
-* If ``-Map`` is specified, ``--cref`` will be printted to the specified file.
+* If ``-Map`` is specified, ``--cref`` will be printed to the specified file.
   (`D114663 <https://reviews.llvm.org/D114663>`_)
 
 Architecture specific changes:
 
 * The x86-32 port now supports TLSDESC (``-mtls-dialect=gnu2``).
   (`D112582 <https://reviews.llvm.org/D112582>`_)
 * The x86-64 port now handles non-RAX/non-adjacent ``R_X86_64_GOTPC32_TLSDESC``
   and ``R_X86_64_TLSDESC_CALL`` (``-mtls-dialect=gnu2``).

polly/docs/ReleaseNotes.rst

- The command line option -polly-opt-fusion has been removed. What the
   flag does was frequently misunderstood and is rarely useful. However,
   the functionality is still accessible using
 
   .. code-block:: console
 
     -polly-isl-arg=--no-schedule-serialize-sccs
 
 - The command line option -polly-loopfusion-greedy has been added.
-  This will agressively try to fuse any loop regardless of
+  This will aggressively try to fuse any loop regardless of
   profitability. The is what users might have expected what
   -polly-opt-fusion=max would do.
 
 - Support for gfortran-generated code has been removed. This includes
   Fortran Array Descriptors (-polly-detect-fortran-arrays) and the
   -polly-rewrite-byref-params pass.