aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorBjörn Gustavsson <[email protected]>2018-11-26 09:52:32 +0100
committerBjörn Gustavsson <[email protected]>2018-11-26 09:52:32 +0100
commit791742877a893e41d17bf2fd6b0e10c3dfebec8b (patch)
tree0da4e3fdbcc60ee7d4a91295ebcd43fe46a44c68
parentf8b185e6cc50ea3799eef4e3c395f82e935125c8 (diff)
downloadotp-791742877a893e41d17bf2fd6b0e10c3dfebec8b.tar.gz
otp-791742877a893e41d17bf2fd6b0e10c3dfebec8b.tar.bz2
otp-791742877a893e41d17bf2fd6b0e10c3dfebec8b.zip
persistent_term.xml: Fix spelling
-rw-r--r--erts/doc/src/persistent_term.xml2
1 files changed, 1 insertions, 1 deletions
diff --git a/erts/doc/src/persistent_term.xml b/erts/doc/src/persistent_term.xml
index d2a138d65f..29a6c67051 100644
--- a/erts/doc/src/persistent_term.xml
+++ b/erts/doc/src/persistent_term.xml
@@ -71,7 +71,7 @@
scan of their heaps for the term that has been deleted. While
such scan is relatively light-weight, if there are many
processes, the system can become less responsive until all
- process have scanned theirs heaps.</p></item>
+ process have scanned their heaps.</p></item>
<item><p>If the deleted term (or any part of it) is still used
by a process, that process will do a major (fullsweep) garbage