From 2d3ab68c60e8bacf9e0efe403895e7065ef683be Mon Sep 17 00:00:00 2001
From: Hans Bolinder <hasse@erlang.org>
Date: Thu, 12 Mar 2015 15:35:13 +0100
Subject: Update Interoperability Tutorial

Language cleaned up by the technical writers xsipewe and tmanevik
from Combitech. Proofreading and corrections by Hans Bolinder.
---
 system/doc/tutorial/introduction.xml | 26 +++++++++++++++++++++-----
 1 file changed, 21 insertions(+), 5 deletions(-)

(limited to 'system/doc/tutorial/introduction.xml')

diff --git a/system/doc/tutorial/introduction.xml b/system/doc/tutorial/introduction.xml
index ed86a00f76..dcf462e311 100644
--- a/system/doc/tutorial/introduction.xml
+++ b/system/doc/tutorial/introduction.xml
@@ -4,7 +4,7 @@
 <chapter>
   <header>
     <copyright>
-      <year>2000</year><year>2013</year>
+      <year>2000</year><year>2015</year>
       <holder>Ericsson AB. All Rights Reserved.</holder>
     </copyright>
     <legalnotice>
@@ -28,18 +28,34 @@
     <rev></rev>
     <file>introduction.xml</file>
   </header>
+  <marker id="interoperability tutorial"></marker>
+  <p>This section informs on interoperability, that is, information
+    exchange, between Erlang and other programming languages. The
+    included examples mainly treat interoperability between Erlang and
+    C.</p>
 
   <section>
     <title>Purpose</title>
-    <p>The purpose of this tutorial is to give the reader an orientation of the different interoperability mechanisms that can be used when integrating a program written in Erlang with a program written in another programming language, from the Erlang programmer's point of view.</p>
+    <p>The purpose of this tutorial is to describe different
+      interoperability mechanisms that can be used when integrating a
+      program written in Erlang with a program written in another
+      programming language, from the Erlang programmer's
+      perspective.</p>
   </section>
 
   <section>
     <title>Prerequisites</title>
-    <p>It is assumed that the reader is a skilled Erlang programmer, familiar with concepts such as Erlang data types, processes, messages and error handling.</p>
-    <p>To illustrate the interoperability principles C programs running in a UNIX environment have been used. It is assumed that the reader has enough knowledge to be able to apply these principles to the relevant programming languages and platforms.</p>
+    <p>It is assumed that you are a skilled Erlang programmer,
+      familiar with concepts such as Erlang data types, processes,
+      messages, and error handling.</p>
+    <p>To illustrate the interoperability principles, C programs
+      running in a UNIX environment have been used. It is assumed that
+      you have enough knowledge to apply these principles to the
+      relevant programming languages and platforms.</p>
     <note>
-      <p>For the sake of readability, the example code has been kept as simple as possible. It does not include functionality such as error handling, which might be vital in a real-life system.</p>
+      <p>For readability, the example code is kept as simple as
+        possible. For example, it does not include error handling,
+        which might be vital in a real-life system.</p>
     </note>
   </section>
 </chapter>
-- 
cgit v1.2.3