More formal conjectural mention of typed slurpies.

And change example that just happened to use them without any notes
on their semantics.

S06-routines.pod

@@ -1151,6 +1151,9 @@ so you can refer to it within the body.
         # %flag has elements (flag => (a => 1)) and (data => [1,2,3])
         # @data has nothing
 
+[Conjecture: a future Perl 6 version will allow typed slurpy parametrs, which
+will validate the types of the passed arguments.]
+
 =head2 Slurpy block
 
 It's also possible to declare a slurpy block: C<*&block>.  It slurps
@@ -1650,11 +1653,11 @@ lexically scoped subroutine:
 The closure parameter can have its own signature in a type specification written
 with C<:(...)>:
 
-    sub limited_Dog_grep ($count, &block:(Dog), Dog *@list) {...}
+    sub limited_Dog_grep ($count, &block:(Dog), *@list) {...}
 
 and even a return type:
 
-    sub limited_Dog_grep ($count, &block:(Dog --> Bool), Dog *@list) {...}
+    sub limited_Dog_grep ($count, &block:(Dog --> Bool), *@list) {...}
 
 When an argument is passed to a closure parameter that has this kind of
 signature, the argument must be a C<Code> object with a compatible