From 61b173e47e4157e784f32fc46a9867fbadc9a53a Mon Sep 17 00:00:00 2001
From: Boris 'billiob' Faure <billiob@gmail.com>
Date: Mon, 1 Nov 2010 22:11:08 +0100
Subject: fix typo in mnesia doc

---
 lib/mnesia/doc/src/Mnesia_chap2.xmlsrc | 6 ++----
 lib/mnesia/doc/src/Mnesia_chap3.xml    | 2 +-
 lib/mnesia/doc/src/mnesia.xml          | 2 +-
 3 files changed, 4 insertions(+), 6 deletions(-)

diff --git a/lib/mnesia/doc/src/Mnesia_chap2.xmlsrc b/lib/mnesia/doc/src/Mnesia_chap2.xmlsrc
index 0714c7b645..f263ea4ed2 100644
--- a/lib/mnesia/doc/src/Mnesia_chap2.xmlsrc
+++ b/lib/mnesia/doc/src/Mnesia_chap2.xmlsrc
@@ -235,9 +235,7 @@
         <seealso marker="Mnesia_chap3#start_mnesia">Starting Mnesia</seealso>.
         </item>
       </list>
-      <p>Continuing the dialogue with the Erlang shell will produce the following
-        the following:
-        </p>
+      <p>Continuing the dialogue with the Erlang shell will produce the following:</p>
       <pre><![CDATA[
         3> company:init().
         {atomic,ok}
@@ -418,7 +416,7 @@ In_proj</tcaption>
         interchangeably throughout this book. 
         </p>
       <p>A Mnesia table is populated by Mnesia records. For example,
-        the tuple <c>{boss, klacke, bjarne}</c> is an record.  The
+        the tuple <c>{boss, klacke, bjarne}</c> is a record.  The
         second element in this tuple is the key. In order to uniquely
         identify a table row both the key and the table name is
         needed. The term <em>object identifier</em>, 
diff --git a/lib/mnesia/doc/src/Mnesia_chap3.xml b/lib/mnesia/doc/src/Mnesia_chap3.xml
index 9a382bcb5a..c3e584123e 100644
--- a/lib/mnesia/doc/src/Mnesia_chap3.xml
+++ b/lib/mnesia/doc/src/Mnesia_chap3.xml
@@ -132,7 +132,7 @@
             function changes the format on all records in table
             <c>Tab</c>. It applies the argument <c>Fun</c> to all
             records in the table. <c>Fun</c> shall be a function which
-            takes an record of the old type, and returns the record of the new
+            takes a record of the old type, and returns the record of the new
             type. The table key may not be changed.</p>
           <code type="none">
 -record(old, {key, val}).
diff --git a/lib/mnesia/doc/src/mnesia.xml b/lib/mnesia/doc/src/mnesia.xml
index 5d3bcf830e..74486b32bd 100644
--- a/lib/mnesia/doc/src/mnesia.xml
+++ b/lib/mnesia/doc/src/mnesia.xml
@@ -2835,7 +2835,7 @@ raise(Name, Amount) ->
     </func>
     <func>
       <name>write(Tab, Record, LockKind) -> transaction abort | ok </name>
-      <fsummary>Write an record into the database.</fsummary>
+      <fsummary>Write a record into the database.</fsummary>
       <desc>
         <p>Writes the record <c>Record</c> to the table <c>Tab</c>.
           </p>
-- 
cgit v1.2.3


From 0d66208766000c58222b2ba471178fb956fc8f31 Mon Sep 17 00:00:00 2001
From: Boris 'billiob' Faure <billiob@gmail.com>
Date: Mon, 1 Nov 2010 22:13:45 +0100
Subject: remove '\011' from mnesia doc

---
 lib/mnesia/doc/src/Mnesia_chap2.xmlsrc |  6 +++---
 lib/mnesia/doc/src/Mnesia_chap3.xml    |  4 ++--
 lib/mnesia/doc/src/Mnesia_chap5.xmlsrc | 18 +++++++++---------
 lib/mnesia/doc/src/mnesia.xml          | 14 +++++++-------
 4 files changed, 21 insertions(+), 21 deletions(-)

diff --git a/lib/mnesia/doc/src/Mnesia_chap2.xmlsrc b/lib/mnesia/doc/src/Mnesia_chap2.xmlsrc
index f263ea4ed2..2e2cc386b7 100644
--- a/lib/mnesia/doc/src/Mnesia_chap2.xmlsrc
+++ b/lib/mnesia/doc/src/Mnesia_chap2.xmlsrc
@@ -551,7 +551,7 @@ In_proj</tcaption>
           stored in the database: 
           </p>
         <pre>
-\011  mnesia:select(employee, [{#employee{sex = female, name = '$1', _ = '_'},[], ['$1']}]).
+mnesia:select(employee, [{#employee{sex = female, name = '$1', _ = '_'},[], ['$1']}]).
         </pre>
         <p>Select must always run within an activity such as a
           transaction. To be able to call from the shell we might
@@ -585,8 +585,8 @@ In_proj</tcaption>
           </p>
         <pre>
           Q = qlc:q([E#employee.name || E <![CDATA[<-]]> mnesia:table(employee),
-\011                                E#employee.sex == female]),
-\011  qlc:e(Q),
+                                E#employee.sex == female]),
+          qlc:e(Q),
         </pre>
         <p>Accessing mnesia tables from a QLC list comprehension must
           always be done within a transaction. Consider the following
diff --git a/lib/mnesia/doc/src/Mnesia_chap3.xml b/lib/mnesia/doc/src/Mnesia_chap3.xml
index c3e584123e..2db9af9cf7 100644
--- a/lib/mnesia/doc/src/Mnesia_chap3.xml
+++ b/lib/mnesia/doc/src/Mnesia_chap3.xml
@@ -418,8 +418,8 @@ skeppet %<input>erl -sname b -mnesia dir '"/ldisc/scratch/Mnesia.company"'</inpu
               type <c>set</c> and <c>bag</c>: </p>
             <pre>
  f() -> F =  fun() ->
-\011      mnesia:write({foo, 1, 2}), mnesia:write({foo, 1, 3}),
-\011      mnesia:read({foo, 1}) end, mnesia:transaction(F).             </pre>
+     mnesia:write({foo, 1, 2}), mnesia:write({foo, 1, 3}),
+     mnesia:read({foo, 1}) end, mnesia:transaction(F).             </pre>
             <p>This transaction will return the list <c>[{foo,1,3}]</c> if
               the <c>foo</c> table is of type <c>set</c>.  However, list
               <c>[{foo,1,2}, {foo,1,3}]</c> will return if the table is
diff --git a/lib/mnesia/doc/src/Mnesia_chap5.xmlsrc b/lib/mnesia/doc/src/Mnesia_chap5.xmlsrc
index 1c7e3662e1..30a8991465 100644
--- a/lib/mnesia/doc/src/Mnesia_chap5.xmlsrc
+++ b/lib/mnesia/doc/src/Mnesia_chap5.xmlsrc
@@ -335,7 +335,7 @@ ok
             explicitly be set at table creation. The default is
             <c>0</c>, but if <c>n_disc_copies</c> and
             <c>n_disc_only_copies</c> also are <c>0</c>,
-            <c>n_ram_copies</c>\011will default be set to <c>1</c>. 
+            <c>n_ram_copies</c> will default be set to <c>1</c>.
             </p>
         </item>
         <tag><c>{n_disc_copies, Int}</c></tag>
@@ -408,7 +408,7 @@ ok
 (a@sam)4> SecProps = [{foreign_key, {prim_dict, sec_val}}].
 [{foreign_key,{prim_dict,sec_val}}]
 (a@sam)5> mnesia:create_table(sec_dict, 
-\011                      [{frag_properties, SecProps},
+                              [{frag_properties, SecProps},
 (a@sam)5>                      {attributes, [sec_key, sec_val]}]).
 {atomic,ok}
 (a@sam)6> Write = fun(Rec) -> mnesia:write(Rec) end.
@@ -418,23 +418,23 @@ ok
 (a@sam)8> SecKey = 42.
 42
 (a@sam)9> mnesia:activity(sync_dirty, Write,
-\011\011          [{prim_dict, PrimKey, -11}], mnesia_frag).
+                          [{prim_dict, PrimKey, -11}], mnesia_frag).
 ok
 (a@sam)10> mnesia:activity(sync_dirty, Write,
-\011\011           [{sec_dict, SecKey, PrimKey}], mnesia_frag).
+                           [{sec_dict, SecKey, PrimKey}], mnesia_frag).
 ok
 (a@sam)11> mnesia:change_table_frag(prim_dict, {add_frag, [node()]}).
 {atomic,ok}
 (a@sam)12> SecRead = fun(PrimKey, SecKey) ->
-\011\011       mnesia:read({sec_dict, PrimKey}, SecKey, read) end.
+               mnesia:read({sec_dict, PrimKey}, SecKey, read) end.
 #Fun<erl_eval>
 (a@sam)13> mnesia:activity(transaction, SecRead,
-\011\011           [PrimKey, SecKey], mnesia_frag).
+                           [PrimKey, SecKey], mnesia_frag).
 [{sec_dict,42,11}]
 (a@sam)14> Info = fun(Tab, Item) -> mnesia:table_info(Tab, Item) end.
 #Fun<erl_eval>
 (a@sam)15> mnesia:activity(sync_dirty, Info,
-\011\011           [prim_dict, frag_size], mnesia_frag).
+                           [prim_dict, frag_size], mnesia_frag).
 [{prim_dict,0},
  {prim_dict_frag2,0},
  {prim_dict_frag3,0},
@@ -444,7 +444,7 @@ ok
  {prim_dict_frag7,0},
  {prim_dict_frag8,0}]
 (a@sam)16> mnesia:activity(sync_dirty, Info,
-\011\011           [sec_dict, frag_size], mnesia_frag).
+                           [sec_dict, frag_size], mnesia_frag).
 [{sec_dict,0},
  {sec_dict_frag2,0},
  {sec_dict_frag3,0},
@@ -1051,7 +1051,7 @@ ok
            ActivityID will be received.  Note that this event may still be received even
            if no table events with a corresponding ActivityID were received, depending on
            the tables to which the receiving process is subscribed.</p>
-	 <p>Dirty operations always only contain one update and thus no activity event is sent.</p>
+         <p>Dirty operations always only contain one update and thus no activity event is sent.</p>
        </item>
      </taglist>
     </section>
diff --git a/lib/mnesia/doc/src/mnesia.xml b/lib/mnesia/doc/src/mnesia.xml
index 74486b32bd..30adc0f071 100644
--- a/lib/mnesia/doc/src/mnesia.xml
+++ b/lib/mnesia/doc/src/mnesia.xml
@@ -799,7 +799,7 @@ mnesia:change_table_copy_type(person, node(), disc_copies)
           </item>
           <item>
             <p><c>{local_content, Bool}</c>, where <c>Bool</c> must be
-              either <c>true</c> or <c>false</c>. The default value is <c>false</c>.\011      </p>
+              either <c>true</c> or <c>false</c>. The default value is <c>false</c>.</p>
           </item>
         </list>
         <p>For example, the following call creates the <c>person</c> table
@@ -1067,7 +1067,7 @@ mnesia:create_table(person,
           <c>mnesia:dirty_next/2</c> but returns the previous object in
           Erlang term  order for the ordered_set table type. For
           all other table types, <c>mnesia:dirty_next/2</c> and 
-          <c>mnesia:dirty_prev/2</c> are synonyms.\011  </p>
+          <c>mnesia:dirty_prev/2</c> are synonyms.</p>
       </desc>
     </func>
     <func>
@@ -1702,7 +1702,7 @@ mnesia:create_table(person,
           <c>mnesia:next/2</c> but returns the previous object in
           Erlang term  order for the ordered_set table type. For
           all other table types, <c>mnesia:next/2</c> and 
-          <c>mnesia:prev/2</c> are synonyms.\011  </p>
+          <c>mnesia:prev/2</c> are synonyms.</p>
       </desc>
     </func>
     <func>
@@ -1891,10 +1891,10 @@ mnesia:create_table(person,
         <p>For example to find the names of all male persons with an age over 30 in table
           Tab do:</p>
         <code type="none">
-\011  MatchHead = #person{name='$1', sex=male, age='$2', _='_'},
-\011  Guard = {'>', '$2', 30},
-\011  Result = '$1',
-\011  mnesia:select(Tab,[{MatchHead, [Guard], [Result]}]),
+MatchHead = #person{name='$1', sex=male, age='$2', _='_'},
+Guard = {'>', '$2', 30},
+Result = '$1',
+mnesia:select(Tab,[{MatchHead, [Guard], [Result]}]),
         </code>
       </desc>
     </func>
-- 
cgit v1.2.3


From 4e0a65b564d9ce015ad375fe3ccee864d6b8a93f Mon Sep 17 00:00:00 2001
From: Boris 'billiob' Faure <billiob@gmail.com>
Date: Mon, 1 Nov 2010 22:17:30 +0100
Subject: doc: "works like" instead of "works as" + missing like

---
 lib/mnesia/doc/src/Mnesia_chap4.xmlsrc |  4 ++--
 lib/mnesia/doc/src/mnesia.xml          | 12 ++++++------
 2 files changed, 8 insertions(+), 8 deletions(-)

diff --git a/lib/mnesia/doc/src/Mnesia_chap4.xmlsrc b/lib/mnesia/doc/src/Mnesia_chap4.xmlsrc
index 7d89c1b0dd..6e8055326b 100644
--- a/lib/mnesia/doc/src/Mnesia_chap4.xmlsrc
+++ b/lib/mnesia/doc/src/Mnesia_chap4.xmlsrc
@@ -514,13 +514,13 @@ The behavior is undefined if any process perform a write
        of the table itself. This is an implementation detail, but remember
        the dirty functions are low level functions. 
       </item>
-      <item><c>mnesia:dirty_last(Tab)</c> This function works exactly as
+      <item><c>mnesia:dirty_last(Tab)</c> This function works exactly like
       <c>mnesia:dirty_first/1</c> but returns the last object in
        Erlang  term  order for the <c>ordered_set</c> table type. For
        all other table types, <c>mnesia:dirty_first/1</c> and 
       <c>mnesia:dirty_last/1</c> are synonyms.
       </item>
-      <item><c>mnesia:dirty_prev(Tab, Key)</c> This function works exactly as
+      <item><c>mnesia:dirty_prev(Tab, Key)</c> This function works exactly like
       <c>mnesia:dirty_next/2</c> but returns the previous object in
        Erlang term  order for the ordered_set table type. For
        all other table types, <c>mnesia:dirty_next/2</c> and 
diff --git a/lib/mnesia/doc/src/mnesia.xml b/lib/mnesia/doc/src/mnesia.xml
index 30adc0f071..16e78ea0af 100644
--- a/lib/mnesia/doc/src/mnesia.xml
+++ b/lib/mnesia/doc/src/mnesia.xml
@@ -1022,7 +1022,7 @@ mnesia:create_table(person,
       <name>dirty_last(Tab) ->  Key | exit({aborted, Reason}) </name>
       <fsummary>Return the key for the last record in a table.</fsummary>
       <desc>
-        <p>This function works exactly 
+        <p>This function works exactly like
           <c>mnesia:dirty_first/1</c> but returns the last object in
           Erlang  term  order for the <c>ordered_set</c> table type. For
           all other table types, <c>mnesia:dirty_first/1</c> and 
@@ -1063,7 +1063,7 @@ mnesia:create_table(person,
       <name>dirty_prev(Tab, Key) -> Key | exit({aborted, Reason}) </name>
       <fsummary>Return the previous key in a table. </fsummary>
       <desc>
-        <p>This function works exactly 
+        <p>This function works exactly like
           <c>mnesia:dirty_next/2</c> but returns the previous object in
           Erlang term  order for the ordered_set table type. For
           all other table types, <c>mnesia:dirty_next/2</c> and 
@@ -1334,7 +1334,7 @@ mnesia:create_table(person,
       <name>foldr(Function, Acc, Table) -> NewAcc | transaction abort </name>
       <fsummary>Call Function for each record in Table  </fsummary>
       <desc>
-        <p>This function works exactly as 
+        <p>This function works exactly like
           <c>foldl/3</c> but iterates the table in the opposite order 
           for the <c>ordered_set</c> table type. For
           all other table types, <c>foldr/3</c> and 
@@ -1512,14 +1512,14 @@ mnesia:create_table(person,
       <fsummary>Check if code is running in a transaction.</fsummary>
       <desc>
         <p>When this function is executed inside a transaction context
-	  it returns <c>true</c>, otherwise <c>false</c>.</p>
+          it returns <c>true</c>, otherwise <c>false</c>.</p>
       </desc>
     </func>
     <func>
       <name>last(Tab) ->  Key | transaction abort </name>
       <fsummary>Return the key for the last record in a table.</fsummary>
       <desc>
-        <p>This function works exactly 
+        <p>This function works exactly like
           <c>mnesia:first/1</c> but returns the last object in
           Erlang  term  order for the <c>ordered_set</c> table type. For
           all other table types, <c>mnesia:first/1</c> and 
@@ -1698,7 +1698,7 @@ mnesia:create_table(person,
       <name>prev(Tab, Key) -> Key | transaction abort </name>
       <fsummary>Return the previous key in a table. </fsummary>
       <desc>
-        <p>This function works exactly 
+        <p>This function works exactly like
           <c>mnesia:next/2</c> but returns the previous object in
           Erlang term  order for the ordered_set table type. For
           all other table types, <c>mnesia:next/2</c> and 
-- 
cgit v1.2.3