[README] a number of smallish updates

README

@@ -8,7 +8,7 @@ Language) compilers for Parrot. Rakudo, a Perl 6 compiler, was built on
 top of PCT.
 
 In short, a whole lot of abstractions, and in the bottom of it all, driving
-the parser, sits PGE. Humming along, it does all the daily parsing we now
+the parser, sat PGE. Humming along, it did all the daily parsing we now
 take, more or less, for granted.
 
 Patrick was once caught saying that given the little time he had spent
@@ -22,7 +22,7 @@ GGE, the Glacial Grammar Engine, is a faithful port of PGE from PIR to Perl
 also attempts (though perhaps not too convincingly) to be a drop-in
 replacement for PGE. Most importantly, besides being written in Perl 6
 rather than PIR, it brings one new essential feature to the table: it's
-slower. Much slower. Hence the name.
+slower. Much slower... but still quite cool. Hence the name.
 
 The "albeit not too hard" reservation to the implementation-independence
 stems from the fact that some PIR tricks used by PGE are unavailable in
@@ -33,12 +33,14 @@ just as with all honest Perl 6 code.
 
 The "though perhaps not too convincingly" reservation to GGE attempting to
 be a drop-in replacement for PGE stems from the fact that now that regular
-expressions _are_ in fact available in the Perl 6 language (through PGE),
-it's sometimes too tempting not to use them. Of course, it would be a fun
-challenge in itself to restrict the writing of GGE to a strict subset of
-Perl 6 -- one not using any regexes at all, directly or indirectly -- but
-that is not the kind of fun optimized for in this case. Future teams of
-developers are welcome to optimize for that kind of fun, should they wish.
+expressions _are_ in fact available in the Perl 6 language (through PGE
+in the case of the old-generation Rakudo, or nqp-rx in the case of the
+new-generation Rakudo), it's sometimes too tempting not to use them. Of
+course, it would be a fun challenge in itself to restrict the writing of
+GGE to a strict subset of Perl 6 -- one not using any regexes at all,
+directly or indirectly -- but that is not the kind of fun optimized for in
+this case. Future teams of developers are welcome to optimize for that kind
+of fun, should they wish.
 
 For an overview of the status of the project, see STATUS. For an overview
 of the cool things that could be built with the project as a dependency,