[svn:parrot] r37128 - in trunk/docs: . book pct pdds
Util at svn.parrot.org
Util at svn.parrot.org
Thu Mar 5 16:58:06 UTC 2009
Author: Util
Date: Thu Mar 5 16:58:05 2009
New Revision: 37128
URL: https://trac.parrot.org/parrot/changeset/37128
Log:
[docs] Typos
Modified:
trunk/docs/book/ch08_architecture.pod
trunk/docs/parrotbyte.pod
trunk/docs/pct/past_building_blocks.pod
trunk/docs/pct/pct_optable_guide.pod
trunk/docs/pdds/pdd13_bytecode.pod
Modified: trunk/docs/book/ch08_architecture.pod
==============================================================================
--- trunk/docs/book/ch08_architecture.pod Thu Mar 5 16:49:42 2009 (r37127)
+++ trunk/docs/book/ch08_architecture.pod Thu Mar 5 16:58:05 2009 (r37128)
@@ -686,7 +686,7 @@
memory, or manipulate thread or global state safely. Event handlers
can even acquire locks if they need to. Even though event handlers have
all these capabilities, it doesn't mean they should be used with
-impugnity. An event handler blocking on a lock can easily deadlock a
+impunity. An event handler blocking on a lock can easily deadlock a
program that hasn't been properly designed. Parrot gives you plenty of
rope, it's up to the programmer not to trip on it.
Modified: trunk/docs/parrotbyte.pod
==============================================================================
--- trunk/docs/parrotbyte.pod Thu Mar 5 16:49:42 2009 (r37127)
+++ trunk/docs/parrotbyte.pod Thu Mar 5 16:58:05 2009 (r37128)
@@ -315,7 +315,7 @@
+----------+----------+----------+----------+
The number of arguments and the type of each argument can usually be determined
-by consulting Parrot::Opcode, or programatically by obtaining the op_info_t
+by consulting Parrot::Opcode, or programmatically by obtaining the op_info_t
structure for the opcode in question.
There are currently 4 opcodes that can take a variable number of arguments:
Modified: trunk/docs/pct/past_building_blocks.pod
==============================================================================
--- trunk/docs/pct/past_building_blocks.pod Thu Mar 5 16:49:42 2009 (r37127)
+++ trunk/docs/pct/past_building_blocks.pod Thu Mar 5 16:58:05 2009 (r37128)
@@ -202,7 +202,7 @@
=head2 Typical use
Nodes of type PAST::Var are used to represent variables and their declarations
-(based on the C<:isdecl> flag, see below). Whereever a variable is used in the
+(based on the C<:isdecl> flag, see below). Wherever a variable is used in the
source language, this can be represented by a PAST::Var node.
=head2 Attributes
Modified: trunk/docs/pct/pct_optable_guide.pod
==============================================================================
--- trunk/docs/pct/pct_optable_guide.pod Thu Mar 5 16:49:42 2009 (r37127)
+++ trunk/docs/pct/pct_optable_guide.pod Thu Mar 5 16:58:05 2009 (r37128)
@@ -37,7 +37,7 @@
}
-An expresson such as C<1 + 2> will result in a parse tree like this:
+An expression such as C<1 + 2> will result in a parse tree like this:
expression
mulexpr
Modified: trunk/docs/pdds/pdd13_bytecode.pod
==============================================================================
--- trunk/docs/pdds/pdd13_bytecode.pod Thu Mar 5 16:49:42 2009 (r37127)
+++ trunk/docs/pdds/pdd13_bytecode.pod Thu Mar 5 16:58:05 2009 (r37128)
@@ -6,7 +6,7 @@
=head2 Abstract
This PDD describes the file format for Parrot Bytecode (PBC) files and the
-interface through which they may be manipulated programatically.
+interface through which they may be manipulated programmatically.
=head2 Version
@@ -742,7 +742,7 @@
=head3 Packfile PMCs
A packfile can be represented in memory by Parrot as a tree of PMCs. These
-provide a programatic way to construct and walk packfiles, both for the
+provide a programmatic way to construct and walk packfiles, both for the
Parrot internals and from programs running on the Parrot VM.
{{ TODO... ManagedStruct and UnmanagedStruct may be helpful for these;
More information about the parrot-commits
mailing list