[lldb] Proofread formatting.rst#149768
Merged
kazutakahirata merged 2 commits intollvm:mainfrom Jul 21, 2025
Merged
Conversation
Member
|
@llvm/pr-subscribers-lldb Author: Kazu Hirata (kazutakahirata) ChangesFull diff: https://github.com/llvm/llvm-project/pull/149768.diff 1 Files Affected:
diff --git a/lldb/docs/use/formatting.rst b/lldb/docs/use/formatting.rst
index 21b3ca1912b02..af0d03ecc19f2 100644
--- a/lldb/docs/use/formatting.rst
+++ b/lldb/docs/use/formatting.rst
@@ -3,7 +3,7 @@ Frame and Thread Format
LLDB has a facility to allow users to define the format of the information that
generates the descriptions for threads and stack frames. Typically when your
-program stops at a breakpoint you will get two lines that describes why your
+program stops at a breakpoint you will get two lines that describe why your
thread stopped and where:
::
@@ -192,7 +192,7 @@ you to desensitize control characters and also emit non-printable characters.
Desensitizing Characters in the Format String
---------------------------------------------
-The backslash control character allows your to enter the typical ``\a``,
+The backslash control character allows you to enter the typical ``\a``,
``\b``, ``\f``, ``\n``, ``\r``, ``\t``, ``\v``, ``\\``, characters and along
with the standard octal representation ``\0123`` and hex ``\xAB`` characters.
This allows you to enter escape characters into your format strings and will
@@ -203,7 +203,7 @@ Scoping
Many times the information that you might have in your prompt might not be
available and you won``t want it to print out if it isn``t valid. To take care
-of this you can enclose everything that must resolve into a scope. A scope is
+of this you can enclose everything that must resolve into a scope. A scope
starts with ``{`` and ends with ``}``. For example in order to only display the
current frame line table entry basename and line number when the information is
available for the current frame:
@@ -269,7 +269,7 @@ thread information:
frame #0: 0x0000000100000e85 a.out`main + 4 at test.c:19
frame #1: 0x0000000100000e40 a.out`start + 52
-The frame related variables are:
+The frame-related variables are:
- ``${file.*}``
- ``${frame.*}``
|
DavidSpickett
approved these changes
Jul 21, 2025
Collaborator
DavidSpickett
left a comment
There was a problem hiding this comment.
With the lack of apostrophes fixed, this LGTM.
This was referenced Jul 23, 2025
mahesh-attarde
pushed a commit
to mahesh-attarde/llvm-project
that referenced
this pull request
Jul 28, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
No description provided.