Author: vamped
Date: 2010-03-13 12:07:29 +0100 (Sat, 13 Mar 2010)
New Revision: 30059

Modified:
   docs/Perl6/Spec/S29-functions.pod
   docs/Perl6/Spec/S32-setting-library/Containers.pod
Log:
changed "scalar context" into "item context" as per S02

Modified: docs/Perl6/Spec/S29-functions.pod
===================================================================
--- docs/Perl6/Spec/S29-functions.pod   2010-03-13 00:47:56 UTC (rev 30058)
+++ docs/Perl6/Spec/S29-functions.pod   2010-03-13 11:07:29 UTC (rev 30059)
@@ -317,9 +317,9 @@
 would be downgraded in context.
 
 C<ord> goes the other direction; it takes a string value and returns
-character values as integers.  In a scalar context, the return value
+character values as integers.  In item context, the return value
 is the just the integer value of the first character in the string. In
-a list context, the return value is the list of integers representing
+list context, the return value is the list of integers representing
 the entire string.  The definition of character is pragma dependent.
 Normally it's a grapheme id, but under codepoints or bytes scopes,
 the string is coerced to the appropriate low-level view and interpreted

Modified: docs/Perl6/Spec/S32-setting-library/Containers.pod
===================================================================
--- docs/Perl6/Spec/S32-setting-library/Containers.pod  2010-03-13 00:47:56 UTC 
(rev 30058)
+++ docs/Perl6/Spec/S32-setting-library/Containers.pod  2010-03-13 11:07:29 UTC 
(rev 30059)
@@ -582,7 +582,7 @@
 dimension, and works with Array References.
 
 C<splice> returns a C<Parcel> of the deleted elements, which behaves as
-expected in either list or scalar context.
+expected in either list or item context.
 
 
 =item unshift

Reply via email to