# HG changeset patch
# User František Kučera <franta-hg@frantovo.cz>
# Date 1547813934 -3600
# Node ID d81c623de7881460ece6f69f0b82f2bea9ebdecc
# Parent  627ff99d475b5ce2034c82faa0647cf8efec3345
examples: small updates

diff -r 627ff99d475b -r d81c623de788 relpipe-data/examples.xml
--- a/relpipe-data/examples.xml	Fri Jan 18 00:39:51 2019 +0100
+++ b/relpipe-data/examples.xml	Fri Jan 18 13:18:54 2019 +0100
@@ -703,8 +703,8 @@
 			Our filesystems contain valuable information and using proper tools we can extract them.
 			Using <code>relpipe-in-filesystem</code> we can gather metadata of our files and process them in relational way.
 			This tools does not traverse our filesystem (remember the rule: <em>do one thing and do it well</em>),
-			instead, it eats list of file paths separated from standard input.
-			It is typically used together with the <code>find</code> command, but we can also create such list by hand using e.g. <code>printf</code> command.
+			instead, it eats a list of file paths separated by <code>\0</code>.
+			It is typically used together with the <code>find</code> command, but we can also create such list by hand using e.g. <code>printf</code> command or <code>tr \\n \\0</code>.
 		</p>
 		
 		<m:pre jazyk="bash">find /etc/ssh/ -print0 | relpipe-in-filesystem | relpipe-out-tabular</m:pre>
@@ -821,7 +821,7 @@
 	| relpipe-out-tabular
 ]]></m:pre>
 
-		<p>And now we know, where the files on our disk come from:</p>
+		<p>And now we know, where the files on our disk came from:</p>
 
 		<pre><![CDATA[filesystem:
  ╭───────────────────────────┬────────────────┬────────────────────────────────────────────────────────────────────╮