Require "no strict;" to enable lax mode

literals or bare "v6;" do not seem to be explicit enough for our current
taste (and -e still defaults to lax mode)

S01-overview.pod

@@ -9,8 +9,8 @@ Synopsis 1: Overview
 
     Created: 10 Aug 2004
 
-    Last Modified: 2 Mar 2012
-    Version: 9
+    Last Modified: 11 Feb 2015
+    Version: 10
 
 This document originally summarized Apocalypse 1, which covers the
 initial design concept.  That original summary may be found below
@@ -105,7 +105,6 @@ code in some other way, such as by:
 
     #!/usr/bin/perl6
     use v6.0;
-    v6;
 
 Also, a file with a C<.p6> extension may be taken as indicative,
 as may any other extension containing the digit C<6>, such as C<p6l>
@@ -147,7 +146,8 @@ a bare version number:
     perl -e '$x = 1'
 
     #!/usr/bin/perl
-    v6; $x = 1;
+    no strict;
+    $x = 1;
 
 =item *
 

S11-modules.pod

@@ -8,8 +8,8 @@ Synopsis 11: Compilation Units
 
     Created: 27 Oct 2004
 
-    Last Modified: 15 Mar 2014
-    Version: 42
+    Last Modified: 11 Feb 2015
+    Version: 43
 
 =head1 Overview
 
@@ -598,16 +598,10 @@ To lock the semantics to 6.0.0, say one of:
     use v6.0.0;
 
 In any of those cases, strictures and warnings are the default
-in your main program.  But if you start your program with a bare
-version number or other literal:
+in your main program. To start it in I<lax> mode, start it with
 
-    v6.0.0;
-    v6;
-    6;
-    "Coolness, dude!";
+    no strict;
 
-it runs Perl 6 in I<lax> mode, without strictures or warnings, since obviously
-a bare literal in a sink (void) context I<ought> to have produced a "Useless use of..." warning.
 (Invoking perl with C<-e '6;'> has the same effect.)
 
 In the other direction, to inline Perl 5 code inside a Perl 6 program, put