[Lldb-commits] [lldb] [lldb][Docs] Fix typo in `tutorial.rst` (PR #111326)

via lldb-commits lldb-commits at lists.llvm.org
Sun Oct 6 19:17:02 PDT 2024


https://github.com/Surinrasu created https://github.com/llvm/llvm-project/pull/111326

None

>From 86831746f36bb895ed4c2712012e33b8dff9dc8e Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?=E8=8B=8F=E7=81=B5=E7=B4=A0=40=E5=A4=8F=E6=97=A5=E9=99=90?=
 =?UTF-8?q?=E5=AE=9A?= <srs at surindaku.dev>
Date: Mon, 7 Oct 2024 10:12:26 +0800
Subject: [PATCH] Fix typo in `tutorial.rst`

---
 lldb/docs/use/tutorial.rst | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

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
 ----------------



More information about the lldb-commits mailing list