summaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
authorMiodrag Tokić <miki@loonies.io>2015-05-19 17:59:45 +0200
committerMiodrag Tokić <miki@loonies.io>2015-05-19 18:06:44 +0200
commitb9cf8d1867ba8d2e60d11d3c6144eadc2d11a162 (patch)
tree36a90d0397866078f88ef372f72a0e7cf55efc6a /doc
parent13640276b95125f84f3f1518f07afb3c2542ac35 (diff)
downloadvdebug-b9cf8d1867ba8d2e60d11d3c6144eadc2d11a162.zip
Fix misspelled words
Fix misspelled words in the help file.
Diffstat (limited to 'doc')
-rw-r--r--doc/Vdebug.txt10
1 files changed, 5 insertions, 5 deletions
diff --git a/doc/Vdebug.txt b/doc/Vdebug.txt
index 7560847..69b6928 100644
--- a/doc/Vdebug.txt
+++ b/doc/Vdebug.txt
@@ -369,7 +369,7 @@ is the port.
3.6 TCL/Wish set up *VdebugSetUpTcl*
Like Python and Ruby, Tcl and Wish have an standalone debugging tool that you
-can use from the command line, which has again been made avilable by
+can use from the command line, which has again been made available by
ActiveState.
Go to http://code.activestate.com/komodo/remotedebugging/, download the Tcl
@@ -473,7 +473,7 @@ between them. The options are shown in a sort of tab interface at the top of
the watch window, and you can switch to a different context by pressing <enter>
(<cr>) on the context you want, or double-clicking on it with your mouse if you
have mouse support enabled. The currently showing context is highlighted (if
-you have syntax highlighting on) and starts with an asterix.
+you have syntax highlighting on) and starts with an asterisk (*).
The watch window is also used to show the results of "eval" operations. See
the |VdebugEval| section for more on that. After evaluating an expression you
@@ -718,7 +718,7 @@ To remove all breakpoints in one go use the command: >
You can evaluate code snippets at the current point of execution, which can be
used to see the result of a condition, arithmetic expressions, etc. These
snippets are written in the language that's being debugged. There are two ways
-of evaluating expresions: you can either write them yourself
+of evaluating expressions: you can either write them yourself
(|VdebugEvalExpression|) or use visual highlighting to select an expression from
the source window.
@@ -740,7 +740,7 @@ The result is shown on the watch window. E.g: >
4.5.2 Evaluating highlighted expressions *VdebugEvalHighlighted*
Use visual highlighting (default command "v") to select an expression that you
-want to evalute and type "<Leader>e" (leader key followed by the letter "e").
+want to evaluate and type "<Leader>e" (leader key followed by the letter "e").
The result of the evaluation is shown on the watch window.
------------------------------------------------------------------------------
@@ -1009,7 +1009,7 @@ There are a couple of hurdles to overcome in doing this:
Firstly, file paths aren't a problem. You can use the options "remote_path" and
"local_path" to swap out sections of the file URIs to make them compatible with
-eachother.
+each other.
Let's say we're debugging a file on a remote machine, and the path is
/home/user/scripts/myscript.php. On my machine the same script is located in