summaryrefslogtreecommitdiff
path: root/pod/perlpodspec.pod
diff options
context:
space:
mode:
authorDavid Landgren <david@landgren.net>2007-09-28 22:42:56 +0200
committerRafael Garcia-Suarez <rgarciasuarez@gmail.com>2007-10-04 14:28:34 +0000
commit353c650532037e4006fbdb2176350717f320f7c3 (patch)
treed168025606b4a4daf862755b087c4ba3b29e97b5 /pod/perlpodspec.pod
parent94fcd414575e04d8b809003ba7bca1216090abff (diff)
downloadperl-353c650532037e4006fbdb2176350717f320f7c3.tar.gz
POD cleanups
Message-ID: <46FD4B30.9070802@landgren.net> p4raw-id: //depot/perl@32026
Diffstat (limited to 'pod/perlpodspec.pod')
-rw-r--r--pod/perlpodspec.pod8
1 files changed, 4 insertions, 4 deletions
diff --git a/pod/perlpodspec.pod b/pod/perlpodspec.pod
index c33b68f0cf..5e38e2c184 100644
--- a/pod/perlpodspec.pod
+++ b/pod/perlpodspec.pod
@@ -65,7 +65,7 @@ directly formatting it). A B<Pod formatter> (or B<Pod translator>)
is a module or program that converts Pod to some other format (HTML,
plaintext, TeX, PostScript, RTF). A B<Pod processor> might be a
formatter or translator, or might be a program that does something
-else with the Pod (like wordcounting it, scanning for index points,
+else with the Pod (like counting words, scanning for index points,
etc.).
Pod content is contained in B<Pod blocks>. A Pod block starts with a
@@ -724,7 +724,7 @@ period-space-space or period-newline sequences).
Pod parsers should not, by default, try to coerce apostrophe (') and
quote (") into smart quotes (little 9's, 66's, 99's, etc), nor try to
turn backtick (`) into anything else but a single backtick character
-(distinct from an openquote character!), nor "--" into anything but
+(distinct from an open quote character!), nor "--" into anything but
two minus signs. They I<must never> do any of those things to text
in CE<lt>...> formatting codes, and never I<ever> to text in verbatim
paragraphs.
@@ -959,7 +959,7 @@ for idiosyncratic mappings of Unicode-to-I<my_escapes>.
=item *
-It is up to individual Pod formatter to display good judgment when
+It is up to individual Pod formatter to display good judgement when
confronted with an unrenderable character (which is distinct from an
unknown EE<lt>thing> sequence that the parser couldn't resolve to
anything, renderable or not). It is good practice to map Latin letters
@@ -1541,7 +1541,7 @@ probably want to format it like so:
Ut Enim
-But (for the forseeable future), Pod does not provide any way for Pod
+But (for the foreseeable future), Pod does not provide any way for Pod
authors to distinguish which grouping is meant by the above
"=item"-cluster structure. So formatters should format it like so: