diff options
author | Tuncer Ayaz <[email protected]> | 2011-08-31 15:20:33 +0200 |
---|---|---|
committer | Tuncer Ayaz <[email protected]> | 2011-09-15 00:12:10 +0200 |
commit | 044a09a57b2fe383062b35b6697c7406f8e8b4b6 (patch) | |
tree | 7354611a592e5685fb237a19c43da8e68fd98275 | |
parent | d15f145c4b459bb7bf3e31dd66f7cd703d4c4fb8 (diff) | |
download | otp-044a09a57b2fe383062b35b6697c7406f8e8b4b6.tar.gz otp-044a09a57b2fe383062b35b6697c7406f8e8b4b6.tar.bz2 otp-044a09a57b2fe383062b35b6697c7406f8e8b4b6.zip |
Fix misspelling of accidentally
-rw-r--r-- | erts/doc/src/notes.xml | 2 | ||||
-rw-r--r-- | lib/inets/doc/src/notes_history.xml | 2 | ||||
-rw-r--r-- | lib/kernel/doc/src/notes.xml | 2 |
3 files changed, 3 insertions, 3 deletions
diff --git a/erts/doc/src/notes.xml b/erts/doc/src/notes.xml index 3733fb2db9..3e9e6a35f2 100644 --- a/erts/doc/src/notes.xml +++ b/erts/doc/src/notes.xml @@ -4534,7 +4534,7 @@ The race occurred when a process removed a table during termination simultaneously as another process removed the same table via <c>ets:delete/1</c> and a third process - created a table that accidentaly got the same internal + created a table that accidentally got the same internal table index as the table being removed.</p> <p> Own Id: OTP-7349</p> diff --git a/lib/inets/doc/src/notes_history.xml b/lib/inets/doc/src/notes_history.xml index 6480bad758..f70ce5cf46 100644 --- a/lib/inets/doc/src/notes_history.xml +++ b/lib/inets/doc/src/notes_history.xml @@ -123,7 +123,7 @@ re-receive of acknowledgments. If multiple copies of the same acknowledgments is received the spurious ones are silently ignored. This fix was intended for inets-4.7.14 - but accidentaly it was not included in that release.</p> + but accidentally it was not included in that release.</p> <p>Own Id: OTP-6706 Aux Id: OTP-6691 </p> </item> </list> diff --git a/lib/kernel/doc/src/notes.xml b/lib/kernel/doc/src/notes.xml index e325443f6c..fc8360b3d1 100644 --- a/lib/kernel/doc/src/notes.xml +++ b/lib/kernel/doc/src/notes.xml @@ -2535,7 +2535,7 @@ <c>badarg</c> if a process is already registered. As it turns out there is no check in <c>global</c> if a process is registered under more than one name. If some process is - accidentaly or by design given several names, it is + accidentally or by design given several names, it is possible that the name registry becomes inconsistent due to the way the resolve function is called when name clashes are discovered (see <c>register_name/3</c> in |