aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorPatrik Nyblom <[email protected]>2013-05-06 14:53:07 +0200
committerPatrik Nyblom <[email protected]>2013-05-06 14:53:07 +0200
commiteb4d4c133a8c2ad00807888289cb99d67f70896f (patch)
treec7870453c2d40f4ddb6fbc5f00d8f1f42bcad20d
parent0c1ceeb0a30609a105dd69e000d1c391e2d2927e (diff)
downloadotp-eb4d4c133a8c2ad00807888289cb99d67f70896f.tar.gz
otp-eb4d4c133a8c2ad00807888289cb99d67f70896f.tar.bz2
otp-eb4d4c133a8c2ad00807888289cb99d67f70896f.zip
Minor spelling correction
-rw-r--r--erts/doc/src/erlang.xml4
1 files changed, 2 insertions, 2 deletions
diff --git a/erts/doc/src/erlang.xml b/erts/doc/src/erlang.xml
index 20fc9e70f2..767edc1cc0 100644
--- a/erts/doc/src/erlang.xml
+++ b/erts/doc/src/erlang.xml
@@ -6086,12 +6086,12 @@ ok
uninterrupted execution time of the process or port,
which will always be <c>&gt;=</c> the <c>Time</c> value
supplied when starting the trace. New tuples may be
- added to the <c>Info</c> lists in the future, and the
+ added to the <c>Info</c> list in the future, and the
order of the tuples in the list may be changed at any
time without prior notice.
</p>
<p>This can be used to detect problems with NIF's or
- drivers that takes too long to execute. Generally, 1 ms
+ drivers that take too long to execute. Generally, 1 ms
is considered a good maximum time for a driver callback
or a NIF. However, a time sharing system should usually
consider everything below 100 ms as "possible" and