Changes to reflect reviews

Author: finanalyst

doc/Language/compilation.pod6

@@ -1,6 +1,6 @@
 =begin pod :kind("Language") :subkind("Language") :category("tutorial")
 
-=TITLE Compilation
+=TITLE CompUnits and where to find them
 
 =SUBTITLE How and when Raku modules are compiled, where they are stored, and how to access them in compiled form.
 
@@ -193,10 +193,14 @@ Such a filter is given by way of a C<CompUnit::DependencySpecification> object w
 
 When looking through candidates, the Installation repository will smart match a module's long name against this
 DependencySpecification or rather the individual fields against the individual matchers.
-Thus a matcher may be some concrete value, a version range or even a regex.
+Thus a matcher may be some concrete value, a version range or even a regex (though an arbitrary regex, such as C<.*>,
+would not produce a useful result, but something like C<3.20.1+> will only find candidates higher than 3.20.1).
+
+Loading the meta data of all installed distributions would be prohibitively slow. The current immplementation of
+the C<Raku> framework uses
+the file system as a kind of database. However, another implementation may use another strategy. The following description
+shows how one implementation works and is included here to illustrate what is happening.
 
-Loading the meta data of all installed distributions would be prohibitively slow.
-Instead, we use the file system as a kind of database.
 We store not only a distribution's files but also create indices for speeding up lookups.
 One of these indices comes in the form of directories named after the short-name of installed modules.
 However most of the file systems in common use today cannot handle Unicode names, so we cannot just use