From 713e6726102f8d262c538431cdf1ff01177a6d45 Mon Sep 17 00:00:00 2001
From: Magnus Henoch
Date: Tue, 13 Mar 2018 14:17:42 +0000
Subject: Fix typos in erl_nif.xml
---
erts/doc/src/erl_nif.xml | 16 ++++++++--------
1 file changed, 8 insertions(+), 8 deletions(-)
diff --git a/erts/doc/src/erl_nif.xml b/erts/doc/src/erl_nif.xml
index b9c2e70b57..705ce46b75 100644
--- a/erts/doc/src/erl_nif.xml
+++ b/erts/doc/src/erl_nif.xml
@@ -538,7 +538,7 @@ int writeiovec(ErlNifEnv *env, ERL_NIF_TERM term, ERL_NIF_TERM *tail,
have to wait for a very long time. Blocking multi-scheduling, that
is, calling
erlang:system_flag(multi_scheduling, block), can
- also take a very long time to complete. This becaue all ongoing
+ also take a very long time to complete. This is because all ongoing
dirty operations on all dirty schedulers must complete before
the block operation can complete.
Many operations communicating with a process executing a
@@ -588,7 +588,7 @@ int writeiovec(ErlNifEnv *env, ERL_NIF_TERM term, ERL_NIF_TERM *tail,
unload is called to release the library. All are
described individually below.
The fourth argument NULL is ignored. It
- was earlier used for the deprectated reload callback
+ was earlier used for the deprecated reload callback
which is no longer supported since OTP 20.
If compiling a NIF for static inclusion through
--enable-static-nifs, you must define STATIC_ERLANG_NIF
@@ -2216,7 +2216,7 @@ enif_inspect_iovec(env, max_elements, term, &tail, &iovec);
enif_get_resource.
-
-
A resoure term can be serialized with term_to_binary and later
+
A resource term can be serialized with term_to_binary and later
be fully recreated if the resource object is still alive when
binary_to_term is called. A stale resource term will be
returned from binary_to_term if the resource object has
@@ -2960,7 +2960,7 @@ enif_map_iterator_destroy(env, &iter);
Argument mode describes the type of events to wait for. It can be
ERL_NIF_SELECT_READ, ERL_NIF_SELECT_WRITE or a bitwise
OR combination to wait for both. It can also be ERL_NIF_SELECT_STOP
- which is described further below. When a read or write event is triggerred,
+ which is described further below. When a read or write event is triggered,
a notification message like this is sent to the process identified by
pid:
{select, Obj, Ref, ready_input | ready_output}
@@ -3011,7 +3011,7 @@ enif_map_iterator_destroy(env, &iter);
- The stop callback was scheduled to run on some other thread
or later by this thread.
- Returns a negative value if the call failed where the follwing bits can be set:
+ Returns a negative value if the call failed where the following bits can be set:
ERL_NIF_SELECT_INVALID_EVENT
- Argument event is not a valid OS event object.
@@ -3019,9 +3019,9 @@ enif_map_iterator_destroy(env, &iter);
- The system call failed to add the event object to the poll set.
- Use bitwise AND to test for specific bits in the return vaue.
+
Use bitwise AND to test for specific bits in the return value.
New significant bits may be added in future releases to give more detailed
- information for both failed and successful calls. Do NOT use equallity tests
+ information for both failed and successful calls. Do NOT use equality tests
like ==, as that may cause your application to stop working.
Example:
@@ -3086,7 +3086,7 @@ if (retval & ERL_NIF_SELECT_STOP_CALLED) {
enif_free_env of cleared for reuse with
enif_clear_env.
If msg_env is set to NULL, the msg term is
- copied and the original term and its environemt is still valid after
+ copied and the original term and its environment is still valid after
the call.
This function is only thread-safe when the emulator with SMP support
is used. It can only be used in a non-SMP emulator from a NIF-calling
--
cgit v1.2.3