File 0886-Change-effecting-into-affecting.patch of Package erlang

Overview Repositories Revisions Requests Users Attributes Meta

File 0886-Change-effecting-into-affecting.patch of Package erlang (Revision 892e7dc5e084bd8d8059892726ddebb4)

Currently displaying revision 892e7dc5e084bd8d8059892726ddebb4 , Show latest

From a3a6920dd1b2b7d1edf4888e6e4c1aa3862cc3cc Mon Sep 17 00:00:00 2001
From: Gustaw Lippa <34194983+gustawlippa@users.noreply.github.com>
Date: Wed, 8 Nov 2023 10:45:19 +0100
Subject: [PATCH] Change "effecting" into "affecting"

---
 system/doc/reference_manual/processes.xml | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/system/doc/reference_manual/processes.xml b/system/doc/reference_manual/processes.xml
index 4f1228e210..98b83eb47a 100644
--- a/system/doc/reference_manual/processes.xml
+++ b/system/doc/reference_manual/processes.xml
@@ -582,11 +582,11 @@ spawn(Module, Name, Args) -> pid()
 	  still executing dirty native code. <i>Directly visible Erlang
 	  resources</i> will be released, but the runtime system cannot
 	  force the native code to stop executing. The runtime system tries
-	  to prevent the execution of the dirty native code from effecting
+	  to prevent the execution of the dirty native code from affecting
 	  other processes by, for example, disabling functionality such as
 	  <seecref marker="erts:erl_nif#enif_send"><c>enif_send()</c></seecref>
 	  when used from a terminated process, but if the NIF is not well
-	  behaved it can still effect other processes. A well behaved dirty
+	  behaved it can still affect other processes. A well behaved dirty
 	  NIF should test if
 	  <seecref marker="erts:erl_nif#enif_is_current_process_alive">the
 	  process it is executing in has exited</seecref>, and if so stop
-- 
2.35.3

Places

File 0886-Change-effecting-into-affecting.patch of Package erlang (Revision 892e7dc5e084bd8d8059892726ddebb4)

Places