# HG changeset patch
# User František Kučera <franta-hg@frantovo.cz>
# Date 1543230940 -3600
# Node ID 42bbbccd87f373cb9eaeccb5b311af6bb7a53654
# Parent  ee7e9615167333c3258421dd14e3b5375212b449
small fixes and improvements

diff -r ee7e96151673 -r 42bbbccd87f3 relpipe-data/classic-example.xml
--- a/relpipe-data/classic-example.xml	Sun Nov 25 19:58:06 2018 +0100
+++ b/relpipe-data/classic-example.xml	Mon Nov 26 12:15:40 2018 +0100
@@ -42,8 +42,8 @@
 WHITE]]></pre>
 
 		<p>
-			So we have a list of colors of our dogs printed upper-case. 
-			In case we have several dogs of same colors, we could avoid duplicates simply by adding <code>| sort -u</code> in the pipeline (after the <code>cut</code> part).
+			So we have a list of colors of our dogs printed in upper-case. 
+			In case we have several dogs of same color, we could avoid duplicates simply by adding <code>| sort -u</code> in the pipeline (after the <code>cut</code> part).
 		</p>
 
 		<h2>The great parts</h2>
@@ -59,6 +59,12 @@
 			And we do it well without being distracted by any low-level issues.
 		</p>
 		
+		<p>
+			Each program used in the pipeline can be written in different programming language and they will work together.
+			Tools written in C, C++, Java, Lisp, Perl, Python, Rust or any other language can be combined together.
+			Thus optimal language can be used for each task.
+		</p>
+		
 		<h2>The pitfalls</h2>
 		
 		<p>
diff -r ee7e96151673 -r 42bbbccd87f3 relpipe-data/index.xml
--- a/relpipe-data/index.xml	Sun Nov 25 19:58:06 2018 +0100
+++ b/relpipe-data/index.xml	Mon Nov 26 12:15:40 2018 +0100
@@ -118,7 +118,7 @@
 		
 		<ul>
 			<li>Shell – we use existing shells (e.g. GNU Bash), work with any shell and even without a shell (e.g. as a stream format passed through a network or stored in a file).</li>
-			<li>Terminal emulator – same as with shells, we use existing terminals and we can use <m:name/> also outside any terminal; if we interact with the terminal, we use standard means as Unicode, ANSI escape sequences etc.</li>
+			<li>Terminal emulator – same as with shells, we use existing terminals and we can use <m:name/> also outside any terminal; if we interact with the terminal, we use standard means like Unicode, ANSI escape sequences etc.</li>
 			<li>IDE – we can use standard <m:unix/> tools as an IDE (GNU Screen, Make etc.) or any other IDE.</li>
 			<li>Programming language – <m:name/> are language-independent data format and can be produced or consumed in any programming language.</li>
 			<li>Query language – although some of our tools are doing queries, filtering or transformations, we are not inventing a new query language – instead, we use existing languages like SQL, XPath or regular expressions.</li>
@@ -131,7 +131,7 @@
 		
 		<p>
 			The main ideas and the roadmap are quite clear, but many things will change (including the format internals and interfaces of the libraries and tools).
-			Because we know how important the API and ABI stability is, we are not ready to publish the version 1.0 yet.
+			Because we understand how important the API and ABI stability is, we are not ready to publish the version 1.0 yet.
 		</p>
 		<p>
 			On the other hand, the already published tools (tagged as v0.x in v_0 branch) should work quite well (should compile, should run, should not segfault often, should not wipe your hard drive or kill your cat),