[llvm][docs]: fix typos (#71303)

llvm/docs/CommandGuide/dsymutil.rst

@@ -34,7 +34,7 @@ OPTIONS
 
 .. option:: --build-variant-suffix <suffix=buildvariant>
 
- Specify the build variant suffix used to build the executabe file.
+ Specify the build variant suffix used to build the executable file.
  There can be multiple variants for the binary of a product, each built
  slightly differently. The most common build variants are 'debug' and
  'profile'. Setting the DYLD_IMAGE_SUFFIX environment variable will

llvm/docs/CommandGuide/llvm-remarkutil.rst

@@ -123,7 +123,7 @@ Summary
 ^^^^^^^
 
 :program:`llvm-remarkutil count` counts `remarks <https://llvm.org/docs/Remarks.html>` based on specified properties.
-By default the tool counts remarks based on how many occour in a source file or function or total for the generated remark file.
+By default the tool counts remarks based on how many occur in a source file or function or total for the generated remark file.
 The tool also supports collecting count based on specific remark arguments. The specified arguments should have an integer value to be able to report a count.
 
 The tool contains utilities to filter the remark count based on remark name, pass name, argument value and remark type.
@@ -149,7 +149,7 @@ OPTIONS
   * ``Total``: Report a count for the provided remark file.
 
 .. option:: --args[=arguments]
-  If `count-by` is set to `arg` this flag can be used to collect from specified remark arguments represented as a comma seperated string.
+  If `count-by` is set to `arg` this flag can be used to collect from specified remark arguments represented as a comma separated string.
   The arguments must have a numeral value to be able to count remarks by
 
 .. option:: --rargs[=arguments]

llvm/docs/LangRef.rst

@@ -6135,7 +6135,7 @@ The current supported opcode vocabulary is limited:
   instruction.
 
   Because ``DW_OP_LLVM_entry_value`` is defined in terms of registers, it is
-  usually used in MIR, but it is also allowed in LLVM IR when targetting a
+  usually used in MIR, but it is also allowed in LLVM IR when targeting a
   :ref:`swiftasync <swiftasync>` argument. The operation is introduced by:
 
     - ``LiveDebugValues`` pass, which applies it to function parameters that

llvm/docs/LoopTerminology.rst

@@ -158,7 +158,7 @@ a dominating header.
 
 * The `FixIrreducible <https://llvm.org/doxygen/FixIrreducible_8h.html>`_
   pass can transform irreducible control flow into loops by inserting
-  new loop headers. It is not inlcuded in any default optimization pass
+  new loop headers. It is not included in any default optimization pass
   pipeline, but is required for some back-end targets.
 
 

llvm/docs/ProgrammersManual.rst

@@ -3561,8 +3561,8 @@ Important Public Members of the ``Module`` class
 * | ``Module::global_iterator`` - Typedef for global variable list iterator
   | ``Module::const_global_iterator`` - Typedef for const_iterator.
   | ``Module::insertGlobalVariable()`` - Inserts a global variable to the list.
-  | ``Module::removeGlobalVariable()`` - Removes a global variable frome the list.
-  | ``Module::eraseGlobalVariable()`` - Removes a global variable frome the list and deletes it.
+  | ``Module::removeGlobalVariable()`` - Removes a global variable from the list.
+  | ``Module::eraseGlobalVariable()`` - Removes a global variable from the list and deletes it.
   | ``global_begin()``, ``global_end()``, ``global_size()``, ``global_empty()``
 
   These are forwarding methods that make it easy to access the contents of a