[Lldb-commits] [lldb] 23e26cb - [lldb] Fix typos in documentation

[Kazu Hirata via lldb-commits]

Author: Kazu Hirata
Date: 2023-05-23T22:10:59-07:00
New Revision: 23e26cb98d5f817b951d6e7e2346246fc937ffb6

URL: https://github.com/llvm/llvm-project/commit/23e26cb98d5f817b951d6e7e2346246fc937ffb6
DIFF: https://github.com/llvm/llvm-project/commit/23e26cb98d5f817b951d6e7e2346246fc937ffb6.diff

LOG: [lldb] Fix typos in documentation

Added: 
    

Modified: 
    lldb/docs/resources/fuzzing.rst
    lldb/docs/use/ondemand.rst
    lldb/docs/use/variable.rst

Removed: 
    


################################################################################
diff  --git a/lldb/docs/resources/fuzzing.rst b/lldb/docs/resources/fuzzing.rst
index 2b1e7bd1eaafd..b827b32e74d50 100644
--- a/lldb/docs/resources/fuzzing.rst
+++ b/lldb/docs/resources/fuzzing.rst
@@ -9,7 +9,7 @@ LLDB has fuzzers that provide automated `fuzz testing <https://en.wikipedia.org/
 Building the fuzzers
 --------------------
 
-Building the LLDB fuzzers requires a build configuration that has the address sanitizer and sanitizer coverage enabled. In addition to your regular CMake arguments, you will need these argumets to build the fuzzers:
+Building the LLDB fuzzers requires a build configuration that has the address sanitizer and sanitizer coverage enabled. In addition to your regular CMake arguments, you will need these arguments to build the fuzzers:
 
 ::
 

diff  --git a/lldb/docs/use/ondemand.rst b/lldb/docs/use/ondemand.rst
index e5aaee8889d5f..9b9ba7c36ee0d 100644
--- a/lldb/docs/use/ondemand.rst
+++ b/lldb/docs/use/ondemand.rst
@@ -79,7 +79,7 @@ debug information by relying on the symbol tables from a module. Debug
 information name indexing is one of the most expensive operations that we are
 trying to avoid with the on demand symbol loading so this is one of the main
 tradeoffs of this feature. When setting a breakpoint by function name, if the
-symbol table contains a match, the debug inforamation will be enabled for that
+symbol table contains a match, the debug information will be enabled for that
 module and the query will be completed using the debug information. This does
 mean that setting breakpoints on inline function names can fail for modules
 that have debug info, but no matches in the symbol table since inlined
@@ -94,7 +94,7 @@ previously it wouldn't fail.
 Global variable lookups rely on the same methodology as breakpoint setting by
 function name: we use the symbol tables to find a match first if debug
 information isn't enabled for a module. If we find a match in the symbol table
-for a global variable lookup, we will enable debug inforamation and complete
+for a global variable lookup, we will enable debug information and complete
 the query using the debug information. It is encouraged to not strip your
 symbol tables with this features as static variables and other non exported
 globals will not appear in the symbol table and can lead to matches not being
@@ -104,8 +104,8 @@ What other things might fail?
 -----------------------------
 
 The on demand symbol loading feature tries to limit expensive name lookups
-within debug inforamtion. As such, some lookups by name might fail when they
-wouldn't when this feature is not eabled:
+within debug information. As such, some lookups by name might fail when they
+wouldn't when this feature is not enabled:
 - Setting breakpoints by function name for inlined functions
 - Type lookups when the expression parser requests types by name
 - Global variable lookups by name when the name of the variable is stripped

diff  --git a/lldb/docs/use/variable.rst b/lldb/docs/use/variable.rst
index 1afe7c28b6b7e..1b7c049db374b 100644
--- a/lldb/docs/use/variable.rst
+++ b/lldb/docs/use/variable.rst
@@ -969,7 +969,7 @@ functions. It is possible to declare this synthetic child without
 including it in the range of children displayed by LLDB. For example,
 this subset of a synthetic children provider class would allow the
 synthetic value to be dereferenced without actually showing any
-synthtic children in the UI:
+synthetic children in the UI:
 
 .. code-block:: python