diff options
author | Björn Gustavsson <[email protected]> | 2010-02-28 08:51:15 +0100 |
---|---|---|
committer | Björn Gustavsson <[email protected]> | 2010-02-28 09:14:51 +0100 |
commit | a0fc666ec22109206141936cb4550bea61da76e9 (patch) | |
tree | 56e7122df9d78fb4367f2cfcd8fc9f8979d3cd4c /system/doc/efficiency_guide | |
parent | d7044099b8da0e5ea38b46764fd005698dc8c612 (diff) | |
download | otp-a0fc666ec22109206141936cb4550bea61da76e9.tar.gz otp-a0fc666ec22109206141936cb4550bea61da76e9.tar.bz2 otp-a0fc666ec22109206141936cb4550bea61da76e9.zip |
Efficiency Guide: Fix typos
Diffstat (limited to 'system/doc/efficiency_guide')
-rw-r--r-- | system/doc/efficiency_guide/advanced.xml | 2 | ||||
-rw-r--r-- | 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> |