more s/async/start/ tweaks

Author: TimToady

S04-control.pod

@@ -902,7 +902,7 @@ lexical scope looks like at run time.  That's okay.)
 X<do>
 
 Other similar forms, where a keyword is followed by code to be controlled by it, may also take bare statements,
-including C<try>, C<once>, C<quietly>, C<contend>, C<async>, C<lazy>, and C<sink>.  These constructs
+including C<try>, C<once>, C<quietly>, C<contend>, C<start>, C<lazy>, and C<sink>.  These constructs
 establish a dynamic scope without necessarily establishing a lexical
 scope.  (You can always establish a lexical scope explicitly by using
 the block form of argument.)  As statement introducers, all these
@@ -1451,7 +1451,7 @@ in lowercase.  They parse the same as phasers:
         try {...}*      evaluate and trap exceptions (implies 'use fatal')
     quietly {...}*      evaluate and suppress warnings
     contend {...}*      attempt side effects under STM
-      async {...}       start a subthread
+      start {...}       start computation of a promised result
 
 Constructs marked with a C<*> have a run-time value, and if evaluated
 earlier than their surrounding expression, they simply save their

S06-routines.pod

@@ -43,7 +43,7 @@ because it is part of a conditional operator, or a default initialization of
 an attribute.  It has no scope of its own, so any new variables defined in
 a thunk, will leak to the scope that they're in.  Note however that
 any and all lazy constructs, whether block-based or thunk-based,
-such as gather or async or C<< ==> >> should declare their own C<$/>
+such as gather or start or C<< ==> >> should declare their own C<$/>
 and C<$!> so that the user's values for those variables cannot be
 clobbered asynchronously.
 

S17-concurrency.pod

@@ -13,8 +13,8 @@ RE-DRAFT: Synopsis 17: Concurrency
 
     Created: 3 Nov 2013
 
-    Last Modified: 3 Nov 2013
-    Version: 1
+    Last Modified: 4 Nov 2013
+    Version: 2
 
 This synopsis is based around the concurrency primitives and tools currently
 being implemented in Rakudo on the JVM.  It covers both things that are
@@ -288,7 +288,7 @@ are kept. If the first promise to produce a result is instead broken, then
 the resulting C<Promise> is also broken. The cause is passed along. When the
 C<Promise> is kept, it has a C<True> result.
 
-    my $calc     = async { ... }
+    my $calc     = start { ... }
     my $timeout  = Promise.alarm(10);
     my $timecalc = Promise.anyof($calc, $timeout);