# HG changeset patch
# User František Kučera <franta-hg@frantovo.cz>
# Date 1544653665 -3600
# Node ID f0a2916368e27be54a382e928148c12085a9be8b
# Parent  74fecc2ba590412f1f3a2eff8db88593efbc6cbe
small fixes and improvements

diff -r 74fecc2ba590 -r f0a2916368e2 relpipe-data/examples.xml
--- a/relpipe-data/examples.xml	Mon Dec 10 22:14:04 2018 +0100
+++ b/relpipe-data/examples.xml	Wed Dec 12 23:27:45 2018 +0100
@@ -375,7 +375,7 @@
 		<h2>Rename VG in /etc/fstab using relpipe-tr-sed</h2>
 		
 		<p>
-			Let's expect that we have a <code>/etc/fstab</code> with many lines defining the mount-points (directories) of particular devices (disks) and we are using LVM.
+			Assume that we have an <code>/etc/fstab</code> with many lines defining the mount-points (directories) of particular devices (disks) and we are using LVM.
 			If we rename a volume group (VG), we have to change all of them. The lines look like this one:
 		</p>
 		
diff -r 74fecc2ba590 -r f0a2916368e2 relpipe-data/principles.xml
--- a/relpipe-data/principles.xml	Mon Dec 10 22:14:04 2018 +0100
+++ b/relpipe-data/principles.xml	Wed Dec 12 23:27:45 2018 +0100
@@ -135,7 +135,7 @@
 		<p>
 			However, there are cases where such streaming is not feasible e.g. if we need to compute some statistics or a column widths while printing a table in the terminal.
 			In such situation, we must read the whole relation and only then generate the output.
-			But we should still be able to do streaming on the relations level e.i. if there are more relation, we always hold only one of them in the memory.
+			But we should still be able to do streaming on the relations level i.e. if there are more relation, we always hold only one of them in the memory.
 		</p>
 		
 		<p>