aboutsummaryrefslogtreecommitdiffstats
path: root/lib/runtime_tools
diff options
context:
space:
mode:
authorRaimo Niskanen <[email protected]>2018-07-26 14:14:14 +0200
committerRaimo Niskanen <[email protected]>2018-07-27 10:16:17 +0200
commit37c11cda19bd9067a4e094fbde53b276d6ab0d3d (patch)
tree2573bafa6dc9ca3b47c1d4dd974590b4a924bb8b /lib/runtime_tools
parent1fd03472d3d57e57ae4ebcbf0109f82dce14b90c (diff)
downloadotp-37c11cda19bd9067a4e094fbde53b276d6ab0d3d.tar.gz
otp-37c11cda19bd9067a4e094fbde53b276d6ab0d3d.tar.bz2
otp-37c11cda19bd9067a4e094fbde53b276d6ab0d3d.zip
Change "can not" into "cannot"
I did not find any legitimate use of "can not", however skipped changing e.g RFCs archived in the source tree.
Diffstat (limited to 'lib/runtime_tools')
-rw-r--r--lib/runtime_tools/doc/src/dbg.xml4
1 files changed, 2 insertions, 2 deletions
diff --git a/lib/runtime_tools/doc/src/dbg.xml b/lib/runtime_tools/doc/src/dbg.xml
index 3262cafefc..ae60b610ed 100644
--- a/lib/runtime_tools/doc/src/dbg.xml
+++ b/lib/runtime_tools/doc/src/dbg.xml
@@ -113,7 +113,7 @@
<p>The imported variables will be replaced by match_spec
<c>const</c> expressions, which is consistent with the
static scoping for Erlang <c>fun()</c>s. Local or global
- function calls can not be in the guard or body of the fun
+ function calls cannot be in the guard or body of the fun
however. Calls to builtin match_spec functions of course is
allowed:</p>
<pre>
@@ -756,7 +756,7 @@ Error: fun containing local erlang function calls ('is_atomm' called in guard)\
<c>cant_add_local_node</c> is returned.
</p>
<p>If a trace port (see <seealso marker="#trace_port-2"><c>trace_port/2</c></seealso>) is
- running on the local node, remote nodes can not be traced with
+ running on the local node, remote nodes cannot be traced with
a tracer process. The error reason
<c>cant_trace_remote_pid_to_local_port</c> is returned. A
trace port can however be started on the remote node with the