Skip to content

[lldb][Docs] Fix typo in tutorial.rst #111326

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Oct 8, 2024
Merged

Conversation

surinrasu
Copy link

No description provided.

Copy link

github-actions bot commented Oct 7, 2024

Thank you for submitting a Pull Request (PR) to the LLVM Project!

This PR will be automatically labeled and the relevant teams will be notified.

If you wish to, you can add reviewers by using the "Reviewers" section on this page.

If this is not working for you, it is probably because you do not have write permissions for the repository. In which case you can instead tag reviewers by name in a comment by using @ followed by their GitHub username.

If you have received no comments on your PR for a week, you can request a review by "ping"ing the PR by adding a comment “Ping”. The common courtesy "ping" rate is once a week. Please remember that you are asking for valuable time from other developers.

If you have further questions, they may be answered by the LLVM GitHub User Guide.

You can also ask questions in a comment on this PR, on the LLVM Discord or on the forums.

@llvmbot llvmbot added the lldb label Oct 7, 2024
@llvmbot
Copy link
Member

llvmbot commented Oct 7, 2024

@llvm/pr-subscribers-lldb

Author: 苏灵素@夏日限定 (Surinrasu)

Changes

Full diff: https://github.com/llvm/llvm-project/pull/111326.diff

1 Files Affected:

  • (modified) lldb/docs/use/tutorial.rst (+3-3)
diff --git a/lldb/docs/use/tutorial.rst b/lldb/docs/use/tutorial.rst
index 76e8ac4aeab89c..7bfe1743b917f6 100644
--- a/lldb/docs/use/tutorial.rst
+++ b/lldb/docs/use/tutorial.rst
@@ -210,7 +210,7 @@ you will have to indicate these are not option markers by putting ``--`` after t
 command name, but before your command string.
 
 LLDB also has a built-in Python interpreter, which is accessible by the
-``"script`` command. All the functionality of the debugger is available as classes
+``script`` command. All the functionality of the debugger is available as classes
 in the Python interpreter, so the more complex commands that in GDB you would
 introduce with the ``define`` command can be done by writing Python functions
 using the LLDB Python library, then loading the scripts into your running
@@ -331,8 +331,8 @@ do:
 
 ::
 
-   (lldb) help <breakpt-id> <breakpt-id> -- Breakpoint ID's consist major and
-   minor numbers; the major etc...
+   (lldb) help <breakpt-id>
+   <breakpt-id> -- Breakpoint ID's consist major and minor numbers; the major etc...
 
 Breakpoint Names
 ----------------

@JDevlieghere JDevlieghere merged commit 646aa81 into llvm:main Oct 8, 2024
11 checks passed
Copy link

github-actions bot commented Oct 8, 2024

@surinrasu Congratulations on having your first Pull Request (PR) merged into the LLVM Project!

Your changes will be combined with recent changes from other authors, then tested by our build bots. If there is a problem with a build, you may receive a report in an email or a comment on this PR.

Please check whether problems have been caused by your change specifically, as the builds can include changes from many authors. It is not uncommon for your change to be included in a build that fails due to someone else's changes, or infrastructure issues.

How to do this, and the rest of the post-merge process, is covered in detail here.

If your change does cause a problem, it may be reverted, or you can revert it yourself. This is a normal part of LLVM development. You can fix your changes and open a new PR to merge them again.

If you don't get any reports, no action is required from you. Your changes are working as expected, well done!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants