Skip to content

Commit 3a14993

Browse files
Fix typos in documentation
1 parent 2051a41 commit 3a14993

File tree

10 files changed

+11
-11
lines changed

10 files changed

+11
-11
lines changed

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

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@
55
clang-analyzer-security.insecureAPI.DeprecatedOrUnsafeBufferHandling
66
====================================================================
77

8-
Warn on uses of unsecure or deprecated buffer manipulating functions.
8+
Warn on uses of insecure or deprecated buffer manipulating functions.
99

1010
The `clang-analyzer-security.insecureAPI.DeprecatedOrUnsafeBufferHandling` check is an alias, please see
1111
`Clang Static Analyzer Available Checkers

clang/docs/LanguageExtensions.rst

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

clang/docs/ReleaseNotes.rst

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -221,7 +221,7 @@ Bug Fixes to C++ Support
221221

222222
- Expressions producing ``nullptr`` are correctly evaluated
223223
by the constant interpreter when appearing as the operand
224-
of a binary comparision.
224+
of a binary comparison.
225225
(`#64923 <https://github.com/llvm/llvm-project/issues/64923>_``)
226226

227227
- Fix a crash when an immediate invocation is not a constant expression

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

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -62,7 +62,7 @@ Other Issues to keep in mind/take care of:
6262
* Even though the method might return a nonnull pointer, when it was sent to a nullable pointer the return type will be nullable.
6363
* The result is nullable unless the receiver is known to be non null.
6464

65-
* Sending a message to a unspecified or nonnull pointer
65+
* Sending a message to an unspecified or nonnull pointer
6666

6767
* If the pointer is not assumed to be nil, we should be optimistic and use the nullability implied by the method.
6868

lldb/docs/python_api_enums.rst

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -504,7 +504,7 @@ ValueType
504504

505505
.. py:data:: eValueTypeVariableArgument
506506
507-
Funfction argument variable.
507+
Function argument variable.
508508

509509
.. py:data:: eValueTypeVariableLocal
510510

llvm/docs/AMDGPUUsage.rst

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -966,10 +966,10 @@ The AMDGPU backend implements the following LLVM IR intrinsics.
966966
LLVM Intrinsic Description
967967
============================================== ==========================================================
968968
llvm.amdgcn.sqrt Provides direct access to v_sqrt_f64, v_sqrt_f32 and v_sqrt_f16
969-
(on targets with half support). Peforms sqrt function.
969+
(on targets with half support). Performs sqrt function.
970970

971971
llvm.amdgcn.log Provides direct access to v_log_f32 and v_log_f16
972-
(on targets with half support). Peforms log2 function.
972+
(on targets with half support). Performs log2 function.
973973

974974
llvm.amdgcn.exp2 Provides direct access to v_exp_f32 and v_exp_f16
975975
(on targets with half support). Performs exp2 function.

llvm/docs/Atomics.rst

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -286,7 +286,7 @@ Relevant standard
286286

287287
Notes for frontends
288288
If you are writing a frontend which uses this directly, use with caution.
289-
Release only provides a semantic guarantee when paired with a Acquire
289+
Release only provides a semantic guarantee when paired with an Acquire
290290
operation.
291291

292292
Notes for optimizers

llvm/docs/Coroutines.rst

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1606,7 +1606,7 @@ Overview:
16061606
"""""""""
16071607

16081608
The '``llvm.coro.suspend.async``' intrinsic marks the point where
1609-
execution of a async coroutine is suspended and control is passed to a callee.
1609+
execution of an async coroutine is suspended and control is passed to a callee.
16101610

16111611
Arguments:
16121612
""""""""""

llvm/docs/GlobalISel/MIRPatterns.rst

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -63,7 +63,7 @@ Semantics:
6363
other patterns in that rule/alternative can simply use ``$x``
6464
(``i32:$x`` is redundant).
6565

66-
* A nammed operand's behavior depends on whether the name has been seen before.
66+
* A named operand's behavior depends on whether the name has been seen before.
6767

6868
* For match patterns, reusing an operand name checks that the operands
6969
are identical (see example 2 below).

llvm/docs/MyFirstTypoFix.rst

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

0 commit comments

Comments
 (0)