summaryrefslogtreecommitdiffstats
path: root/lldb/www
diff options
context:
space:
mode:
authorBruce Mitchener <bruce.mitchener@gmail.com>2015-06-18 05:27:05 +0000
committerBruce Mitchener <bruce.mitchener@gmail.com>2015-06-18 05:27:05 +0000
commit58ef391f3ef80cc4e4e375b7e2f1f397afd47b90 (patch)
tree5745c92f275d16ef1c8c47b79e523929b3169a36 /lldb/www
parent8b2492f2a0e0b143c4c4f17765901e568af92e68 (diff)
downloadbcm5719-llvm-58ef391f3ef80cc4e4e375b7e2f1f397afd47b90.tar.gz
bcm5719-llvm-58ef391f3ef80cc4e4e375b7e2f1f397afd47b90.zip
Fix a variety of typos.
No functional change. llvm-svn: 239995
Diffstat (limited to 'lldb/www')
-rwxr-xr-xlldb/www/python-reference.html4
-rw-r--r--lldb/www/python_reference/lldb-module.html4
-rw-r--r--lldb/www/python_reference/lldb-pysrc.html4
-rw-r--r--lldb/www/remote.html2
4 files changed, 7 insertions, 7 deletions
diff --git a/lldb/www/python-reference.html b/lldb/www/python-reference.html
index bb4506229f5..4869c4fbfc4 100755
--- a/lldb/www/python-reference.html
+++ b/lldb/www/python-reference.html
@@ -418,7 +418,7 @@ Enter your Python command(s). Type 'DONE' to end.
<code>
<font color=blue>class</font> CommandObjectType:<br/>
&nbsp;&nbsp;&nbsp;&nbsp;<font color=blue>def</font> __init__(self, debugger, session_dict):<br/>
- &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<i>this call should initialize the command with respect to the command interpeter for the passed-in debugger</i> <br/>
+ &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<i>this call should initialize the command with respect to the command interpreter for the passed-in debugger</i> <br/>
&nbsp;&nbsp;&nbsp;&nbsp;<font color=blue>def</font> __call__(self, debugger, command, exe_ctx, result): <br/>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<i>this is the actual bulk of the command, akin to Python command functions</i> <br/>
&nbsp;&nbsp;&nbsp;&nbsp;<font color=blue>def</font> get_short_help(self): <br/>
@@ -444,7 +444,7 @@ Enter your Python command(s). Type 'DONE' to end.
<p>where <b>debugger</b> and <b>internal_dict</b> are as above, that function will get run when the module is loaded
allowing you to add whatever commands you want into the current debugger. Note that
- this function will only be run when using the LLDB comand <b>command script import</b>,
+ this function will only be run when using the LLDB command <b>command script import</b>,
it will not get run if anyone imports your module from another module.
If you want to always run code when your module is loaded from LLDB
<u>or</u> when loaded via an <b>import</b> statement in python code
diff --git a/lldb/www/python_reference/lldb-module.html b/lldb/www/python_reference/lldb-module.html
index dc972a752fd..5b351bceb7d 100644
--- a/lldb/www/python_reference/lldb-module.html
+++ b/lldb/www/python_reference/lldb-module.html
@@ -71,9 +71,9 @@ o SBFrame: Represents one of the stack frames associated with a thread. SBThread
o SBSymbolContext: A container that stores various debugger related info.
o SBValue: Represents the value of a variable, a register, or an expression.
o SBModule: Represents an executable image and its associated object and symbol
- files. SBTarget conatins SBModule(s).
+ files. SBTarget contains SBModule(s).
o SBBreakpoint: Represents a logical breakpoint and its associated settings.
- SBTarget conatins SBBreakpoint(s).
+ SBTarget contains SBBreakpoint(s).
o SBSymbol: Represents the symbol possibly associated with a stack frame.
o SBCompileUnit: Represents a compilation unit, or compiled source file.
o SBFunction: Represents a generic function, which can be inlined or not.
diff --git a/lldb/www/python_reference/lldb-pysrc.html b/lldb/www/python_reference/lldb-pysrc.html
index b9200eee28a..43a1c03a79d 100644
--- a/lldb/www/python_reference/lldb-pysrc.html
+++ b/lldb/www/python_reference/lldb-pysrc.html
@@ -77,9 +77,9 @@
<a name="L18"></a><tt class="py-lineno"> 18</tt> <tt class="py-line"><tt class="py-docstring">o SBSymbolContext: A container that stores various debugger related info.</tt> </tt>
<a name="L19"></a><tt class="py-lineno"> 19</tt> <tt class="py-line"><tt class="py-docstring">o SBValue: Represents the value of a variable, a register, or an expression.</tt> </tt>
<a name="L20"></a><tt class="py-lineno"> 20</tt> <tt class="py-line"><tt class="py-docstring">o SBModule: Represents an executable image and its associated object and symbol</tt> </tt>
-<a name="L21"></a><tt class="py-lineno"> 21</tt> <tt class="py-line"><tt class="py-docstring"> files. SBTarget conatins SBModule(s).</tt> </tt>
+<a name="L21"></a><tt class="py-lineno"> 21</tt> <tt class="py-line"><tt class="py-docstring"> files. SBTarget contains SBModule(s).</tt> </tt>
<a name="L22"></a><tt class="py-lineno"> 22</tt> <tt class="py-line"><tt class="py-docstring">o SBBreakpoint: Represents a logical breakpoint and its associated settings.</tt> </tt>
-<a name="L23"></a><tt class="py-lineno"> 23</tt> <tt class="py-line"><tt class="py-docstring"> SBTarget conatins SBBreakpoint(s).</tt> </tt>
+<a name="L23"></a><tt class="py-lineno"> 23</tt> <tt class="py-line"><tt class="py-docstring"> SBTarget contains SBBreakpoint(s).</tt> </tt>
<a name="L24"></a><tt class="py-lineno"> 24</tt> <tt class="py-line"><tt class="py-docstring">o SBSymbol: Represents the symbol possibly associated with a stack frame.</tt> </tt>
<a name="L25"></a><tt class="py-lineno"> 25</tt> <tt class="py-line"><tt class="py-docstring">o SBCompileUnit: Represents a compilation unit, or compiled source file.</tt> </tt>
<a name="L26"></a><tt class="py-lineno"> 26</tt> <tt class="py-line"><tt class="py-docstring">o SBFunction: Represents a generic function, which can be inlined or not.</tt> </tt>
diff --git a/lldb/www/remote.html b/lldb/www/remote.html
index 913228a0abc..e5fc2d2b6a6 100644
--- a/lldb/www/remote.html
+++ b/lldb/www/remote.html
@@ -64,7 +64,7 @@
<p>
On Linux and Android, all required remote functionality is contained in the
<code>lldb-server</code> binary. This binary combines the functionality of the
- platform and gdb-remote stub. A single binary fascilitates deployment and reduces
+ platform and gdb-remote stub. A single binary facilitates deployment and reduces
code size, since the two functions share a lot of code. The
<code>lldb-server</code> binary is also statically linked with the rest of LLDB
(unlike <code>lldb</code>, which dynamically links to <code>liblldb.so</code> by
OpenPOWER on IntegriCloud