Some deprecated warnings were also in the syntax category

[p5sagit/p5-mst-13.2.git] / pod / perldsc.pod

diff --git a/pod/perldsc.pod b/pod/perldsc.pod
index 158322b..623e367 100644 (file)
--- a/pod/perldsc.pod
+++ b/pod/perldsc.pod
@@ -71,8 +71,8 @@ these types of data structures.
 =head1 REFERENCES
 X<reference> X<dereference> X<dereferencing> X<pointer>
 
-The most important thing to understand about all data structures in Perl
--- including multidimensional arrays--is that even though they might
+The most important thing to understand about all data structures in
+Perl--including multidimensional arrays--is that even though they might
 appear otherwise, Perl C<@ARRAY>s and C<%HASH>es are all internally
 one-dimensional.  They can hold only scalar values (meaning a string,
 number, or a reference).  They cannot directly contain other arrays or
@@ -199,7 +199,7 @@ much harder to read:
 Is it the same?  Well, maybe so--and maybe not.  The subtle difference
 is that when you assign something in square brackets, you know for sure
 it's always a brand new reference with a new I<copy> of the data.
-Something else could be going on in this new case with the C<@{$AoA[$i]}}>
+Something else could be going on in this new case with the C<@{$AoA[$i]}>
 dereference on the left-hand-side of the assignment.  It all depends on
 whether C<$AoA[$i]> had been undefined to start with, or whether it
 already contained a reference.  If you had already populated @AoA with