[libc] Fix typos in documentation

Author: kazutakahirata

libcxx/docs/BuildingLibcxx.rst

@@ -10,7 +10,7 @@ Building libc++
 .. _build instructions:
 
 The instructions on this page are aimed at vendors who ship libc++ as part of an
-operating system distribution, a toolchain or similar shipping vehicules. If you
+operating system distribution, a toolchain or similar shipping vehicles. If you
 are a user merely trying to use libc++ in your program, you most likely want to
 refer to your vendor's documentation, or to the general documentation for using
 libc++ :ref:`here <using-libcxx>`.

libcxx/docs/DesignDocs/ExtendedCXX03Support.rst

@@ -88,10 +88,10 @@ in the function parameter list, and in the return type. For example:
   template <class _Tp>
   enable_if_t</*...*/> baz(_Tp); // # 3
 
-Using default template parameters for SFINAE (#1) should always be prefered.
+Using default template parameters for SFINAE (#1) should always be preferred.
 
 Option #2 has two problems. First, users can observe and accidentally pass values to the SFINAE
-function argument. Second, the default arguement creates a live variable, which causes debug
+function argument. Second, the default argument creates a live variable, which causes debug
 information to be emitted containing the text of the SFINAE.
 
 Option #3 can also cause more debug information to be emitted than is needed, because the function

libcxx/docs/DesignDocs/UnspecifiedBehaviorRandomization.rst

@@ -17,7 +17,7 @@ Consider the follow snippet which steadily happens in tests:
 
 Under this assumption all elements in the vector whose first elements are equal
 do not guarantee any order. Unfortunately, this prevents libcxx introducing
-other implementatiosn because tests might silently fail and the users might
+other implementations because tests might silently fail and the users might
 heavily depend on the stability of implementations.
 
 Goal

libcxx/docs/ReleaseNotes.rst

@@ -73,12 +73,12 @@ Deprecations and Removals
   - C++2b: ``atomic``, ``bit``, ``cstdint``, ``cstdlib``, ``cstring``, ``initializer_list``, ``limits``, ``new``,
            ``stdexcept``, ``system_error``, ``type_traits``, ``typeinfo``
 
-- ``<algorithm>`` no longer includes ``<chrono>`` in any C++ version (it was prevously included in C++17 and earlier).
+- ``<algorithm>`` no longer includes ``<chrono>`` in any C++ version (it was previously included in C++17 and earlier).
 
-- ``<string>`` no longer includes ``<vector>`` in any C++ version (it was prevously included in C++20 and earlier).
+- ``<string>`` no longer includes ``<vector>`` in any C++ version (it was previously included in C++20 and earlier).
 
 - ``<string>``, ``<string_view>``, and ``<mutex>`` no longer include ``<functional>``
-  in any C++ version (it was prevously included in C++20 and earlier).
+  in any C++ version (it was previously included in C++20 and earlier).
 
 - The headers ``<experimental/algorithm>`` and ``<experimental/functional>`` have been removed, since all the contents
   have been implemented in namespace ``std`` for at least two releases.

libcxx/docs/TestingLibcxx.rst

@@ -319,7 +319,7 @@ concatenate its arguments to a ``std::string`` and write it to ``stderr``. When
 the output can't be concatenated a default message will be written to
 ``stderr``. This is useful for tests where the arguments use different
 character types like ``char`` and ``wchar_t``, the latter can't simply be
-written to ``stderrr``.
+written to ``stderr``.
 
 This macro is in a different header as ``assert_macros.h`` since it pulls in
 additional headers.

libcxx/docs/UsingLibcxx.rst

@@ -173,7 +173,7 @@ that this function is provided by the static or shared library, so it is only av
 to a platform where the compiled library is sufficiently recent. On older platforms, the program will
 terminate in an unspecified unsuccessful manner, but the quality of diagnostics won't be great.
 However, users can also override that mechanism at two different levels. First, the mechanism can be
-overriden at compile-time by defining the ``_LIBCPP_VERBOSE_ABORT(format, args...)`` variadic macro.
+overridden at compile-time by defining the ``_LIBCPP_VERBOSE_ABORT(format, args...)`` variadic macro.
 When that macro is defined, it will be called with a format string as the first argument, followed by
 a series of arguments to format using printf-style formatting. Compile-time customization may be
 interesting to get precise control over code generation, however it is also inconvenient to use in