#60364 [PATCH] pod fixes: L<draft/pdd19_pid.pod>, typos, syntax

Courtesy of Brad Bowman. git-svn-id: https://svn.parrot.org/parrot/trunk@32378 d31e2699-5ff4-0310-a27c-f18f2fbe73fe
ashgti · Nov 6, 2008 · 088256f · 088256f
1 parent de3b145
commit 088256f
Show file tree

Hide file tree

Showing 7 changed files with 14 additions and 12 deletions.
diff --git a/CREDITS b/CREDITS
@@ -129,6 +129,9 @@ N: Bob Wilkinson
 D: Numerous document typos.
 E: bob@fourtheye.org
 
+N: Brad Bowman
+D: pod fixes
+
 N: Brad Gilbert
 D: Add test for sysinfo op.
 E: b2gills@gmail.com

diff --git a/docs/art/pp001-intro.pod b/docs/art/pp001-intro.pod
@@ -88,7 +88,7 @@ executing this subroutine. By the way, I could use C<.sub foo :main> and
 Parrot will use the C<foo> subroutine as the main body of the program.
 The actual name of the subroutine does not matter as long as it has the
 C<:main> pragma.  The full set of pragmas are defined in
-L<docs/pdds/draft/pdd19_pir.pod>.
+L<docs/pdds/pdd19_pir.pod>.
 
 Before going into more details about subroutines and calling
 conventions, let's compare some PIR syntax to the equivalent PASM.
@@ -297,7 +297,7 @@ Alberto Simões
 
 =over 4
 
-* Jonathan Scott Duff
+=item * Jonathan Scott Duff
 
 =back
 

diff --git a/docs/compiler_faq.pod b/docs/compiler_faq.pod
@@ -50,7 +50,7 @@ If the function name might collide with a Parrot opcode, quote it:
    i = 'new'(42)
 
 You can also use the full PCC for these calls. See
-L<docs/draft/pdd19_pir.pod/Parameter Passing and Getting Flags> and other
+L<docs/pdd19_pir.pod/Parameter Passing and Getting Flags> and other
 quesitons below for more information.
 
 =head2 How do I generate a method call in PIR?
@@ -179,10 +179,9 @@ Use the C<:optional> and C<:opt_flag> pragmas:
 
 =head2 How do I create nested subroutines?
 
-Please refer to L<docs/pdds/pdd20_lexical_vars.pod> for details: look for
-C<:outer>.
-
-XXX Fix L syntax here.
+Please refer to 
+L<docs/pdds/pdd20_lexical_vars.pod/Nested Subroutines Have Outies; the ":outer" attribute> 
+for details.
 
 =head1 Variables
 

diff --git a/docs/faq.pod b/docs/faq.pod
@@ -33,7 +33,7 @@ Yes.
 
 Although Parrot is currently still under development, Parrot has been usable for
 a long time. The primary way to use Parrot is to write Parrot Intermediate
-Representation (PIR), described in L<PDD19|docs/pdds/draft/pdd19_pir.pod>.
+Representation (PIR), described in L<PDD19|docs/pdds/pdd19_pir.pod>.
 PIR is a high-level assembly language. See the L<examples> directory.
 
 =head2 When can I expect to use Parrot with a I<real> programming language?

diff --git a/docs/pct/gettingstarted.pod b/docs/pct/gettingstarted.pod
@@ -203,7 +203,7 @@ implementation of a simple yet non-trivial language.
 
 =item * L<docs/pdds/pdd26_past.pod>
 
-=item * L<docs/pdds/draft/pdd19_pir.pod>
+=item * L<docs/pdds/pdd19_pir.pod>
 
 =item * F<http://dev.perl.org/perl6/doc/design/syn/S05.html>
 

diff --git a/docs/pmc/subs.pod b/docs/pmc/subs.pod
@@ -132,7 +132,7 @@ subs, B<:init> subs are also run when compiling from memory.  B<:load> subs
 are run only in any source or bytecode files loaded subsequently.
 
 These markers are called "pragmas", and are defined fully in
-L<docs/pdds/draft/pdd19_pir.pod>.  The following table summarizes the behavior
+L<docs/pdds/pdd19_pir.pod>.  The following table summarizes the behavior
 of the five pragmas that cause Parrot to run a sub implicitly:
 
                 ------ Executed when --------
@@ -309,7 +309,7 @@ F<t/pmc/sub.t>
 =head1 SEE ALSO
 
 F<docs/pdds/pdd03_calling_conventions.pod>
-F<docs/pdds/draft/pdd19_pir.pod>
+F<docs/pdds/pdd19_pir.pod>
 
 =head1 AUTHOR
 

diff --git a/docs/stm/howto.pod b/docs/stm/howto.pod
@@ -93,7 +93,7 @@ STMLog PMC type.
 =head2 Starting and ending transactions
 
 The runtime library C<transaction> runs a supplied subroutine (with
-optional supplied arugments) in a separate transaction commiting the
+optional supplied arguments) in a separate transaction commiting the
 result. For example, (Perlish) pseudocode for inserting at the beginning
 of a linked list might look like this: