aboutsummaryrefslogtreecommitdiffstats
path: root/system/doc
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 /system/doc
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 'system/doc')
-rw-r--r--system/doc/design_principles/statem.xml2
-rw-r--r--system/doc/embedded/starting.xml2
2 files changed, 2 insertions, 2 deletions
diff --git a/system/doc/design_principles/statem.xml b/system/doc/design_principles/statem.xml
index 16a901b3a5..98fd1fd69d 100644
--- a/system/doc/design_principles/statem.xml
+++ b/system/doc/design_principles/statem.xml
@@ -1410,7 +1410,7 @@ open(cast, {button,_}, Data) ->
<seealso marker="erts:erlang#start_timer/4"><c>erlang:start_timer/3,4</c></seealso>.
Most time-out tasks can be performed with the
time-out features in <c>gen_statem</c>,
- but an example of one that can not is if you should need
+ but an example of one that cannot is if you should need
the return value from
<seealso marker="erts:erlang#cancel_timer/2"><c>erlang:cancel_timer(Tref)</c></seealso>, that is; the remaining time of the timer.
</p>
diff --git a/system/doc/embedded/starting.xml b/system/doc/embedded/starting.xml
index 11bf9b412a..6888f9c959 100644
--- a/system/doc/embedded/starting.xml
+++ b/system/doc/embedded/starting.xml
@@ -231,7 +231,7 @@ exec $BINDIR/erlexec -boot $RELDIR/$VSN/start -config $RELDIR/$VSN/sys $* <
<p>If a diskless and/or read-only client node with the SASL
configuration parameter <c>static_emulator</c> set to <c>true</c>
is about to start the <c>-boot</c> and <c>-config</c> flags must be
- changed. As such a client can not read a new <c>start_erl.data</c>
+ changed. As such a client cannot read a new <c>start_erl.data</c>
file (the file is not possible to change dynamically) the boot and
config files is always fetched from the same place (but with a new
contents if a new release has been installed). The