relpipe-data/index.xml
branchv_0
changeset 148 d51787006954
parent 146 8c2e2dbee5cc
child 183 82897ccc01ce
--- a/relpipe-data/index.xml	Mon Nov 26 19:02:11 2018 +0100
+++ b/relpipe-data/index.xml	Tue Nov 27 00:22:01 2018 +0100
@@ -84,7 +84,7 @@
 		
 		
 		<p>
-			Now the question is: how the data passed through pipes should be formatted and structured.
+			But the question is: how the data passed through pipes should be formatted and structured.
 			There is wide spectrum of options from simple unstructured text files (just arrays of lines)
 			through various <abbr title="delimiter-separated values e.g. CSV separated by comas">DSV</abbr>
 			to formats like XML (YAML, JSON, ASN.1, Diameter, S-expressions etc.).
@@ -140,7 +140,7 @@
 			
 		<p>
 			<m:name/> respect the existing ecosystem and are rather an improvement or supplement than a replacement.
-			So <m:name/> are not a:
+			So the <m:name/> are not a:
 		</p>
 		
 		<ul>