From a0fc666ec22109206141936cb4550bea61da76e9 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Bj=C3=B6rn=20Gustavsson?= <bjorn@erlang.org>
Date: Sun, 28 Feb 2010 08:51:15 +0100
Subject: Efficiency Guide: Fix typos

---
 system/doc/efficiency_guide/advanced.xml | 2 +-
 system/doc/efficiency_guide/myths.xml    | 4 ++--
 2 files changed, 3 insertions(+), 3 deletions(-)

diff --git a/system/doc/efficiency_guide/advanced.xml b/system/doc/efficiency_guide/advanced.xml
index 0ec3afbd59..82f82f9fd6 100644
--- a/system/doc/efficiency_guide/advanced.xml
+++ b/system/doc/efficiency_guide/advanced.xml
@@ -175,7 +175,7 @@ The maximum number of atoms is 1048576. </item>
       <tag><em>Total amount of data allocated by an Erlang node</em></tag>
       <item>The Erlang runtime system can use the complete 32 (or 64) bit address space,
        but the operating system often limits a single process to use less than that.</item>
-      <tag><em>length of a node name</em></tag>
+      <tag><em>Length of a node name</em></tag>
       <item>An Erlang node name has the form host@shortname or host@longname. The node name is 
        used as an atom within the system so the maximum size of 255 holds for the node name too.</item>
       <tag><em>Open ports</em></tag>
diff --git a/system/doc/efficiency_guide/myths.xml b/system/doc/efficiency_guide/myths.xml
index 76a72368bb..65113c9372 100644
--- a/system/doc/efficiency_guide/myths.xml
+++ b/system/doc/efficiency_guide/myths.xml
@@ -168,8 +168,8 @@ vanilla_reverse([], Acc) ->
     <p>Actually, string handling could be slow if done improperly.
     In Erlang, you'll have to think a little more about how the strings
     are used and choose an appropriate representation and use
-    the <seealso marker="stdlib:re">re</seealso> instead of the obsolete
-    <c>regexp</c> module if you are going to use regualr expressions.</p>
+    the <seealso marker="stdlib:re">re</seealso> module instead of the obsolete
+    <c>regexp</c> module if you are going to use regular expressions.</p>
   </section>
 
   <section>
-- 
cgit v1.2.3


From cedee54fd81ddf8e4423e5ad4b3e6454001c6e95 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Bj=C3=B6rn=20Gustavsson?= <bjorn@erlang.org>
Date: Sun, 28 Feb 2010 09:10:34 +0100
Subject: Efficiency Guide: The maximum number of atoms can be configured

---
 system/doc/efficiency_guide/advanced.xml      | 3 ++-
 system/doc/efficiency_guide/commoncaveats.xml | 2 +-
 2 files changed, 3 insertions(+), 2 deletions(-)

diff --git a/system/doc/efficiency_guide/advanced.xml b/system/doc/efficiency_guide/advanced.xml
index 82f82f9fd6..6a191ebdb8 100644
--- a/system/doc/efficiency_guide/advanced.xml
+++ b/system/doc/efficiency_guide/advanced.xml
@@ -154,7 +154,8 @@ On 64-bit architectures: 4 words for a reference from the current local node, an
       <item>255</item>
       <tag><em>Atoms </em></tag>
       <item>      <marker id="atoms"></marker>
-The maximum number of atoms is 1048576. </item>
+	By default, the maximum number of atoms is 1048576.
+	This limit can be raised or lowered using the <c>+t</c> option.</item>
       <tag><em>Ets-tables</em></tag>
       <item>The default is 1400, can be changed with the environment variable <c>ERL_MAX_ETS_TABLES</c>.</item>
       <tag><em>Elements in a tuple</em></tag>
diff --git a/system/doc/efficiency_guide/commoncaveats.xml b/system/doc/efficiency_guide/commoncaveats.xml
index e18e5aa510..326db6df8c 100644
--- a/system/doc/efficiency_guide/commoncaveats.xml
+++ b/system/doc/efficiency_guide/commoncaveats.xml
@@ -69,7 +69,7 @@
 
     <p>Atoms are not garbage-collected. Once an atom is created, it will never
     be removed. The emulator will terminate if the limit for the number
-    of atoms (1048576) is reached.</p>
+    of atoms (1048576 by default) is reached.</p>
 
     <p>Therefore, converting arbitrary input strings to atoms could be
     dangerous in a system that will run continuously.
-- 
cgit v1.2.3


From 5a662ce8fa95ab467e77a654088df43e5528a584 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Bj=C3=B6rn=20Gustavsson?= <bjorn@erlang.org>
Date: Sun, 28 Feb 2010 09:41:40 +0100
Subject: Efficiency Guide: Recommend external funs over tuple funs

---
 system/doc/efficiency_guide/functions.xml | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/system/doc/efficiency_guide/functions.xml b/system/doc/efficiency_guide/functions.xml
index d55b60e39c..0d2e756900 100644
--- a/system/doc/efficiency_guide/functions.xml
+++ b/system/doc/efficiency_guide/functions.xml
@@ -179,7 +179,9 @@ explicit_map_pairs(Map, Xs0, Ys0) ->
        A "tuple fun", <c>{Module,Function}</c>, is not a fun.
        The cost for calling a "tuple fun" is similar to that
        of <c>apply/3</c> or worse. Using "tuple funs" is <em>strongly discouraged</em>,
-       as they may not be supported in a future release.</p></warning>
+       as they may not be supported in a future release,
+       and because there exists a superior alternative since the R10B
+       release, namely the <c>fun Module:Function/Arity</c> syntax.</p></warning>
 
        <p><c>apply/3</c> must look up the code for the function to execute
        in a hash table. Therefore, it will always be slower than a
-- 
cgit v1.2.3