Skip to content

Commit

Permalink
Browse files Browse the repository at this point in the history
Fix typos.
  • Loading branch information
Util committed Jan 26, 2015
1 parent f507992 commit e315952
Show file tree
Hide file tree
Showing 10 changed files with 19 additions and 19 deletions.
2 changes: 1 addition & 1 deletion S03-operators.pod
Expand Up @@ -163,7 +163,7 @@ Array composer
Provides list context inside. (Technically, it really provides a
"semilist" context, which is a semicolon-separated list of statements,
each of which is interpreted in list context; if there is only one
statement, it makes a 1-dimensional arry, but if there are more, it
statement, it makes a 1-dimensional array, but if there are more, it
makes a 2-dimensional array instead.)

=item *
Expand Down
2 changes: 1 addition & 1 deletion S04-control.pod
Expand Up @@ -492,7 +492,7 @@ That is,

loop {...}

is equivalent to the Cish idiom:
is equivalent to the C-ish idiom:

loop (;;) {...}

Expand Down
2 changes: 1 addition & 1 deletion S15-unicode.pod
Expand Up @@ -82,7 +82,7 @@ Form Grapheme. It's a Perl 6-invented character representation, designed to deal
with un-precomposed graphemes properly.
Formally Perl 6 graphemes are defined exactly according to Unicode Grapheme Cluster Boundaries
at level "extended" (in contrast to "taylored" or "legacy"),
at level "extended" (in contrast to "tailored" or "legacy"),
see Unicode Standard Annex #29 UNICODE TEXT SEGMENTATION
L<3 Grapheme Cluster Boundaries|http://www.unicode.org/reports/tr29/tr29-25.html#Grapheme_Cluster_Boundaries>>.
This is the same as the Perl 5 character class
Expand Down
4 changes: 2 additions & 2 deletions S16-io.pod
Expand Up @@ -96,7 +96,7 @@ Note that the C<open()> sub, is just really syntactic sugar for the above:
=head2 $*SPEC

The current system's path semantics are encapsulated in C<$*SPEC> dynamic
variable. It adhers to the C<IO::Spec> interface, and is automatically
variable. It adheres to the C<IO::Spec> interface, and is automatically
initialized for the current environment. But like any dynamic variable,
can be overridden in a scope:

Expand Down Expand Up @@ -426,7 +426,7 @@ has been C<.close>d. The C<.open> method does interact with the file system:
It either returns True, or a C<Failure> with additional information.

The other methods of the C<IO::Handle> class are only valid B<after> the
C<.open> has been called succesfully:
C<.open> has been called successfully:

close close file handle, flush buffers
encoding set/return encoding of file handle
Expand Down
2 changes: 1 addition & 1 deletion S22-package-format.pod
Expand Up @@ -447,7 +447,7 @@ application.

=head3 t

All C<.t> files in this directory, will be tested in alphabatical order,
All C<.t> files in this directory, will be tested in alphabetical order,
possibly in parallel. Any files in this directory will never be installed.

=head3 hooks
Expand Down
2 changes: 1 addition & 1 deletion S24-testing.pod
Expand Up @@ -125,7 +125,7 @@ The C<diag()> function allows specific diagnostic information to be printed
in a TAP-compatible manner on C<$*ERR>. It is usually used when a particular
test has failed to provide information that the test itself did not provide.
Or it can be used to provide visual markers on how the testing of a test-file
is progressing (which can be important when doing stresstesting).
is progressing (which can be important when doing stress testing).

=head2 todo(), skip(), skip_rest()

Expand Down
2 changes: 1 addition & 1 deletion S32-setting-library/Containers.pod
Expand Up @@ -1123,7 +1123,7 @@ encoding instead.
Returns a part of the original buffer, starting from index C<$from> and taking
C<$elems> elements (or to the end of the buffer, if not provided).

The method fails with C<X::OutOfRange> if either C<$from> or C<$elems> are negative. The method also fails if C<$from> is larger than the amount of elemens in the buffer.
The method fails with C<X::OutOfRange> if either C<$from> or C<$elems> are negative. The method also fails if C<$from> is larger than the amount of elements in the buffer.

C<$from> may be specified relative to the end of the string using a WhateverCode:

Expand Down
2 changes: 1 addition & 1 deletion S32-setting-library/IO.pod
Expand Up @@ -257,7 +257,7 @@ the scope of the indicated localized C<$*CWD>. A typical use case:
}
# restored to what it was

Returns C<True> if succesful, or an appropriate C<Failure>, e.g if the
Returns C<True> if successful, or an appropriate C<Failure>, e.g if the
directory does not exist, or is not a directory, or is not readable.

Please note that this directory has B<no> connection with whatever the
Expand Down
2 changes: 1 addition & 1 deletion S32-setting-library/Str.pod
Expand Up @@ -398,7 +398,7 @@ The directives are:
Compatibility:

i a synonym for %d
u a synonum for %d
u a synonym for %d
D a synonym for %d
U a synonym for %u
O a synonym for %o
Expand Down
18 changes: 9 additions & 9 deletions S99-glossary.pod
Expand Up @@ -154,7 +154,7 @@ is a port of Perl 5's Dancer web framework (L<http://perldancer.org/>).

=head2 bare string

A non-quoted alphanumeric string. In Perl 6, only allowd at the left of a L</fat comma>.
A non-quoted alphanumeric string. In Perl 6, only allowed at the left of a L</fat comma>.

=head2 biab

Expand Down Expand Up @@ -193,7 +193,7 @@ L<Value|/value> of type L</Bool>. Apart the class itself, can be either C<True>

A L</context> that forces an L<expression|/Expression> to give a L</boolean> value.
The L</prefix> L</operator>s C<so>, C<not> and their
repective higher L</precedence> C<?> and C<!> forms force a boolean context with C<!> and C<not> doing
respective higher L</precedence> C<?> and C<!> forms force a boolean context with C<!> and C<not> doing
a negation.
The L</predicate> part of a L</control flow> L</statement> forces a boolean context.
A class can define a C<Bool> method to handle the boolean context.
Expand All @@ -204,7 +204,7 @@ of the L</STable> structure.

Starting up a system that uses itself to define, build or compile itself, is a practical exercise on solving the chicken and egg problem.
This phase is called bootstrap. L<Documentation|https://github.com/MoarVM/MoarVM/blob/master/docs/bootstrap.markdown>
about booststrapping the L</6model> of L<MoarVM>
about bootstrapping the L</6model> of L<MoarVM>

=head2 boxing

Expand All @@ -226,7 +226,7 @@ Bounded Serialization.
=head2 Bug report

The way to report problems to the implementors.
For the interpretors themselves, use L</RT>.
For the interpreters themselves, use L</RT>.
It is good practice to include the interpreter L</version> in a bug report.
A short piece of example code that demonstrates the bug without requiring any
further set-up is usually very well received, too - see also L</golfing>
Expand Down Expand Up @@ -407,7 +407,7 @@ Some L</prefix> L</operator>s are used to force the context.

Without control flow statements, a program's execution would be purely sequential.
A control flow statement generally uses a predicate and branches to one of its
subtatements according to the predicate value.
substatements according to the predicate value.

=head2 Control Flow Graph

Expand Down Expand Up @@ -537,7 +537,7 @@ See L</Control Flow Graph>

=head2 DYNAMIC::

A L</pseudo-scope> to access contextutal L</symbol>s in my or any L</caller>'s lexical L</scope>.
A L</pseudo-scope> to access contextual L</symbol>s in my or any L</caller>'s lexical L</scope>.

=head2 dynamic

Expand Down Expand Up @@ -758,7 +758,7 @@ timezones, one contributor's morning is another contributor's evening.
=head2 gorilla/banana problem

"You wanted a banana but what you got was a gorilla holding the banana and the entire jungle."
says Joe Amstrong, Erlang creator, complaining of traditional
says Joe Armstrong, Erlang creator, complaining of traditional
L</OO> inheritance based environment inflexibility.
In non L</dynamic language>s, you can't dynamically add L</attribute>s/L</method>s for an L</object>/L</class> so
you end up shoving everything you may ever need in a deep class hierarchy.
Expand Down Expand Up @@ -1306,7 +1306,7 @@ postcircumfix operator C<[0]> where C<0> is the postcircumfixed subexpression.
The C<< <O(I<...>)> >> construction gives information about an operator that completes the
information provided by its category.
Below C<%conditional> is the category, C<< :reducecheck<ternary> >>, which specifies calling C<.ternary> to
posprocess the L<parse subtree|/parse tree> and C<< :pasttype<if> >> specifies the nqp L</opcode> generated in the
post-process the L<parse subtree|/parse tree> and C<< :pasttype<if> >> specifies the nqp L</opcode> generated in the
L</AST> from the parse subtree.

<O('%conditional, :reducecheck<ternary>, :pasttype<if>')>
Expand Down Expand Up @@ -2084,7 +2084,7 @@ See L<also|http://www.unicode.org/ucd/>.
=head2 Unicode Normalization Form

See L</UAX> L<15|http://unicode.org/reports/tr15/>.
Perl 6 defines an addtional one : L</NFG>.
Perl 6 defines an additional one : L</NFG>.

=head2 unit

Expand Down

0 comments on commit e315952

Please sign in to comment.