aboutsummaryrefslogtreecommitdiffstats
path: root/lib/syntax_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/syntax_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/syntax_tools')
-rw-r--r--lib/syntax_tools/src/igor.erl2
1 files changed, 1 insertions, 1 deletions
diff --git a/lib/syntax_tools/src/igor.erl b/lib/syntax_tools/src/igor.erl
index 16e3511734..b712b77e9f 100644
--- a/lib/syntax_tools/src/igor.erl
+++ b/lib/syntax_tools/src/igor.erl
@@ -660,7 +660,7 @@ merge_files1(Files, Opts) ->
%% transitions), code replacement is expected to be detected. Then, if
%% we in the merged code do not check at these points if the
%% <em>target</em> module (the result of the merge) has been replaced,
-%% we can not be sure in general that we will be able to do code
+%% we cannot be sure in general that we will be able to do code
%% replacement of the merged state machine - it could run forever
%% without detecting the code change. Therefore, all such calls must
%% remain remote-calls (detecting code changes), but may call the target