diff -r d4c2968a391f -r d7ae02390fac relpipe-data/examples-guile-aggregations.xml
--- a/relpipe-data/examples-guile-aggregations.xml	Sat Sep 12 13:20:21 2020 +0200
+++ b/relpipe-data/examples-guile-aggregations.xml	Fri Sep 25 14:38:24 2020 +0200
@@ -2,15 +2,15 @@
 	xmlns="https://trac.frantovo.cz/xml-web-generator/wiki/xmlns/strana"
 	xmlns:m="https://trac.frantovo.cz/xml-web-generator/wiki/xmlns/makro">
 	
-	<nadpis>Aggregating data with Guile</nadpis>
+	<nadpis>Aggregating data with Scheme</nadpis>
 	<perex>counting records and computing sum</perex>
 	<m:pořadí-příkladu>01700</m:pořadí-příkladu>
 
 	<text xmlns="http://www.w3.org/1999/xhtml">
 		
 		<p>
-			In <code>relpipe-tr-guile</code> we can generate new records – not only modify records from the input.
-			There is <code>--has-more-records</code> option which – if evaluated as true – says: „read one more record from the Guile context and call me again“.
+			In <code>relpipe-tr-scheme</code> we can generate new records – not only modify records from the input.
+			There is <code>--has-more-records</code> option which – if evaluated as true – says: „read one more record from the Scheme context and call me again“.
 			We can also suppress all original records by <code>--where '#f'</code>.
 			And we can also change the structure of the relation (see previous examples).
 			Thus we can iterate through a relation but completely replace its structure and content.
@@ -49,7 +49,7 @@
 		</p>
 		
 		<p>
-			One day, there might also be a translator that parses SQL code and generates Guile code,
+			One day, there might also be a translator that parses SQL code and generates Scheme code,
 			so we could have advantages of both worlds
 			a) concise and declarative syntax of SQL and 
 			b) streaming – which means no need for putting all the data in the RAM or on the disk.