Merge branch 'maint' into sverk/trace-process_dump-matchstate

Conflicts:
	erts/emulator/beam/erl_printf_term.c
	erts/emulator/beam/erl_term.c
	erts/emulator/beam/utils.c

1 files changed, 26 insertions, 16 deletions

diff --git a/system/doc/tutorial/example.xmlsrc b/system/doc/tutorial/example.xmlsrc
index f87eb217e9..d49c7fe88c 100644
--- a/system/doc/tutorial/example.xmlsrc
+++ b/system/doc/tutorial/example.xmlsrc
@@ -4,20 +4,21 @@
 <chapter>
   <header>
     <copyright>
-      <year>2000</year><year>2013</year>
+      <year>2000</year><year>2015</year>
       <holder>Ericsson AB. All Rights Reserved.</holder>
     </copyright>
     <legalnotice>
-      The contents of this file are subject to the Erlang Public License,
-      Version 1.1, (the "License"); you may not use this file except in
-      compliance with the License. You should have received a copy of the
-      Erlang Public License along with this software. If not, it can be
-      retrieved online at http://www.erlang.org/.
-    
-      Software distributed under the License is distributed on an "AS IS"
-      basis, WITHOUT WARRANTY OF ANY KIND, either express or implied. See
-      the License for the specific language governing rights and limitations
-      under the License.
+      Licensed under the Apache License, Version 2.0 (the "License");
+      you may not use this file except in compliance with the License.
+      You may obtain a copy of the License at
+ 
+          http://www.apache.org/licenses/LICENSE-2.0
+
+      Unless required by applicable law or agreed to in writing, software
+      distributed under the License is distributed on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+      See the License for the specific language governing permissions and
+      limitations under the License.
     
     </legalnotice>
 
@@ -31,16 +32,25 @@
 
   <section>
     <title>Description</title>
-    <p>A common interoperability situation is when there exists a piece of code solving some complex problem, and we would like to incorporate this piece of code in our Erlang program. Suppose for example we have the following C functions that we would like to be able to call from Erlang.</p>
-    <codeinclude file="complex.c" tag="" type="none"></codeinclude>
-    <p>(For the sake of keeping the example as simple as possible, the functions are not very complicated in this case).</p>
-    <p>Preferably we would like to able to call <c>foo</c> and <c>bar</c> without having to bother about them actually being C functions.</p>
+    <p>A common interoperability situation is when you want to incorporate
+      a piece of code, solving a complex problem, in your Erlang
+      program. Suppose for example, that you have the following C
+      functions that you would like to call from Erlang:</p>
+      <codeinclude file="complex.c" tag="" type="none"></codeinclude>
+    <p>The functions are deliberately kept as simple as possible, for
+      readability reasons.</p>
+    <p>From an Erlang perspektive, it is preferable to be able to call
+      <c>foo</c> and <c>bar</c> without having to bother about that
+      they are C functions:</p>
     <pre>
 % Erlang code
 ...
 Res = complex:foo(X),
 ...</pre>
-    <p>The communication with C is hidden in the implementation of <c>complex.erl</c>. In the following chapters it is shown how this module can be implemented using the different interoperability mechanisms.</p>
+    <p>Here, the communication with C is hidden in the implementation
+      of <c>complex.erl</c>.
+      In the following sections, it is shown how this module can be
+      implemented using the different interoperability mechanisms.</p>
   </section>
 </chapter>