[lldb] NFC: Fix trivial typo in comments, documents, and messages

Differential Revision: https://reviews.llvm.org/D77460

5 files changed, 5 insertions, 5 deletions

diff --git a/lldb/test/API/python_api/default-constructor/TestDefaultConstructorForAPIObjects.py b/lldb/test/API/python_api/default-constructor/TestDefaultConstructorForAPIObjects.py
index e002065..09f44f5 100644
--- a/lldb/test/API/python_api/default-constructor/TestDefaultConstructorForAPIObjects.py
+++ b/lldb/test/API/python_api/default-constructor/TestDefaultConstructorForAPIObjects.py
@@ -7,7 +7,7 @@ the tests where None is passed to SB API which expects (const char *) in the
 C++ API counterpart.  Passing None should not crash lldb!
 
 There are three exceptions to the above general rules, though; API objects
-SBCommadnReturnObject, SBStream, and SBSymbolContextList, are all valid objects
+SBCommandReturnObject, SBStream, and SBSymbolContextList, are all valid objects
 after default construction.
 """
 
diff --git a/lldb/test/API/python_api/frame/TestFrames.py b/lldb/test/API/python_api/frame/TestFrames.py
index 91ac30e..6d4b7b5 100644
--- a/lldb/test/API/python_api/frame/TestFrames.py
+++ b/lldb/test/API/python_api/frame/TestFrames.py
@@ -114,7 +114,7 @@ class FrameAPITestCase(TestBase):
         if self.TraceOn():
             print("Full stack traces when stopped on the breakpoint 'c':")
             print(session.getvalue())
-        self.expect(session.getvalue(), "Argugment values displayed correctly",
+        self.expect(session.getvalue(), "Argument values displayed correctly",
                     exe=False,
                     substrs=["a((int)val=1, (char)ch='A')",
                              "a((int)val=3, (char)ch='A')"])
diff --git a/lldb/test/API/python_api/function_symbol/main.c b/lldb/test/API/python_api/function_symbol/main.c
index 7dc18d2..d5f8ceb 100644
--- a/lldb/test/API/python_api/function_symbol/main.c
+++ b/lldb/test/API/python_api/function_symbol/main.c
@@ -3,7 +3,7 @@
 // This simple program is to test the lldb Python APIs SBTarget, SBFrame,
 // SBFunction, SBSymbol, and SBAddress.
 //
-// When stopped on breakppint 1, we can get the line entry using SBFrame API
+// When stopped on breakpoint 1, we can get the line entry using SBFrame API
 // SBFrame.GetLineEntry().  We'll get the start address for the line entry
 // with the SBAddress type, resolve the symbol context using the SBTarget API
 // SBTarget.ResolveSymbolContextForAddress() in order to get the SBSymbol.
diff --git a/lldb/test/API/python_api/target/main.c b/lldb/test/API/python_api/target/main.c
index 0d0580d..7724fa7 100644
--- a/lldb/test/API/python_api/target/main.c
+++ b/lldb/test/API/python_api/target/main.c
@@ -2,7 +2,7 @@
 
 // This simple program is to test the lldb Python API SBTarget.
 //
-// When stopped on breakppint 1, and then 2, we can get the line entries using
+// When stopped on breakpoint 1, and then 2, we can get the line entries using
 // SBFrame API SBFrame.GetLineEntry().  We'll get the start addresses for the
 // two line entries; with the start address (of SBAddress type), we can then
 // resolve the symbol context using the SBTarget API
diff --git a/lldb/test/API/python_api/thread/TestThreadAPI.py b/lldb/test/API/python_api/thread/TestThreadAPI.py
index 9124138..87d4eb8 100644
--- a/lldb/test/API/python_api/thread/TestThreadAPI.py
+++ b/lldb/test/API/python_api/thread/TestThreadAPI.py
@@ -72,7 +72,7 @@ class ThreadAPITestCase(TestBase):
             "main2.cpp", "// we should reach here after 3 step-over's.")
 
         # We'll use the test method name as the exe_name for executable
-        # comppiled from main2.cpp.
+        # compiled from main2.cpp.
         self.exe_name = self.testMethodName
 
     def get_process(self):