Author: Kazu Hirata
Date: 2025-05-25T08:20:04-07:00
New Revision: 6235479db3b34e52e7f58a8f587372f4f818d68a

URL: 
https://github.com/llvm/llvm-project/commit/6235479db3b34e52e7f58a8f587372f4f818d68a
DIFF: 
https://github.com/llvm/llvm-project/commit/6235479db3b34e52e7f58a8f587372f4f818d68a.diff

LOG: [lldb] Fix a typo in documentation (#141384)

Added: 
    

Modified: 
    lldb/docs/use/python-reference.rst

Removed: 
    


################################################################################
diff  --git a/lldb/docs/use/python-reference.rst 
b/lldb/docs/use/python-reference.rst
index 4bf0cb075064b..325d0685d9d38 100644
--- a/lldb/docs/use/python-reference.rst
+++ b/lldb/docs/use/python-reference.rst
@@ -609,7 +609,7 @@ special needs.
 The easiest way to do this is to derive your new command from the 
lldb.ParsedCommand
 class.  That responds in the same way to the help & repeat command interfaces, 
and
 provides some convenience methods, and most importantly an 
LLDBOptionValueParser,
-accessed throught lldb.ParsedCommand.get_parser().  The parser is used to set
+accessed through lldb.ParsedCommand.get_parser().  The parser is used to set
 your command definitions, and to retrieve option values in the __call__ method.
 
 To set up the command definition, implement the ParsedCommand abstract method:


        
_______________________________________________
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits

Reply via email to