--- a/relpipe-data/examples-guile-multiple-relations.xml	Sat Sep 12 13:20:21 2020 +0200
+++ b/relpipe-data/examples-guile-multiple-relations.xml	Fri Sep 25 14:38:24 2020 +0200
@@ -2,14 +2,14 @@
 	xmlns="https://trac.frantovo.cz/xml-web-generator/wiki/xmlns/strana"
 	xmlns:m="https://trac.frantovo.cz/xml-web-generator/wiki/xmlns/makro">
 	
-	<nadpis>Processing multiple relations with Guile</nadpis>
+	<nadpis>Processing multiple relations with Scheme</nadpis>
 	<perex>filter some relations and others keep unaffected</perex>
 	<m:pořadí-příkladu>01800</m:pořadí-příkladu>
 
 	<text xmlns="http://www.w3.org/1999/xhtml">
 		
 		<p>
-			The <code>relpipe-tr-guile</code> is capable to process multiple relations in a single pass.
+			The <code>relpipe-tr-scheme</code> is capable to process multiple relations in a single pass.
 			So we can filter some relations and let others flow unaffected through this pipeline step.
 		</p>
 
@@ -21,9 +21,9 @@
 # put them together in a single stream function:
 sample-data() { r1; r2; r3; }
 
-# let them flow through our Guile transformation:
+# let them flow through our Scheme transformation:
 sample-data \
-	| relpipe-tr-guile \
+	| relpipe-tr-scheme \
 		--relation fstab \
 			--where '(or (string= $type "btrfs") (string-prefix? "/mnt/" $mount_point) )' \
 		--relation filesystem \
@@ -74,7 +74,7 @@
 
 
 		<p>
-			In Guile, we have filtered the <code>fstab</code> and <code>filesystem</code> relations
+			In Scheme, we have filtered the <code>fstab</code> and <code>filesystem</code> relations
 			while the <code>seq</code> relation was kept intact.
 		</p>
 		
@@ -85,7 +85,7 @@
 		</p>
 		
 		<p>
-			If we define some variables in the Guile context, they will stay there – so we can pass data across relations.
+			If we define some variables in the Scheme context, they will stay there – so we can pass data across relations.
 			Thus we can do even JOIN, if we really want.
 		</p>