X-Git-Url: http://git.shadowcat.co.uk/gitweb/gitweb.cgi?a=blobdiff_plain;f=pod%2Fperlpod.pod;h=6a578caec355647754ced1d061ee961e98cdf21e;hb=b4793f7f58b137d8b2f6d505d6c77dee2cd8cb25;hp=6a13991437b3c67852fe24b66329adcbb422d8da;hpb=55a864fe4cea1a0586891b83d359ba71e0972da5;p=p5sagit%2Fp5-mst-13.2.git
diff --git a/pod/perlpod.pod b/pod/perlpod.pod
index 6a13991..6a578ca 100644
--- a/pod/perlpod.pod
+++ b/pod/perlpod.pod
@@ -54,7 +54,7 @@ items consistent: either use "=item *" for all of them, to produce bullets,
or use "=item 1.", "=item 2.", etc., to produce numbered lists, or use
"=item foo", "=item bar", etc., i.e., things that looks nothing like bullets
or numbers. If you start with bullets or numbers, stick with them, as many
-formatters use the first "=item" type to decide how to format the list.
+formatters use the first "=item" type to decide how to format the list.
For, begin, and end let you include sections that are not interpreted
as pod text, but passed directly to particular formatters. A formatter
@@ -63,12 +63,12 @@ completely ignored. The directive "=for" specifies that the entire next
paragraph is in the format indicated by the first word after
"=for", like this:
- =for html
+ =for html
This is a raw HTML paragraph
The paired commands "=begin" and "=end" work very similarly to "=for", but instead of only accepting a single paragraph, all text from "=begin" to a -paragraph with a matching "=end" are treated as a particular format. +paragraph with a matching "=end" are treated as a particular format. Here are some examples of how to use these: @@ -132,7 +132,7 @@ here and in commands: I literal code
+ C literal code
L A link (cross reference) to name
L manual page
L item in manual page
@@ -142,7 +142,7 @@ here and in commands:
L"sec"> ditto
F Used for filenames
X An index entry
- ZEE A zero-width character
+ Z<> A zero-width character
E A named character (very similar to HTML escapes)
E A literal <
E A literal >