[llvm] [NFC] Fix typos in llvm-mc doc (PR #72457)
via llvm-commits
llvm-commits at lists.llvm.org
Wed Nov 15 16:34:21 PST 2023
llvmbot wrote:
<!--LLVM PR SUMMARY COMMENT-->
@llvm/pr-subscribers-llvm-binary-utilities
Author: Jacob Lambert (lamb-j)
<details>
<summary>Changes</summary>
---
Full diff: https://github.com/llvm/llvm-project/pull/72457.diff
1 Files Affected:
- (modified) llvm/docs/CommandGuide/llvm-mc.rst (+6-6)
``````````diff
diff --git a/llvm/docs/CommandGuide/llvm-mc.rst b/llvm/docs/CommandGuide/llvm-mc.rst
index ea1fbf482550de5..20ece823cf3b24b 100644
--- a/llvm/docs/CommandGuide/llvm-mc.rst
+++ b/llvm/docs/CommandGuide/llvm-mc.rst
@@ -11,13 +11,13 @@ SYNOPSIS
DESCRIPTION
-----------
-The :program:`llvm-mc` command take input as the assembly code for a specified
-architecture and generate object file or executable as a output for a specified
-architecture.
+The :program:`llvm-mc` command takes as input assembly code for a specified
+architecture and generates as output an object file or executable for a
+specified architecture.
-:program:`llvm-mc` provide powerful set of the tool for working with the
-machine code such as encoding of their instruction and their internal
-representation, disassemble string to bytes etc.
+:program:`llvm-mc` provides a powerful tool for working with machine code,
+such as encoding of instructions and displaying their internal representations,
+disassembling strings to bytes, etc.
The choice of architecture for the output assembly code is automatically
determined from the input file, unless the :option:`--arch` option is used to
``````````
</details>
https://github.com/llvm/llvm-project/pull/72457
More information about the llvm-commits
mailing list