[llvm] 32870da - Fix typos in documentation

[Kazu Hirata via llvm-commits]

Author: Chris Cotter
Date: 2023-08-13T23:46:44-07:00
New Revision: 32870da3ba38ab0ab0710867d92465aacc6349e6

URL: https://github.com/llvm/llvm-project/commit/32870da3ba38ab0ab0710867d92465aacc6349e6
DIFF: https://github.com/llvm/llvm-project/commit/32870da3ba38ab0ab0710867d92465aacc6349e6.diff

LOG: Fix typos in documentation

Added: 
    

Modified: 
    clang-tools-extra/docs/ReleaseNotes.rst
    clang-tools-extra/docs/clang-tidy/checks/modernize/use-std-print.rst
    clang/docs/analyzer/checkers.rst
    libc/docs/contributing.rst
    libcxx/docs/Modules.rst
    llvm/docs/CommandGuide/llvm-symbolizer.rst
    llvm/docs/FatLTO.rst

Removed: 
    


################################################################################
diff  --git a/clang-tools-extra/docs/ReleaseNotes.rst b/clang-tools-extra/docs/ReleaseNotes.rst
index 122ec5fe6e0d31..46cda6a8caf1f5 100644
--- a/clang-tools-extra/docs/ReleaseNotes.rst
+++ b/clang-tools-extra/docs/ReleaseNotes.rst
@@ -196,7 +196,7 @@ Changes in existing checks
 
 - Improved :doc:`misc-include-cleaner
   <clang-tidy/checks/misc/include-cleaner>` check by adding option
-  `DeduplicateFindings` to output one finding per symbol occurence.
+  `DeduplicateFindings` to output one finding per symbol occurrence.
 
 - Improved :doc:`modernize-loop-convert
   <clang-tidy/checks/modernize/loop-convert>` to support for-loops with

diff  --git a/clang-tools-extra/docs/clang-tidy/checks/modernize/use-std-print.rst b/clang-tools-extra/docs/clang-tidy/checks/modernize/use-std-print.rst
index 378caccf611bb8..9bb691e9d9512e 100644
--- a/clang-tools-extra/docs/clang-tidy/checks/modernize/use-std-print.rst
+++ b/clang-tools-extra/docs/clang-tidy/checks/modernize/use-std-print.rst
@@ -81,7 +81,7 @@ If the call is deemed suitable for conversion then:
   is of ``signed char`` or ``unsigned char`` type are wrapped in a
   ``reinterpret_cast<const char *>``.
 - any arguments where the format string and the parameter 
diff er in
-  signedness will be wrapped in an approprate ``static_cast`` if `StrictMode`
+  signedness will be wrapped in an appropriate ``static_cast`` if `StrictMode`
   is enabled.
 - any arguments that end in a call to ``std::string::c_str()`` or
   ``std::string::data()`` will have that call removed.

diff  --git a/clang/docs/analyzer/checkers.rst b/clang/docs/analyzer/checkers.rst
index b7860af80c200d..98cf799ae46280 100644
--- a/clang/docs/analyzer/checkers.rst
+++ b/clang/docs/analyzer/checkers.rst
@@ -2499,7 +2499,7 @@ and add the `csa_mark_sanitized` function.
 
 Then calling `csa_mark_sanitized(X)` will tell the analyzer that `X` is safe to
 be used after this point, because its contents are verified. It is the
-responisibility of the programmer to ensure that this verification was indeed
+responsibility of the programmer to ensure that this verification was indeed
 correct. Please note that `csa_mark_sanitized` function is only declared and
 used during Clang Static Analysis and skipped in (production) builds.
 

diff  --git a/libc/docs/contributing.rst b/libc/docs/contributing.rst
index 7f02630145eb9c..50151348f88057 100644
--- a/libc/docs/contributing.rst
+++ b/libc/docs/contributing.rst
@@ -13,7 +13,7 @@ a list of open projects that one can start with:
    `LLVM style <https://llvm.org/docs/CodingStandards.html>`_ but 
diff ers in a
    few aspects: We use ``snake_case`` for non-constant variable and function
    names,``CamelCase`` for internal type names (those which are not defined in a
-   public header), and ``CAPITILIZED_SNAKE_CASE`` for constants. When we started
+   public header), and ``CAPITALIZED_SNAKE_CASE`` for constants. When we started
    working on the project, we started using the general LLVM style for
    everything. However, for a short period, we switched to the style that is
    currently followed by the `LLD project <https://github.com/llvm/llvm-project/tree/main/lld>`_.

diff  --git a/libcxx/docs/Modules.rst b/libcxx/docs/Modules.rst
index 504ec98db8526e..f5efb454994a20 100644
--- a/libcxx/docs/Modules.rst
+++ b/libcxx/docs/Modules.rst
@@ -7,7 +7,7 @@ Modules in libc++
 .. warning:: Modules are an experimental feature. It has additional build
              requirements and not all libc++ configurations are supported yet.
 
-             The work is still in an early developement state and not
+             The work is still in an early development state and not
              considered stable nor complete
 
 This page contains information regarding C++23 module support in libc++.

diff  --git a/llvm/docs/CommandGuide/llvm-symbolizer.rst b/llvm/docs/CommandGuide/llvm-symbolizer.rst
index fa4f2a0da341ae..d058cde98f1b0e 100644
--- a/llvm/docs/CommandGuide/llvm-symbolizer.rst
+++ b/llvm/docs/CommandGuide/llvm-symbolizer.rst
@@ -268,7 +268,7 @@ OPTIONS
   ``#<number>[.<inline>] <address> <function> <file>:<line>:<col> (<module>+<relative address>)``
 
   ``<inline>`` provides frame numbers for calls inlined into the caller
-  coresponding to ``<number>``. The inlined call numbers start at 1 and increase
+  corresponding to ``<number>``. The inlined call numbers start at 1 and increase
   from callee to caller.
 
   ``<address>`` is an address inside the call instruction to the function.  The

diff  --git a/llvm/docs/FatLTO.rst b/llvm/docs/FatLTO.rst
index 5773a30b7ae4a0..b505bb2a96fe16 100644
--- a/llvm/docs/FatLTO.rst
+++ b/llvm/docs/FatLTO.rst
@@ -67,7 +67,7 @@ extending support to other linkers isn't planned for now.
 .. NOTE
    For standard linking the fat object files should be usable by any
    linker capable of using ELF objects, since the ``.llvm.lto`` section is
-   marked ``SHF_EXLUDE``.
+   marked ``SHF_EXCLUDE``.
 
 Supported File Formats
 ----------------------