File 0288-Fix-typos-in-erl_nif.xml.patch of Package erlang

Overview Repositories Revisions Requests Users Attributes Meta

File 0288-Fix-typos-in-erl_nif.xml.patch of Package erlang

From 713e6726102f8d262c538431cdf1ff01177a6d45 Mon Sep 17 00:00:00 2001
From: Magnus Henoch <magnus@erlang-solutions.com>
Date: Tue, 13 Mar 2018 14:17:42 +0000
Subject: [PATCH] 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 <seealso marker="erlang#system_flag_multi_scheduling">
 <c>erlang:system_flag(multi_scheduling, block)</c></seealso>, 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
@@ -3086,7 +3086,7 @@ if (retval &amp; ERL_NIF_SELECT_STOP_CALLED) {
 <c>enif_free_env</c></seealso> of cleared for reuse with
 <seealso marker="#enif_clear_env"><c>enif_clear_env</c></seealso>.
 If <c>msg_env</c> is set to <c>NULL</c>, the <c>msg</c> 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
-- 
2.16.3

Places

File 0288-Fix-typos-in-erl_nif.xml.patch of Package erlang

Places