diff -r d4c2968a391f -r d7ae02390fac relpipe-data/examples-in-sql-reading-sql.xml
--- a/relpipe-data/examples-in-sql-reading-sql.xml	Sat Sep 12 13:20:21 2020 +0200
+++ b/relpipe-data/examples-in-sql-reading-sql.xml	Fri Sep 25 14:38:24 2020 +0200
@@ -44,10 +44,10 @@
 		--relation '.*' --drop \
 	| relpipe-out-tabular
 
-# Guile transformation:
+# Scheme transformation:
 cat relpipe-in-sql-1.sql \
 	| relpipe-in-sql \
-	| relpipe-tr-guile \
+	| relpipe-tr-scheme \
 		--relation 'a' --where '(string= $message "Hello,")' \
 		--relation '.*' --drop \
 	| relpipe-out-tabular]]></m:pre>
@@ -68,7 +68,7 @@
 	<p>
 		Actually, the <code>relpipe-in-sql</code> is just a symbolic link to the <code>relpipe-tr-sql</code> 
 		and have the same capabilities (with just bit different default behavior to match general logic of the input filters).
-		So if we do not need special feautres of Guile, AWK or other transformation tool, it is better to stay with SQL (when we already use the SQL module).
+		So if we do not need special feautres of Scheme, AWK or other transformation tool, it is better to stay with SQL (when we already use the SQL module).
 	</p>
 	
 	<p>