Fix typos in documentation

Author: kazutakahirata

clang-tools-extra/docs/clang-tidy/checks/clang-analyzer/security.insecureAPI.DeprecatedOrUnsafeBufferHandling.rst

@@ -5,7 +5,7 @@
 clang-analyzer-security.insecureAPI.DeprecatedOrUnsafeBufferHandling
 ====================================================================
 
-Warn on uses of unsecure or deprecated buffer manipulating functions.
+Warn on uses of insecure or deprecated buffer manipulating functions.
 
 The `clang-analyzer-security.insecureAPI.DeprecatedOrUnsafeBufferHandling` check is an alias, please see
 `Clang Static Analyzer Available Checkers

clang/docs/LanguageExtensions.rst

@@ -3163,7 +3163,7 @@ avoid cache misses when the developer has a good understanding of which data
 are going to be used next. ``addr`` is the address that needs to be brought into
 the cache. ``rw`` indicates the expected access mode: ``0`` for *read* and ``1``
 for *write*. In case of *read write* access, ``1`` is to be used. ``locality``
-indicates the expected persistance of data in cache, from ``0`` which means that
+indicates the expected persistence of data in cache, from ``0`` which means that
 data can be discarded from cache after its next use to ``3`` which means that
 data is going to be reused a lot once in cache. ``1`` and ``2`` provide
 intermediate behavior between these two extremes.

clang/docs/ReleaseNotes.rst

@@ -221,7 +221,7 @@ Bug Fixes to C++ Support
 
 - Expressions producing ``nullptr`` are correctly evaluated
   by the constant interpreter when appearing as the operand
-  of a binary comparision.
+  of a binary comparison.
   (`#64923 <https://github.com/llvm/llvm-project/issues/64923>_``)
 
 - Fix a crash when an immediate invocation is not a constant expression

clang/docs/analyzer/developer-docs/nullability.rst

@@ -62,7 +62,7 @@ Other Issues to keep in mind/take care of:
     * Even though the method might return a nonnull pointer, when it was sent to a nullable pointer the return type will be nullable.
   	* The result is nullable unless the receiver is known to be non null.
 
-  * Sending a message to a unspecified or nonnull pointer
+  * Sending a message to an unspecified or nonnull pointer
 
     * If the pointer is not assumed to be nil, we should be optimistic and use the nullability implied by the method.
 

lldb/docs/python_api_enums.rst

@@ -504,7 +504,7 @@ ValueType
 
 .. py:data:: eValueTypeVariableArgument
 
-   Funfction argument variable.
+   Function argument variable.
 
 .. py:data:: eValueTypeVariableLocal
 

llvm/docs/AMDGPUUsage.rst

@@ -966,10 +966,10 @@ The AMDGPU backend implements the following LLVM IR intrinsics.
   LLVM Intrinsic                                   Description
   ==============================================   ==========================================================
   llvm.amdgcn.sqrt                                 Provides direct access to v_sqrt_f64, v_sqrt_f32 and v_sqrt_f16
-                                                   (on targets with half support). Peforms sqrt function.
+                                                   (on targets with half support). Performs sqrt function.
 
   llvm.amdgcn.log                                  Provides direct access to v_log_f32 and v_log_f16
-                                                   (on targets with half support). Peforms log2 function.
+                                                   (on targets with half support). Performs log2 function.
 
   llvm.amdgcn.exp2                                 Provides direct access to v_exp_f32 and v_exp_f16
                                                    (on targets with half support). Performs exp2 function.

llvm/docs/Atomics.rst

@@ -286,7 +286,7 @@ Relevant standard
 
 Notes for frontends
   If you are writing a frontend which uses this directly, use with caution.
-  Release only provides a semantic guarantee when paired with a Acquire
+  Release only provides a semantic guarantee when paired with an Acquire
   operation.
 
 Notes for optimizers

llvm/docs/Coroutines.rst

@@ -1606,7 +1606,7 @@ Overview:
 """""""""
 
 The '``llvm.coro.suspend.async``' intrinsic marks the point where
-execution of a async coroutine is suspended and control is passed to a callee.
+execution of an async coroutine is suspended and control is passed to a callee.
 
 Arguments:
 """"""""""

llvm/docs/GlobalISel/MIRPatterns.rst

@@ -63,7 +63,7 @@ Semantics:
     other patterns in that rule/alternative can simply use ``$x``
     (``i32:$x`` is redundant).
 
-* A nammed operand's behavior depends on whether the name has been seen before.
+* A named operand's behavior depends on whether the name has been seen before.
 
   * For match patterns, reusing an operand name checks that the operands
     are identical (see example 2 below).

llvm/docs/MyFirstTypoFix.rst

@@ -316,7 +316,7 @@ the change was made.
    $ git commit -am "[Diagnostic] Clarify -Winfinite-recursion message"
 
 Now we're ready to send this change out into the world! By the way,
-There is a unwritten convention of using tag for your commit. Tags
+There is an unwritten convention of using tag for your commit. Tags
 usually represent modules that you intend to modify. If you don't know
 the tags for your modules, you can look at the commit history :
 https://github.com/llvm/llvm-project/commits/main.