File 2573-Fix-various-small-typos-in-the-OTP-Design-Principles.patch of Package erlang

From f5cf1840e6b491512d545037cc2cf4189ec79907 Mon Sep 17 00:00:00 2001
From: Lars Eric Olsson <lars@eric-olsson.com>
Date: Fri, 15 May 2020 13:57:02 +0200
Subject: [PATCH] Fix various small typos in the OTP Design Principles

---
 system/doc/design_principles/applications.xml |  8 +++----
 system/doc/design_principles/des_princ.xml    |  7 +++---
 system/doc/design_principles/events.xml       |  7 +++---
 .../design_principles/release_handling.xml    | 13 +++++-----
 .../design_principles/release_structure.xml   |  9 ++++---
 system/doc/design_principles/statem.xml       | 24 +++++++++----------
 system/doc/design_principles/sup_princ.xml    |  7 +++---
 7 files changed, 35 insertions(+), 40 deletions(-)

diff --git a/system/doc/design_principles/statem.xml b/system/doc/design_principles/statem.xml
index 8158416fb1..2d6ea27635 100644
--- a/system/doc/design_principles/statem.xml
+++ b/system/doc/design_principles/statem.xml
@@ -164,7 +164,7 @@ State(S) x Event(E) -> Actions(A), State(S')</pre>
     </p>
     <p>
       The behaviour engine holds the state machine state,
-      server data, timer references, a queue of posponed messages
+      server data, timer references, a queue of postponed messages
       and other metadata.  It receives all process messages,
       handles the system messages, and calls the callback module
       with machine specific events.
@@ -574,7 +574,7 @@ State(S) x Event(E) -> Actions(A), State(S')</pre>
 	</seealso>
       </tag>
       <item>
-	Generate the next event to handle, see section 
+	Generate the next event to handle, see section
 	<seealso marker="#Inserted Events">Inserted Events</seealso>
       </item>
     </taglist>
@@ -740,7 +740,7 @@ StateName(EventType, EventContent, Data) ->
     </p>
     <p>
       You may repeat the state enter call using the <c>{repeat_state,...}</c>
-      return value from the 
+      return value from the
       <seealso marker="#Event Handler">Event Handler</seealso>.
       In this case <c>OldState</c> will also be equal to the current state.
     </p>
@@ -1465,10 +1465,10 @@ open(cast, {button,_}, Data) ->
       Note that no time-out message will arrive after this (because the timer has been explicitly canceled),
       unless you have already postponed one earlier (see the next section),
       so ensure that you do not accidentally postpone such messages.
-      Also note that a time-out message may arrive during a **state callback** 
+      Also note that a time-out message may arrive during a <em>state callback</em>
       that is cancelling the timer, so you may have to read out
       such a message from the process mailbox, depending on
-      the return value from 
+      the return value from
       <seealso marker="erts:erlang#cancel_timer/2"><c>erlang:cancel_timer(Tref)</c></seealso>.
     </p>
     <p>
-- 
2.26.2