More POD fixes and typos

p4raw-id: //depot/perl@15889

diff --git a/pod/perlunicode.pod b/pod/perlunicode.pod
index 66ed3d3..40b4916 100644 (file)
--- a/pod/perlunicode.pod
+++ b/pod/perlunicode.pod
@@ -274,7 +274,7 @@ written right to left.
 =head2 Scripts
 
 The scripts available via C<\p{...}> and C<\P{...}>, for example
-C<\p{Latin}> or \p{Cyrillic>, are as follows:
+C<\p{Latin}> or C<\p{Cyrillic}>, are as follows:
 
     Arabic
     Armenian
@@ -363,8 +363,8 @@ and further derived properties:
     ID_Continue     ID_Start + Mn + Mc + Nd + Pc
 
     Any             Any character
-    Assigned        Any non-Cn character (i.e. synonym for C<\P{Cn}>)
-    Unassigned      Synonym for C<\p{Cn}>
+    Assigned        Any non-Cn character (i.e. synonym for \P{Cn})
+    Unassigned      Synonym for \p{Cn}
     Common          Any character (or unassigned code point)
                     not explicitly assigned to a script
 
@@ -880,7 +880,7 @@ not think that LATIN SMALL LETTER ETH is a letter (unless you happen
 to speak Icelandic), but Unicode does.
 
 As discussed elsewhere, Perl tries to stand one leg (two legs, being
-a quadrupled camel?) in two worlds: the old world of byte and the new
+a quadruped camel?) in two worlds: the old world of byte and the new
 world of characters, upgrading from bytes to characters when necessary.
 If your legacy code is not explicitly using Unicode, no automatic
 switchover to characters should happen, and characters shouldn't get
@@ -1071,7 +1071,7 @@ perl's internal representation like so:
 Sometimes, when the extension does not convert data but just stores
 and retrieves them, you will be in a position to use the otherwise
 dangerous Encode::_utf8_on() function. Let's say the popular
-<Foo::Bar> extension, written in C, provides a C<param> method that
+C<Foo::Bar> extension, written in C, provides a C<param> method that
 lets you store and retrieve data according to these prototypes:
 
     $self->param($name, $value);            # set a scalar
@@ -1095,7 +1095,7 @@ derived class with such a C<param> method:
 
 Some extensions provide filters on data entry/exit points, as e.g.
 DB_File::filter_store_key and family. Watch out for such filters in
-the documentations of your extensions, they can make the transition to
+the documentation of your extensions, they can make the transition to
 Unicode data much easier.
 
 =head2 speed