Fix some "an" usage

Author: coke

doc/Language/5to6-perlfunc.rakudoc

@@ -933,7 +933,7 @@ Replaced by C<chars>, typically used as a method (C<$string.chars>), but
 also works as a function.
 
 The Raku ecosystem has a module L<C<P5length>|https://raku.land/zef:lizmat/P5length>
-which exports an C<length> function that mimics the original Perl behavior
+which exports a C<length> function that mimics the original Perl behavior
 as much as possible.
 
 =head2 X<__LINE__|Other languages,__LINE__ - perlfunc>

doc/Language/contexts.rakudoc

@@ -93,7 +93,7 @@ say +"  \n ";     # OUTPUT: «0␤»
 Whitespace in any quantity will be converted to 0, as is shown in the last
 statement. In the case of I<listy> things, the numeric value will be in general
 equivalent to C<.elems>; in some cases, like
-L<Thread|/routine/Numeric#(Thread)_method_Numeric>, it will return an unique
+L<Thread|/routine/Numeric#(Thread)_method_Numeric>, it will return a unique
 thread identifier.
 
 =head1 X<String|Language,string context>

doc/Language/glossary.rakudoc

@@ -306,7 +306,7 @@ sufficiently different from its arguments that op= makes little sense.
 =head1 X<Exegesis|Reference,Exegesis>
 
 A document originally written by L<TheDamian|#TheDamian>, in which he tried to explain
-the L<Apocalypses|#Apocalypse> to the common (wo)man. Now only kept as an
+the L<Apocalypses|#Apocalypse> to the common (wo)man. Now only kept as a
 historical document for reference. See also L<Synopsis|#Synopsis>.
 
 X<|Reference,forward declaration>

doc/Language/hashmap.rakudoc

@@ -185,8 +185,8 @@ or
 
 Please note that curly braces are used only in the case that we are not
 assigning it to a C<%>-sigiled variable; in case we use it for a C<%>-sigiled
-variable we will get an C<Potential difficulties:␤ Useless use of hash
-composer on right side of hash assignment; did you mean := instead?> error. As
+variable we will get an error of C<Potential difficulties:␤ Useless use of hash
+composer on right side of hash assignment; did you mean := instead?>. As
 this error indicates, however, we can use curly braces as long as we use also
 binding:
 

doc/Language/objects.rakudoc

@@ -262,7 +262,7 @@ my $vacation = Journey.new(
 # Use an accessor; this outputs Sweden.
 say $vacation.origin;
 
-# Use an rw accessor to change the value.
+# Use a rw accessor to change the value.
 $vacation.notes = 'Pack hiking gear and sunglasses!';
 =end code
 

doc/Language/statement-prefixes.rakudoc

@@ -105,7 +105,7 @@ say $!; # OUTPUT: «Cannot pop from an empty Array␤..»
 
 =head2 X<C<do>|Syntax,do (statement prefix)>
 
-C<do> can be used as an statement prefix to disambiguate the statement they
+C<do> can be used as a statement prefix to disambiguate the statement they
 precede; this is needed, for instance, if you want to assign the result of a
 C<for> statement. A bare C<for> will fail, but this will work:
 

doc/Language/subscripts.rakudoc

@@ -915,7 +915,7 @@ C<AT-POS> (which would have to create and return a potentially expensive
 container object).
 
 Note that implementing C<ASSIGN-POS> does I<not> relieve you from making
-C<AT-POS> an C<rw> method though, because less trivial
+C<AT-POS> a C<rw> method though, because less trivial
 assignments/modifications such as C<@numbers[5]++> will still use
 C<AT-POS>.
 
@@ -1098,7 +1098,7 @@ C<AT-KEY> (which would have to create and return a potentially expensive
 container object).
 
 Note that implementing C<ASSIGN-KEY> does I<not> relieve you from making
-C<AT-KEY> an C<rw> method though, because less trivial
+C<AT-KEY> a C<rw> method though, because less trivial
 assignments/modifications such as C<<%age<Claire>++>> will still use
 C<AT-KEY>.
 

doc/Type/Allomorph.rakudoc

@@ -261,7 +261,7 @@ uniquely identifies the object.
 
 Compare two C<Allomorph> objects.  The comparison is done on the
 L<C<Numeric>|/type/Numeric> value first and then on the L<C<Str>|/type/Str> value. If you want to
-compare in a different order then you would coerce to an L<C<Numeric>|/type/Numeric>
+compare in a different order then you would coerce to a L<C<Numeric>|/type/Numeric>
 or L<C<Str>|/type/Str> value first:
 
     my $f = IntStr.new(42, "smaller");

doc/Type/Compiler.rakudoc

@@ -21,7 +21,7 @@ and the C<$*PERL> variables.
 
 =head2 method id
 
-Returns an unique identifier, a long hexadecimal string
+Returns a unique identifier, a long hexadecimal string
 
 =head2 method release
 

doc/Type/DateTime.rakudoc

@@ -62,7 +62,7 @@ is from the components (year, month, day, hour, ...) separately. Another is to
 pass a L<C<Date>|/type/Date> object for the date component, and specify the time
 component-wise. Yet another is to obtain the time from an
 L<C<Instant>|/type/Instant>, and only supply the time zone and formatter. Or
-instead of an Instant you can supply an L<C<Numeric>|/type/Numeric> as a UNIX timestamp.
+instead of an Instant you can supply a L<C<Numeric>|/type/Numeric> as a UNIX timestamp.
 
 You can also supply a L<C<Str>|/type/Str> formatted in ISO 8601 timestamp
 notation or as a full L<RFC 3339|https://tools.ietf.org/html/rfc3339>

doc/Type/IO/Socket/INET.rakudoc

@@ -44,7 +44,7 @@ say $conn.recv;
 $conn.close;
 =end code
 
-Please bear in mind that this is a synchronous connection; an attempt by any of the nodes to write without the other reading will produce an C<Could not receive data from socket: Connection reset by peer> error.
+Please bear in mind that this is a synchronous connection; an attempt by any of the nodes to write without the other reading will produce the error C<Could not receive data from socket: Connection reset by peer>.
 
 =head1 Methods
 

doc/Type/Int.rakudoc

@@ -50,7 +50,7 @@ These notations allow you to use variables, too:
     multi method new(int   \value --> Int:D)
 
 The first form will throw an exception; the second and third form will create
- an new Int from the actual integer value contained in the variable.
+ a new Int from the actual integer value contained in the variable.
 
 =head2 method Str
 

doc/Type/Map.rakudoc

@@ -90,7 +90,7 @@ Returns the number of pairs stored in the Map.
     multi method ACCEPTS(Map:D: Regex      $topic)
     multi method ACCEPTS(Map:D: Any        $topic)
 
-Used in smartmatching if the right-hand side is an C<Map>.
+Used in smartmatching if the right-hand side is a C<Map>.
 
 If the topic is list-like (L<C<Positional>|/type/Positional>), returns True if
 any of the list elements exist as a key in the Map.

doc/Type/Metamodel/Mixins.rakudoc

@@ -57,7 +57,7 @@ This makes it possible for mixins to not only have composable methods,
 but composable state as well. Using this feature, the example above can
 be rewritten so billboards can be vandalized more than once without
 needing to generate more mixins by making C<Billboard::Vandalism>'s
-C<$vandalism> named parameter an L<rw|/type/Attribute#trait_is_rw>
+C<$vandalism> named parameter a L<rw|/type/Attribute#trait_is_rw>
 mixin attribute instead:
 
 =begin code

doc/Type/Range.rakudoc

@@ -431,7 +431,7 @@ type of the instance (C<Range>) and the C<min> and C<max> attributes:
     multi infix:<+>(Range:D \r, Real:D \v)
     multi infix:<+>(Real:D \v, Range:D \r)
 
-Takes an L<C<Real>|/type/Real> and adds that number to both
+Takes a L<C<Real>|/type/Real> and adds that number to both
 boundaries of the C<Range> object. Be careful with
 the use of parenthesis.
 
@@ -442,7 +442,7 @@ the use of parenthesis.
 
     multi infix:<->(Range:D \r, Real:D \v)
 
-Takes an L<C<Real>|/type/Real> and subtract that number to both
+Takes a L<C<Real>|/type/Real> and subtract that number to both
 boundaries of the C<Range> object. Be careful with
 the use of parenthesis.
 
@@ -454,7 +454,7 @@ the use of parenthesis.
     multi infix:<*>(Range:D \r, Real:D \v)
     multi infix:<*>(Real:D \v, Range:D \r)
 
-Takes an L<C<Real>|/type/Real> and multiply both boundaries
+Takes a L<C<Real>|/type/Real> and multiply both boundaries
 of the C<Range> object by that number.
 
     say (1..2) * 2; # OUTPUT: «2..4␤»
@@ -463,7 +463,7 @@ of the C<Range> object by that number.
 
     multi infix:</>(Range:D \r, Real:D \v)
 
-Takes an L<C<Real>|/type/Real> and divide both boundaries
+Takes a L<C<Real>|/type/Real> and divide both boundaries
 of the C<Range> object by that number.
 
     say (2..4) / 2; # OUTPUT: «1..2␤»

doc/Type/independent-routines.rakudoc

@@ -1272,7 +1272,7 @@ type, it should behave as if its signature was just:
 Autovivification to an instance of the new type is L<provided by the default
 base class|/routine/append#(Any)_method_append> if the new type implements the
 L<C<Positional>|/type/Positional> role. If the new type is not L<C<Positional>|/type/Positional>, autovivification can
-be supported by an adding a multi method with a signature like
+be supported by adding a multi method with a signature like
 
     multi method push(::?CLASS:U: **@values is raw --> ::?CLASS:D)
 

writing-docs/EXAMPLES.md

@@ -39,7 +39,7 @@ For pedagogical reasons, it's
 OK to break what would otherwise be a large block of code into smaller
 chunks and discuss each one separately - we still want to do our best
 to compile these individual chunks. However, avoid this practice across
-methods on a Type/ page, which an be split up to show only a single method.
+methods on a Type/ page, which can be split up to show only a single method.
 Even on a Language/ page, avoid continuing an example for more than a
 page or so.
 

xt/rakudoc-types.rakutest

@@ -112,7 +112,7 @@ sub is-valid-type($node, $parent, $file) {
         pass "L<{render-node($node)}|$meta>";
     } else {
         if $meta.starts-with('/routine/') {
-            # Is this pointing to an routine page? /routine is generated, so we cannot verify
+            # Is this pointing to a routine page? /routine is generated, so we cannot verify
             # the existence of an actual file; trust if present.
             # Should be caught on error-report in site build
             pass "L<{render-node($node)}|$meta> - routine";