From 37c11cda19bd9067a4e094fbde53b276d6ab0d3d Mon Sep 17 00:00:00 2001
From: Raimo Niskanen
Date: Thu, 26 Jul 2018 14:14:14 +0200
Subject: 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.
---
system/doc/design_principles/statem.xml | 2 +-
system/doc/embedded/starting.xml | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
(limited to 'system')
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) ->
erlang:start_timer/3,4.
Most time-out tasks can be performed with the
time-out features in gen_statem,
- 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
erlang:cancel_timer(Tref), that is; the remaining time of the timer.
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 $* <
If a diskless and/or read-only client node with the SASL
configuration parameter static_emulator set to true
is about to start the -boot and -config flags must be
- changed. As such a client can not read a new start_erl.data
+ changed. As such a client cannot read a new start_erl.data
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
--
cgit v1.2.3