File 0793-Grammatical-spelling-fixups-for-the-efficiency-guide.patch of Package erlang

From 98ec607e887181e0ed57b85921a2d10f3ffb7a69 Mon Sep 17 00:00:00 2001
From: Bryan Paxton <bryan@starbelly.io>
Date: Sat, 19 Jun 2021 14:03:39 -0500
Subject: [PATCH 2/2] Grammatical / spelling fixups for the efficiency guide
 profiling section

---
 system/doc/efficiency_guide/profiling.xml | 16 ++++++++--------
 1 file changed, 8 insertions(+), 8 deletions(-)

diff --git a/system/doc/efficiency_guide/profiling.xml b/system/doc/efficiency_guide/profiling.xml
index 594d066df4..847949cd2a 100644
--- a/system/doc/efficiency_guide/profiling.xml
+++ b/system/doc/efficiency_guide/profiling.xml
@@ -47,7 +47,7 @@
 
       <item><p><c>eprof</c> provides time information of each function
       used in the program. No call graph is produced, but <c>eprof</c> has
-      considerable less impact on the program it profiles.</p>
+      considerably less impact on the program it profiles.</p>
       <p>If the program is too large to be profiled by <c>fprof</c> or
       <c>eprof</c>, the <c>cover</c> and <c>cprof</c> tools can be used
       to locate code parts that are to be more thoroughly profiled using
@@ -78,7 +78,7 @@
 
     <p>For a large system, you do not want to run the profiling
       tools on the whole system. Instead you want to concentrate on
-      central processes and modules, which contribute for a big part
+      central processes and modules, which account for a big part
       of the execution.</p>
   </section>
 
@@ -136,7 +136,7 @@
       <p><c>eprof</c> is based on the Erlang <c>trace_info</c> BIFs.
       <c>eprof</c> shows how much time has been used by each process,
       and in which function calls this time has been spent. Time is
-      shown as percentage of total time and absolute time. For more
+      shown as a percentage of total time and absolute time. For more
       information, see the <seealso marker="tools:eprof">eprof</seealso>
       manual page in <c>tools</c>.</p>
     </section>
@@ -234,7 +234,7 @@
     implementation of a given algorithm or function is the fastest.
     Benchmarking is far from an exact science. Today's operating systems
     generally run background tasks that are difficult to turn off.
-    Caches and multiple CPU cores does not facilitate benchmarking.
+    Caches and multiple CPU cores do not facilitate benchmarking.
     It would be best to run UNIX computers in single-user mode when
     benchmarking, but that is inconvenient to say the least for casual
     testing.</p>
-- 
2.31.1