File 0171-Fix-typos-for-doc-in-erts.patch of Package erlang
From 0fab29c1fedd09d5a4a9fb94245aa650021589c4 Mon Sep 17 00:00:00 2001
From: "Kian-Meng, Ang" <kianmeng@cpan.org>
Date: Tue, 9 Nov 2021 09:33:20 +0800
Subject: [PATCH 1/2] Fix typos for doc in erts
---
erts/doc/src/alt_dist.xml | 4 +-
erts/doc/src/erl_cmd.xml | 2 +-
erts/doc/src/erl_dist_protocol.xml | 2 +-
erts/doc/src/erl_nif.xml | 2 +-
erts/doc/src/erlang.xml | 38 +++++++--------
erts/doc/src/erlc_cmd.xml | 2 +-
erts/doc/src/erts_alloc.xml | 2 +-
erts/doc/src/notes.xml | 74 +++++++++++++++---------------
8 files changed, 63 insertions(+), 63 deletions(-)
diff --git a/erts/doc/src/alt_dist.xml b/erts/doc/src/alt_dist.xml
index d8d8765b91..a75368c179 100644
--- a/erts/doc/src/alt_dist.xml
+++ b/erts/doc/src/alt_dist.xml
@@ -1025,7 +1025,7 @@
header of four bytes containing the length of the package in a
big-endian 32-bit integer. As Unix domain sockets only can be used
between processes on the same machine, we do not need to
- code the integer in some special endianess, but we will do it anyway
+ code the integer in some special endianness, but we will do it anyway
because in most situation you need to do it. Unix domain
sockets are reliable and order maintaining, so we do not need to
implement resends and such in the driver.</p>
@@ -1410,7 +1410,7 @@
<section>
<title>Selected Parts of the Distribution Driver Implementation</title>
- <p>The implemenation of the distribution driver is not completely
+ <p>The implementation of the distribution driver is not completely
covered here, details about buffering and other things
unrelated to driver writing are not explained. Likewise are
some peculiarities of the UDS protocol not explained in
diff --git a/erts/doc/src/erl_cmd.xml b/erts/doc/src/erl_cmd.xml
index 7ef3ca88f9..af501fbfd9 100644
--- a/erts/doc/src/erl_cmd.xml
+++ b/erts/doc/src/erl_cmd.xml
@@ -1781,7 +1781,7 @@ $ <input>erl \
</item>
<tag><c><![CDATA[ERL_CRASH_DUMP_SECONDS=-1]]></c></tag>
<item>A negative value causes the termination of the runtime system
- to wait indefinitely until the crash dump file has been completly
+ to wait indefinitely until the crash dump file has been completely
written. This is the default if option <c>-heart</c> is <em>not</em>
passed to <c>erl</c> and <c>ERL_CRASH_DUMP_SECONDS</c> is not set.
</item>
diff --git a/erts/doc/src/erl_dist_protocol.xml b/erts/doc/src/erl_dist_protocol.xml
index 29027f0eeb..29d733840e 100644
--- a/erts/doc/src/erl_dist_protocol.xml
+++ b/erts/doc/src/erl_dist_protocol.xml
@@ -737,7 +737,7 @@ io:format("old/unused name ~ts at port ~p, fd = ~p ~n",
</item>
<tag><c>named:</c></tag>
<item><p>
- The handshake willl continue, but <c>A</c> requested a dynamic
+ The handshake will continue, but <c>A</c> requested a dynamic
node name by setting flag <seeguide marker="#DFLAG_NAME_ME">
<c>DFLAG_NAME_ME</c></seeguide>. The dynamic node name of
<c>A</c> is supplied at the end of the status message from
diff --git a/erts/doc/src/erl_nif.xml b/erts/doc/src/erl_nif.xml
index 954a8a802f..a8c21f8155 100644
--- a/erts/doc/src/erl_nif.xml
+++ b/erts/doc/src/erl_nif.xml
@@ -3242,7 +3242,7 @@ enif_map_iterator_destroy(env, &iter);</code>
<c>ERL_NIF_SELECT_READ</c> and/or <c>ERL_NIF_SELECT_WRITE</c> to
indicate which type of event to cancel. Arguments <c>pid</c> and
<c>ref</c> are ignored when <c>ERL_NIF_SELECT_CANCEL</c> is specified.
- The return value will tell if the event was actualy cancelled or if a
+ The return value will tell if the event was actually cancelled or if a
notification may already have been sent.</p>
<p>Use <c>ERL_NIF_SELECT_STOP</c> as <c>mode</c> in order to safely
close an event object that has been passed to <c>enif_select</c>. The
diff --git a/erts/doc/src/erlang.xml b/erts/doc/src/erlang.xml
index 6db112a55e..b0d393350c 100644
--- a/erts/doc/src/erlang.xml
+++ b/erts/doc/src/erlang.xml
@@ -510,14 +510,14 @@
<datatype>
<name name="dist_handle" prefix="true"/>
<desc>
- <p>An opaque handle identifing a distribution channel.</p>
+ <p>An opaque handle identifying a distribution channel.</p>
</desc>
</datatype>
<datatype>
<name name="nif_resource" prefix="true"/>
<desc>
- <p>An opaque handle identifing a
+ <p>An opaque handle identifying a
<seecref marker="erl_nif#resource_objects">NIF resource object
</seecref>.</p>
</desc>
@@ -1514,7 +1514,7 @@ end</code>
<p>
This function is used when implementing an alternative
distribution carrier using processes as distribution
- controllers. <c><anno>DHandle</anno></c> is retrived
+ controllers. <c><anno>DHandle</anno></c> is retrieved
via the callback
<seeguide marker="erts:alt_dist#hs_data_f_handshake_complete"><c>f_handshake_complete</c></seeguide>.
More information can be found in the documentation of
@@ -1543,7 +1543,7 @@ end</code>
<p>
This function is used when implementing an alternative
distribution carrier using processes as distribution
- controllers. <c><anno>DHandle</anno></c> is retrived
+ controllers. <c><anno>DHandle</anno></c> is retrieved
via the callback
<seeguide marker="erts:alt_dist#hs_data_f_handshake_complete"><c>f_handshake_complete</c></seeguide>.
More information can be found in the documentation of
@@ -1579,7 +1579,7 @@ end</code>
<p>
This function is used when implementing an alternative
distribution carrier using processes as distribution
- controllers. <c><anno>DHandle</anno></c> is retrived
+ controllers. <c><anno>DHandle</anno></c> is retrieved
via the callback
<seeguide marker="erts:alt_dist#hs_data_f_handshake_complete"><c>f_handshake_complete</c></seeguide>.
More information can be found in the documentation of
@@ -1600,7 +1600,7 @@ end</code>
Once this function has been called, <c><anno>InputHandler</anno></c>
is the only process allowed to call
<seemfa marker="erlang#dist_ctrl_put_data/2"><c>erlang:dist_ctrl_put_data(DHandle, Data)</c></seemfa>
- with the <c><anno>DHandle</anno></c> identifing this distribution
+ with the <c><anno>DHandle</anno></c> identifying this distribution
channel.
</p>
<note><p>
@@ -1612,7 +1612,7 @@ end</code>
<p>
This function is used when implementing an alternative
distribution carrier using processes as distribution
- controllers. <c><anno>DHandle</anno></c> is retrived
+ controllers. <c><anno>DHandle</anno></c> is retrieved
via the callback
<seeguide marker="erts:alt_dist#hs_data_f_handshake_complete"><c>f_handshake_complete</c></seeguide>.
More information can be found in the documentation of
@@ -1645,7 +1645,7 @@ end</code>
<p>
This function is used when implementing an alternative
distribution carrier using processes as distribution
- controllers. <c><anno>DHandle</anno></c> is retrived
+ controllers. <c><anno>DHandle</anno></c> is retrieved
via the callback
<seeguide marker="erts:alt_dist#hs_data_f_handshake_complete"><c>f_handshake_complete</c></seeguide>.
More information can be found in the documentation of
@@ -1694,7 +1694,7 @@ end</code>
<p>
This function is used when implementing an alternative
distribution carrier using processes as distribution
- controllers. <c><anno>DHandle</anno></c> is retrived
+ controllers. <c><anno>DHandle</anno></c> is retrieved
via the callback
<seeguide marker="erts:alt_dist#hs_data_f_handshake_complete"><c>f_handshake_complete</c></seeguide>.
More information can be found in the documentation of
@@ -2357,7 +2357,7 @@ account.</p>
{#Fun<test.2.107738983>,#Fun<test.3.107738983>}
</pre>
<p>Explanation: The string representations differ because the funs
-come from different fun experssions.</p>
+come from different fun expressions.</p>
<pre>
> <input>{fun() -> 1 end, fun() -> 1 end}.</input> > <input></input>
{#Fun<erl_eval.45.97283095>,#Fun<erl_eval.45.97283095>}
@@ -2592,7 +2592,7 @@ uncompiled code with the same arity are mapped to the same list by
applications with a supervision tree, because OTP
assumes the group leader of their processes is
their application master.</p>
- <p>Setting the group leader follows the signal ordering guarentees
+ <p>Setting the group leader follows the signal ordering guarantees
described in the
<seeguide marker="system/reference_manual:processes#signals">
Processes Chapter</seeguide> in the <i>Erlang Reference Manual</i>.</p>
@@ -3081,7 +3081,7 @@ is_process_alive(P2Pid),
<p>See the documentation about
<seeguide marker="system/reference_manual:processes#signals">signals</seeguide>
and <seemfa marker="#exit/2">erlang:exit/2</seemfa> for more
- information about signals and exit singnals.</p>
+ information about signals and exit signals.</p>
</desc>
</func>
@@ -3667,7 +3667,7 @@ is_process_alive(P2Pid),
<func>
<name name="make_tuple" arity="3" since=""/>
- <fsummary>Create a new tuple with specifed arity and contents.</fsummary>
+ <fsummary>Create a new tuple with specified arity and contents.</fsummary>
<desc>
<p>Creates a tuple of size <c><anno>Arity</anno></c>, where each element
has value <c><anno>DefaultValue</anno></c>, and then fills in
@@ -4641,7 +4641,7 @@ receive_replies(ReqId, N, Acc) ->
new Erlang port. A port can be seen as an external Erlang
process.</p>
<p>The name of the executable as well as the arguments
- specifed in <c>cd</c>, <c>env</c>, <c>args</c>, and <c>arg0</c> are
+ specified in <c>cd</c>, <c>env</c>, <c>args</c>, and <c>arg0</c> are
subject to Unicode filename translation if the system is running
in Unicode filename mode. To avoid
translation or to force, for example UTF-8, supply the executable
@@ -6151,7 +6151,7 @@ receive_replies(ReqId, N, Acc) ->
<c><anno>Item</anno></c>s were included
in <c><anno>ItemList</anno></c>. Valid <c><anno>Item</anno></c>s can
be included multiple times in <c><anno>ItemList</anno></c>.</p>
- <p>Getting process informations follows the signal ordering guarantees
+ <p>Getting process information follows the signal ordering guarantees
described in the
<seeguide marker="system/reference_manual:processes#signals">
Processes Chapter</seeguide> in the <i>Erlang Reference Manual</i>.</p>
@@ -8310,7 +8310,7 @@ lists:map(
and <seeerl marker="#system_info_dirty_cpu_schedulers">dirty CPU</seeerl>
schedulers in the system have been busy. This value is normally a
better indicator of how much load an Erlang node is under instead of
- looking at the CPU utilization privided by tools such as <c>top</c> or
+ looking at the CPU utilization provided by tools such as <c>top</c> or
<c>sysstat</c>. This is because <c>scheduler_wall_time</c> also includes
time where the scheduler is waiting for some other reasource (such as an internal
mutex) to be available but does not use the CPU. In order to better
@@ -8615,7 +8615,7 @@ ok
</item>
</taglist>
<p>
- Appart from the reply message, the <c>{asynchronous,
+ Apart from the reply message, the <c>{asynchronous,
ReplyTag}</c> option behaves exactly the same as the
<c>asynchronous</c> option without reply tag.
</p>
@@ -9928,7 +9928,7 @@ Metadata = #{ pid => pid(),
introduced in the future:</p>
<taglist>
<tag><c>{function, Function}</c></tag>
- <item><p><c>Function</c> is the name of the funcion used.</p>
+ <item><p><c>Function</c> is the name of the function used.</p>
</item>
<tag><c>{clock_id, ClockId}</c></tag>
<item><p>Exists only if <c>Function</c>
@@ -12094,7 +12094,7 @@ improper_end</pre>
<item>
<p>Returns a list of atoms indicating what kind of traces is
enabled for the process. The list is empty if no
- traces are enabled, and one or more of the followings
+ traces are enabled, and one or more of the following
atoms if traces are enabled: <c>send</c>,
<c>'receive'</c>, <c>set_on_spawn</c>, <c>call</c>,
<c>return_to</c>, <c>procs</c>, <c>ports</c>,
diff --git a/erts/doc/src/erlc_cmd.xml b/erts/doc/src/erlc_cmd.xml
index 98042d49b7..26a0bc810c 100644
--- a/erts/doc/src/erlc_cmd.xml
+++ b/erts/doc/src/erlc_cmd.xml
@@ -326,7 +326,7 @@ erlc +export_all file.erl</pre>
<p>Using the compile server does not always speed up the build, as
the compile server sometimes must be restarted to ensure correctness.
- Here are some examples of situtations that force a restart:</p>
+ Here are some examples of situations that force a restart:</p>
<list type="bulleted">
<item><c>erlc</c> wants to use a different version of Erlang
diff --git a/erts/doc/src/erts_alloc.xml b/erts/doc/src/erts_alloc.xml
index cd98123c5c..2f2c409616 100644
--- a/erts/doc/src/erts_alloc.xml
+++ b/erts/doc/src/erts_alloc.xml
@@ -638,7 +638,7 @@
good fit strategy is selected for allocator
<c><![CDATA[<S>]]></c>. When the good fit strategy is used, free
blocks are placed in segregated free-lists. Each free-list
- contains blocks of sizes in a specific range. The maxiumum block
+ contains blocks of sizes in a specific range. The maximum block
search depth sets a limit on the maximum number of blocks to
inspect in a free-list during a search for suitable block
satisfying the request.</p>
diff --git a/erts/doc/src/notes.xml b/erts/doc/src/notes.xml
index f15da6c383..2e1d1054a0 100644
--- a/erts/doc/src/notes.xml
+++ b/erts/doc/src/notes.xml
@@ -167,7 +167,7 @@
simultaneously received signals to that port could cause
a runtime system crash. The effected signals are
<c>link</c>, <c>monitor</c> and <c>demonitor</c>. On OTP
- 22 a similiar race could also cause a memory leak when
+ 22 a similar race could also cause a memory leak when
receiving an <c>unlink</c> signal.</p>
<p>
Own Id: OTP-17642 Aux Id: PR-5248 </p>
@@ -874,7 +874,7 @@
order to prevent late responses. The <c>gen_statem</c>
behavior still use a proxy process in the distributed
case, since it has always prevented late replies and
- aliases wont work against pre OTP 24 nodes. The proxy
+ aliases won't work against pre OTP 24 nodes. The proxy
process can be removed in OTP 26.</p>
<p>
The alias feature also made it possible to introduce new
@@ -2436,7 +2436,7 @@
<item>
<p>Internally in BEAM, handling of continuation pointers
has been simplified. This change is not user-visible,
- except when examing a process stack in the crashdump
+ except when examining a process stack in the crashdump
viewer. The continuation pointer for a function will now
be stored below the y(0) for that function.</p>
<p>
@@ -7238,7 +7238,7 @@
<c>cpu_timestamp</c> in <seemfa
marker="erlang#trace/3">erlang:trace/3</seemfa> to use
it instead of per process CPU time. This makes this
- option useable on such OSs when running multiple
+ option usable on such OSs when running multiple
schedulers.</p>
<p>
Own Id: OTP-15090</p>
@@ -7282,7 +7282,7 @@
</item>
<item>
<p>
- Fix segfault when a process is interally re-scheduled
+ Fix segfault when a process is internally re-scheduled
while being traced for in out events. This bug was
introduced in erts-8.0 (OTP-19.0).</p>
<p>
@@ -7833,7 +7833,7 @@
request signal to the other process and waits for the
result instead of locking the other process and reading
the result directly. In some special cases where no
- conflicts occur, signal order wont be violated, and the
+ conflicts occur, signal order won't be violated, and the
amount of data requested is guaranteed to be small, the
inspected process may be inspected directly.</p>
<p>
@@ -10050,7 +10050,7 @@
<item>
<p>
Add option to make SIGTERM trigger the OS default
- behaviour instead of doing a gracefull shutdown. To
+ behaviour instead of doing a graceful shutdown. To
activate this bahviour the environment variable
ERL_ZZ_SIGTERM_KILL should be set to "true". This option
only works in OTP 19 as OTP 20 will have a different way
@@ -10379,9 +10379,9 @@
<p>
Fix a quite rare bug causing VM crash during code loading
and the use of export funs (fun M:F/A) of not yet loaded
- modules. Requires a very specfic timing of concurrent
+ modules. Requires a very specific timing of concurrent
scheduler threads. Has been seen on ARM but can probably
- also occure on other architectures. Bug has existed since
+ also occurred on other architectures. Bug has existed since
OTP R16.</p>
<p>
Own Id: OTP-14144 Aux Id: seq13242 </p>
@@ -10685,7 +10685,7 @@
</item>
<item>
<p>
- Update build scripts to not make assumtions about where
+ Update build scripts to not make assumptions about where
env, cp and perl are located.</p>
<p>
Own Id: OTP-13800</p>
@@ -12560,7 +12560,7 @@
<p>
Fix global call trace when hipe compiled code call beam
compiled functions. Tracing of beam functions should now
- alway work regardless who the caller is.</p>
+ always work regardless who the caller is.</p>
<p>
Own Id: OTP-11939</p>
</item>
@@ -12936,7 +12936,7 @@
<p>
Development of perfctr in the linux kernel ceased in
2010. The perfctr support code in the Erlang VM is thus
- effectively dead code and therefor removed.</p>
+ effectively dead code and therefore removed.</p>
<p>
Own Id: OTP-12508</p>
</item>
@@ -13581,7 +13581,7 @@
<item>
<p>
Fix two cases of unreachable code caused by false use of
- assigment operators.</p>
+ assignment operators.</p>
<p>
Own Id: OTP-12222</p>
</item>
@@ -14635,11 +14635,11 @@
Characteristics impact: A call to the
<c>garbage_collect/1</c> BIF or the
<c>check_process_code/2</c> BIF will normally take longer
- time to complete while the system as a whole wont be as
+ time to complete while the system as a whole won't be as
much negatively effected by the operation as before. A
call to <c>code:purge/1</c> and <c>code:soft_purge/1</c>
may complete faster or slower depending on the state of
- the system while the system as a whole wont be as much
+ the system while the system as a whole won't be as much
negatively effected by the operation as before.</p>
<p>
Own Id: OTP-11388 Aux Id: OTP-11535, OTP-11648 </p>
@@ -15633,7 +15633,7 @@
system:</p> <list> <item>Reduced memory footprint when
the memory load is unevenly distributed between scheduler
specific allocator instances.</item> <item>Depending on
- the default allocaton strategy used on a specific
+ the default allocation strategy used on a specific
allocator there might or might not be a slight
performance loss.</item> <item>When enabled on the
<c>fix_alloc</c> allocator, a different strategy for
@@ -15915,7 +15915,7 @@
<item>Memory leak when terminating ports</item>
<item>Memory leak when reaching the system limit of
maximum amount of concurrently existing ports</item>
- <item>Crashs due to missing, or late test of bad port
+ <item>Crashes due to missing, or late test of bad port
handle</item> <item>The newly introduced driver API
function <c>erl_drv_busy_msgq_limits()</c> could not be
used by dynamically linked in drivers on Windows</item>
@@ -15926,7 +15926,7 @@
<item>
<p>
Fix <c>{packet,httph}</c> header capitalization for
- unrecognized header fields longer than 20 charachters
+ unrecognized header fields longer than 20 characters
such as <c>Sec-Websocket-Version</c>. The limit is simply
raised from 20 to 50 characters with the hope that valid
headers longer than 50 are not used.</p>
@@ -16124,7 +16124,7 @@
For instance, prefer sbc segments over mbc segments,
caching policy is time-arrow aware, evicting older cached
segments to store newer segments. </p> <p>The default
- number of cachable segment has been increased from five
+ number of cacheable segment has been increased from five
to ten segments. This can be modified, same as before,
with the command line option <c>+MMmcs 5</c></p>
<p>Impact: Increased speed for processing on larger
@@ -16200,7 +16200,7 @@
<p>
The effect of the deprecated environment variable
ERL_MAX_PORTS had been removed premeturely. It has now
- been readded. Note that this is still scheduled to be
+ been read. Note that this is still scheduled to be
released in R17B.</p>
<p>
Own Id: OTP-10895</p>
@@ -16428,7 +16428,7 @@
port lock as well as truly asynchronous communication
with ports.</item> <item>Optimized lookup of port handles
from drivers.</item> <item>Optimized driver lookup when
- creating ports.</item> <item>Preemptable <seemfa
+ creating ports.</item> <item>Preemptible <seemfa
marker="erts:erlang#ports/0">erlang:ports/0</seemfa>
BIF.</item> <item>Improving responsiveness by bumping
reductions for a process calling a driver callback
@@ -16990,7 +16990,7 @@
</item>
<item>
<p>
- Correct formating in exit error messages</p>
+ Correct formatting in exit error messages</p>
<p>
Ensure displayed sizes are not negative. (Thanks to
Michael Santos)</p>
@@ -17347,7 +17347,7 @@
<section><title>Fixed Bugs and Malfunctions</title>
<list>
<item>
- <p><c>erlang:system_profile</c> errorneous profiled the
+ <p><c>erlang:system_profile</c> erroneous profiled the
profiler process when observing runnable processes. This
has been corrected. </p>
<p>
@@ -17428,7 +17428,7 @@
and async threads operations when you exit the emulator,
you use erlang:halt/2 with an integer first argument and
an option list containing {flush,false} as the second
- argument. Note that now is flushing not dependant of the
+ argument. Note that now is flushing not dependent of the
exit code, and you cannot only flush async threads
operations which we deemed as a strange behaviour anyway.
</p>
@@ -19739,7 +19739,7 @@
<p>
<c>epmd</c> used to generate a message to the syslog when
it started up, which could be annoying. This has been
- changed to only generate the message if the debug swith
+ changed to only generate the message if the debug switch
is given. (Thanks to Michael Santos.)</p>
<p>
Own Id: OTP-8775</p>
@@ -19915,7 +19915,7 @@
<item>
<p>
Extreme combinations of register/unregister in a highly
- parallell SMP application could crash the VM. The error
+ parallel SMP application could crash the VM. The error
is corrected.</p>
<p>
Own Id: OTP-8663</p>
@@ -20159,7 +20159,7 @@
<item>
<p>
Support for using gcc's built-in functions for atomic
- memory access has been added. This functionallity will be
+ memory access has been added. This functionality will be
used if available and no other native atomic
implementation in ERTS is available.</p>
<p>
@@ -20640,7 +20640,7 @@
GC. See the documentation for <c>spawn_opt/2-5</c>,
<c>erlang:system_info/1</c>, <c>erlang:system_flag/2</c>,
<c>process_flag/2-3</c>, <c>erlang:trace/3</c>, and the
- documenation for <c>erl</c> for the new command line
+ documentation for <c>erl</c> for the new command line
options <c>+hms</c> and <c>+hmbs</c>.</p>
<p>
Own Id: OTP-8370</p>
@@ -20670,7 +20670,7 @@
app-vsn/ebin/mod.beam file, the file info for the app-vsn
and app-vsn/ebin directories are faked using the file
info from the archive file as origin. The virtual
- direcories can also be listed. For short, the top
+ directories can also be listed. For short, the top
directories are virtual if they does not exist.</p>
<p>
Own Id: OTP-8387</p>
@@ -21093,7 +21093,7 @@
</item>
<item>
<p>
- The pthread rwlock implemention on Linux could cause
+ The pthread rwlock implementation on Linux could cause
starvation of writers. We, therefore, now use our own
rwlock implementation on Linux.</p>
<p>
@@ -22179,7 +22179,7 @@
</item>
<item>
<p>
- Floating point arithmetics in drivers could cause a
+ Floating point arithmetic in drivers could cause a
runtime system crash and/or unexpected results on runtime
systems with floating point exceptions enabled. Floating
point exceptions are disabled unless explicitly enabled
@@ -22191,7 +22191,7 @@
<p>
A bug when many sockets got signalled simultaneously
causing the emulator to panic with the message
- "Inconsistent, why isnt io reported?" is now corrected.</p>
+ "Inconsistent, why isn't io reported?" is now corrected.</p>
<p>
Own Id: OTP-7420</p>
</item>
@@ -22649,7 +22649,7 @@
<list>
<item>
<p>
- Floating point arithmetics in drivers can cause a runtime
+ Floating point arithmetic in drivers can cause a runtime
system crash and/or unexpected results on runtime systems
with floating point exceptions enabled. Floating point
exceptions are disabled unless explicitly enabled or if
@@ -22975,7 +22975,7 @@
<list>
<item>
<p>
- Floating point arithmetics in drivers can cause a runtime
+ Floating point arithmetic in drivers can cause a runtime
system crash on runtime systems with floating point
exceptions enabled. Floating point exceptions are
disabled unless explicitly enabled or if hipe is enabled.</p>
@@ -24027,7 +24027,7 @@
<p>Attempting to construct a binary longer than 536870911
bytes will now fail with a <c><![CDATA[system_limit]]></c> exception
(rather than fail in mysterious ways or construct an
- binary with incorrect contents). Similarily, attempting
+ binary with incorrect contents). Similarly, attempting
to match a binary longer than 536870911 bytes will now
fail (instead of producing an incorrect result). This
limitation has been documented in the Efficiency Guide.
--
2.31.1
