aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorMagnus Henoch <[email protected]>2016-05-20 15:35:26 +0100
committerMagnus Henoch <[email protected]>2016-05-20 15:35:26 +0100
commitc5a18407907b316117c285046c53fb0a1795602e (patch)
treec35086b17f14dc7f4876aa3cf7eeceebb51babc4
parent2098d573b097566d598ded1444625439ee6c0ae3 (diff)
downloadotp-c5a18407907b316117c285046c53fb0a1795602e.tar.gz
otp-c5a18407907b316117c285046c53fb0a1795602e.tar.bz2
otp-c5a18407907b316117c285046c53fb0a1795602e.zip
Fix spelling of "atomicity" in ets.xml
-rw-r--r--lib/stdlib/doc/src/ets.xml4
1 files changed, 2 insertions, 2 deletions
diff --git a/lib/stdlib/doc/src/ets.xml b/lib/stdlib/doc/src/ets.xml
index ad7591e214..9fb7d227a3 100644
--- a/lib/stdlib/doc/src/ets.xml
+++ b/lib/stdlib/doc/src/ets.xml
@@ -98,10 +98,10 @@
All updates to single objects are guaranteed to be both <em>atomic</em>
and <em>isolated</em>. This means that an updating operation towards
a single object will either succeed or fail completely without any
- effect at all (atomicy).
+ effect at all (atomicity).
Nor can any intermediate results of the update be seen by other
processes (isolation). Some functions that update several objects
- state that they even guarantee atomicy and isolation for the entire
+ state that they even guarantee atomicity and isolation for the entire
operation. In database terms the isolation level can be seen as
"serializable", as if all isolated operations were carried out serially,
one after the other in a strict order.</p>