* docs/pdds/draft/pdd06_pasm.pod:

   + Remove refs to old pad ops.
* docs/pdds/pdd03_calling_conventions.pod:
   + Remove unmatched ")".


git-svn-id: https://svn.parrot.org/parrot/trunk@26829 d31e2699-5ff4-0310-a27c-f18f2fbe73fe

docs/pdds/draft/pdd06_pasm.pod

@@ -573,37 +573,12 @@ the inline POD documentation in F<ops/var.ops>.
 
 =over 4
 
-=item new_pad ix
-
-=item new_pad Px, iy
-
-=item push_pad Px
-
-=item pop_pad
-
-=item pop_pad Px
-
-=item peek_pad Px
-
-Instructions for creating scratchpads and manipulating the lexical stack.
-
 =item store_lex sx, Py
 
-=item store_lex ix, sy, Pz
-
-=item store_lex ix, iy, Pz
-
 =item find_lex Px, sy
 
-=item find_lex Px, iy, sz
-
-=item find_lex Px, iy, iz
-
-Instructions for storing in, and retrieving from the scratchpad currently at
-the top of the lexical stack.  For each of these operations there is an
-equivalent form that uses keyed versions of the set instruction. The keyed
-variants require that a scratchpad be specified rather than implicitly
-operating on the scratchpad on the top of the stack.
+Instructions for storing in, and retrieving from, the scratchpad associated
+with the current context.
 
 =item find_global Px, sy, sz
 

docs/pdds/pdd03_calling_conventions.pod

@@ -54,7 +54,7 @@ C<get_results>, for accepting return values.
 FAQ: Given Parrot's internal use of continuation-passing style ["CPS"], it
 would be possible to use one pair of opcodes for both call and return, since
 under CPS returns I<are> calls.  And perhaps someday we will have only two
-opcodes.  But for now, certain efficiency hacks are easier with four opcodes.)
+opcodes.  But for now, certain efficiency hacks are easier with four opcodes.
 
 The common syntax of these opcodes is: