[libcxx-commits] [libcxx] 11e2975 - Fx typos in documentation
Kazu Hirata via libcxx-commits
libcxx-commits at lists.llvm.org
Fri Aug 18 23:36:14 PDT 2023
Author: Kazu Hirata
Date: 2023-08-18T23:36:04-07:00
New Revision: 11e2975810acd6abde9071818e03634d99492b54
URL: https://github.com/llvm/llvm-project/commit/11e2975810acd6abde9071818e03634d99492b54
DIFF: https://github.com/llvm/llvm-project/commit/11e2975810acd6abde9071818e03634d99492b54.diff
LOG: Fx typos in documentation
Added:
Modified:
clang-tools-extra/docs/clang-tidy/checks/objc/assert-equals.rst
clang/docs/ClangFormatStyleOptions.rst
clang/docs/DebuggingCoroutines.rst
clang/docs/LanguageExtensions.rst
clang/docs/OpenCLSupport.rst
clang/docs/ReleaseNotes.rst
libc/docs/porting.rst
libcxx/docs/DesignDocs/FileTimeType.rst
lldb/source/Plugins/TraceExporter/docs/htr.rst
llvm/docs/ScudoHardenedAllocator.rst
openmp/docs/CommandLineArgumentReference.rst
openmp/docs/design/Runtimes.rst
Removed:
################################################################################
diff --git a/clang-tools-extra/docs/clang-tidy/checks/objc/assert-equals.rst b/clang-tools-extra/docs/clang-tidy/checks/objc/assert-equals.rst
index b7a3e76401c468..09f5ef01c10c38 100644
--- a/clang-tools-extra/docs/clang-tidy/checks/objc/assert-equals.rst
+++ b/clang-tools-extra/docs/clang-tidy/checks/objc/assert-equals.rst
@@ -7,5 +7,5 @@ Finds improper usages of `XCTAssertEqual` and `XCTAssertNotEqual` and replaces
them with `XCTAssertEqualObjects` or `XCTAssertNotEqualObjects`.
This makes tests less fragile, as many improperly rely on pointer equality for
-strings that have equal values. This assumption is not guarantted by the
+strings that have equal values. This assumption is not guaranteed by the
language.
diff --git a/clang/docs/ClangFormatStyleOptions.rst b/clang/docs/ClangFormatStyleOptions.rst
index 651fa4436dfe78..3b3f6f2860906a 100644
--- a/clang/docs/ClangFormatStyleOptions.rst
+++ b/clang/docs/ClangFormatStyleOptions.rst
@@ -5097,7 +5097,7 @@ the configuration (without a prefix: ``Auto``).
AfterControlStatements: true
AfterFunctionDefinitionName: true
- * ``bool AfterControlStatements`` If ``true``, put space betwee control statement keywords
+ * ``bool AfterControlStatements`` If ``true``, put space between control statement keywords
(for/if/while...) and opening parentheses.
.. code-block:: c++
diff --git a/clang/docs/DebuggingCoroutines.rst b/clang/docs/DebuggingCoroutines.rst
index 842f7645f967bf..53bdd08fdbc02f 100644
--- a/clang/docs/DebuggingCoroutines.rst
+++ b/clang/docs/DebuggingCoroutines.rst
@@ -501,7 +501,7 @@ So we can use the ``continuation`` field to construct the asynchronous stack:
# In the example, the continuation is the first field member of the promise_type.
# So they have the same addresses.
# If we want to generalize the scripts to other coroutine types, we need to be sure
- # the continuation field is the first memeber of promise_type.
+ # the continuation field is the first member of promise_type.
self.continuation_addr = self.promise_addr
def next_task_addr(self):
diff --git a/clang/docs/LanguageExtensions.rst b/clang/docs/LanguageExtensions.rst
index c6f781dfe35e89..a51dea03fcb655 100644
--- a/clang/docs/LanguageExtensions.rst
+++ b/clang/docs/LanguageExtensions.rst
@@ -2410,7 +2410,7 @@ this always needs to be called to grow the table.
It takes three arguments. The first argument is the WebAssembly table
to grow. The second argument is the reference typed value to store in
the new table entries (the initialization value), and the third argument
-is the amound to grow the table by. It returns the previous table size
+is the amount to grow the table by. It returns the previous table size
or -1. It will return -1 if not enough space could be allocated.
.. code-block:: c++
diff --git a/clang/docs/OpenCLSupport.rst b/clang/docs/OpenCLSupport.rst
index 43c30970d113bf..f9b6564a9ebaac 100644
--- a/clang/docs/OpenCLSupport.rst
+++ b/clang/docs/OpenCLSupport.rst
@@ -333,7 +333,7 @@ Missing features or with limited support
- IR generation for non-trivial global destructors is incomplete (See:
`PR48047 <https://llvm.org/PR48047>`_).
-- Support of `destrutors with non-default address spaces
+- Support of `destructors with non-default address spaces
<https://www.khronos.org/opencl/assets/CXX_for_OpenCL.html#_construction_initialization_and_destruction>`_
is incomplete (See: `D109609 <https://reviews.llvm.org/D109609>`_).
diff --git a/clang/docs/ReleaseNotes.rst b/clang/docs/ReleaseNotes.rst
index 054c06ffa0f5c9..d76005692aa809 100644
--- a/clang/docs/ReleaseNotes.rst
+++ b/clang/docs/ReleaseNotes.rst
@@ -173,7 +173,7 @@ Bug Fixes to C++ Support
a Unicode character whose name contains a ``-``.
(Fixes `#64161 <https://github.com/llvm/llvm-project/issues/64161>`_)
-- Fix cases where we ignore ambiguous name lookup when looking up memebers.
+- Fix cases where we ignore ambiguous name lookup when looking up members.
(`#22413 <https://github.com/llvm/llvm-project/issues/22413>`_),
(`#29942 <https://github.com/llvm/llvm-project/issues/29942>`_),
(`#35574 <https://github.com/llvm/llvm-project/issues/35574>`_) and
diff --git a/libc/docs/porting.rst b/libc/docs/porting.rst
index 3f41eb2c969915..a3b318d3613921 100644
--- a/libc/docs/porting.rst
+++ b/libc/docs/porting.rst
@@ -11,7 +11,7 @@ Bringup on a New OS or Architecture
CI builders
===========
-If you are contributing a port for a operating system or architecture which
+If you are contributing a port for an operating system or architecture which
is not covered by existing CI builders, you will also have to present a plan
for testing and contribute a CI builder. See
`this guide <https://llvm.org/docs/HowToAddABuilder.html>`_ for information
diff --git a/libcxx/docs/DesignDocs/FileTimeType.rst b/libcxx/docs/DesignDocs/FileTimeType.rst
index a54d2bf2720440..f775fd840e2368 100644
--- a/libcxx/docs/DesignDocs/FileTimeType.rst
+++ b/libcxx/docs/DesignDocs/FileTimeType.rst
@@ -153,7 +153,7 @@ We should also consider the opposite problem of having a ``file_time_type``
that is able to represent a larger range than ``timespec``. At least in
this case ``last_write_time`` can be used to get and set all possible values
supported by the underlying filesystem; meaning ``last_write_time(p)`` will
-never throw a overflow error when retrieving a value.
+never throw an overflow error when retrieving a value.
However, this introduces a new problem, where users are allowed to attempt to
create a time point beyond what the filesystem can represent. Two particular
diff --git a/lldb/source/Plugins/TraceExporter/docs/htr.rst b/lldb/source/Plugins/TraceExporter/docs/htr.rst
index 1341cf5f0c805d..beee14dce25afb 100644
--- a/lldb/source/Plugins/TraceExporter/docs/htr.rst
+++ b/lldb/source/Plugins/TraceExporter/docs/htr.rst
@@ -21,7 +21,7 @@ Concepts
**Pass:** A transformation applied to a *layer* that generates a new *layer* that is a more summarized, consolidated representation of the trace data.
A pass merges instructions/blocks based on its specific purpose - for example, a pass designed to summarize a processor trace by function calls would merge all the blocks of a function into a single block representing the entire function.
-The image below illusrates the transformation of a trace's representation (HTR)
+The image below illustrates the transformation of a trace's representation (HTR)
.. image:: media/htr-example.png
diff --git a/llvm/docs/ScudoHardenedAllocator.rst b/llvm/docs/ScudoHardenedAllocator.rst
index 875d018c4d9ffc..3862415111960f 100644
--- a/llvm/docs/ScudoHardenedAllocator.rst
+++ b/llvm/docs/ScudoHardenedAllocator.rst
@@ -115,7 +115,7 @@ Memory reclaiming
Primary and Secondary allocators have
diff erent behaviors with regard to
reclaiming. While Secondary mapped allocations can be unmapped on deallocation,
it isn't the case for the Primary, which could lead to a steady growth of the
-RSS of a process. To counteracty this, if the underlying OS allows it, pages
+RSS of a process. To counteract this, if the underlying OS allows it, pages
that are covered by contiguous free memory blocks in the Primary can be
released: this generally means they won't count towards the RSS of a process and
be zero filled on subsequent accesses). This is done in the deallocation path,
diff --git a/openmp/docs/CommandLineArgumentReference.rst b/openmp/docs/CommandLineArgumentReference.rst
index d07d25bff26646..ceea18e953e7cc 100644
--- a/openmp/docs/CommandLineArgumentReference.rst
+++ b/openmp/docs/CommandLineArgumentReference.rst
@@ -66,7 +66,7 @@ Offloading Specific Command-Line Arguments
| It is also possible to specify :ref:`fopenmp-targets` without specifying
``--offload-arch``. In that case, the executables ``amdgpu-arch`` or
``nvptx-arch`` will be executed as part of the compiler driver to
- detect the device arhitecture automatically.
+ detect the device architecture automatically.
| Finally, the device architecture will also be automatically inferred with
``--offload-arch=native``.
diff --git a/openmp/docs/design/Runtimes.rst b/openmp/docs/design/Runtimes.rst
index c15c098f344fd4..4c848ca76fb8d5 100644
--- a/openmp/docs/design/Runtimes.rst
+++ b/openmp/docs/design/Runtimes.rst
@@ -1130,7 +1130,7 @@ LIBOMPTARGET_MIN_THREADS_FOR_LOW_TRIP_COUNT
This environment variable defines a lower bound for the number of threads if a
combined kernel, e.g., `target teams distribute parallel for`, has insufficient
parallelism. Especially if the trip count of the loops is lower than the number
-of threads possible times the number of teams (aka. blocks) the device preferes
+of threads possible times the number of teams (aka. blocks) the device prefers
(see also :ref:`LIBOMPTARGET_AMDGPU_TEAMS_PER_CU`), we will reduce the thread
count to increase outer (team/block) parallelism. The thread count will never
be reduced below the value passed for this environment variable though.
More information about the libcxx-commits
mailing list