diff options
Diffstat (limited to 'lib/Pod')
-rw-r--r-- | lib/Pod/Checker.pm | 2 | ||||
-rw-r--r-- | lib/Pod/Html.pm | 6 | ||||
-rw-r--r-- | lib/Pod/InputObjects.pm | 2 | ||||
-rw-r--r-- | lib/Pod/LaTeX.pm | 2 | ||||
-rw-r--r-- | lib/Pod/Man.pm | 2 | ||||
-rw-r--r-- | lib/Pod/Parser.pm | 6 | ||||
-rw-r--r-- | lib/Pod/Select.pm | 2 |
7 files changed, 11 insertions, 11 deletions
diff --git a/lib/Pod/Checker.pm b/lib/Pod/Checker.pm index b1753b95a2..60d2fefd87 100644 --- a/lib/Pod/Checker.pm +++ b/lib/Pod/Checker.pm @@ -695,7 +695,7 @@ sub idx { =item C<$checker-E<gt>hyperlink()> Add (if argument specified) and retrieve the hyperlinks (as defined by -C<LE<lt>E<gt>>) of the current POD. They consist of an 2-item array: line +C<LE<lt>E<gt>>) of the current POD. They consist of a 2-item array: line number and C<Pod::Hyperlink> object. =back diff --git a/lib/Pod/Html.pm b/lib/Pod/Html.pm index 1e9cd568e8..69953617eb 100644 --- a/lib/Pod/Html.pm +++ b/lib/Pod/Html.pm @@ -1169,7 +1169,7 @@ sub process_cut { } # -# process_pod - process a pod pod tag, thus stop ignoring pod directives +# process_pod - process a pod tag, thus stop ignoring pod directives # until we see a corresponding cut. # sub process_pod { @@ -1574,7 +1574,7 @@ sub process_text1($$;$$){ warn "$0: $podfile: cannot resolve L<$opar> in paragraph $paragraph."; } - # now we have an URL or just plain code + # now we have a URL or just plain code $$rstr = $linktext . '>' . $$rstr; if( defined( $url ) ){ $res = "<A HREF=\"$url\">" . process_text1( $lev, $rstr ) . '</A>'; @@ -1692,7 +1692,7 @@ sub dosify { } # -# page_sect - make an URL from the text of a L<> +# page_sect - make a URL from the text of a L<> # sub page_sect($$) { my( $page, $section ) = @_; diff --git a/lib/Pod/InputObjects.pm b/lib/Pod/InputObjects.pm index 352373b9da..079a40bd5b 100644 --- a/lib/Pod/InputObjects.pm +++ b/lib/Pod/InputObjects.pm @@ -447,7 +447,7 @@ C<-line> keywords indicate the filename and line number corresponding to the beginning of the interior sequence. If the C<$ptree> argument is given, it must be the last argument, and it must be either string, or else an array-ref suitable for passing to B<Pod::ParseTree::new> (or -it may be a reference to an Pod::ParseTree object). +it may be a reference to a Pod::ParseTree object). =cut diff --git a/lib/Pod/LaTeX.pm b/lib/Pod/LaTeX.pm index c909d21f35..218714d2fd 100644 --- a/lib/Pod/LaTeX.pm +++ b/lib/Pod/LaTeX.pm @@ -370,7 +370,7 @@ In its simplest form this is simply: \end{document} -but can be more complicated if a index is required. +but can be more complicated if an index is required. Can be used to set or retrieve the current value. $add = $parser->AddPostamble(); diff --git a/lib/Pod/Man.pm b/lib/Pod/Man.pm index ffb35dc4c3..ab12eeb8e2 100644 --- a/lib/Pod/Man.pm +++ b/lib/Pod/Man.pm @@ -1292,7 +1292,7 @@ output). =item release Set the centered footer. By default, this is the version of Perl you run -Pod::Man under. Note that some system an macro sets assume that the +Pod::Man under. Note that some system macro sets assume that the centered footer will be a modification date and will prepend something like "Last modified: "; if this is the case, you may want to set C<release> to the last modified date and C<date> to the version number. diff --git a/lib/Pod/Parser.pm b/lib/Pod/Parser.pm index 6782519d96..85551faca8 100644 --- a/lib/Pod/Parser.pm +++ b/lib/Pod/Parser.pm @@ -151,7 +151,7 @@ to do more sophisticated tree-based parsing. See L<"TREE-BASED PARSING">. A I<parse-option> is simply a named option of B<Pod::Parser> with a value that corresponds to a certain specified behavior. These various -behaviors of B<Pod::Parser> may be enabled/disabled by setting or +behaviors of B<Pod::Parser> may be enabled/disabled by setting or unsetting one or more I<parse-options> using the B<parseopts()> method. The set of currently accepted parse-options is as follows: @@ -647,7 +647,7 @@ their functionality. This method is useful if you need to perform your own interpolation of interior sequences and can't rely upon B<interpolate> to expand -them in simple bottom-up order order. +them in simple bottom-up order. The parameter C<$text> is a string or block of text to be parsed for interior sequences; and the parameter C<$line_num> is the @@ -1588,7 +1588,7 @@ markup languages like HTML and XML) then you may need to take the tree-based approach. Rather than doing everything in one pass and calling the B<interpolate()> method to expand sequences into text, it may be desirable to instead create a parse-tree using the B<parse_text()> -method to return a tree-like structure which may contain an ordered list +method to return a tree-like structure which may contain an ordered list of children (each of which may be a text-string, or a similar tree-like structure). diff --git a/lib/Pod/Select.pm b/lib/Pod/Select.pm index e7c820f350..8310ea6c7c 100644 --- a/lib/Pod/Select.pm +++ b/lib/Pod/Select.pm @@ -181,7 +181,7 @@ Where I<cmd-expr> is intended to match the name of one or more POD commands, and I<text-expr> is intended to match the paragraph text for the command. If a range-regex is supposed to match a POD command, then the first character of the regex (the one after the initial '/') -absolutely I<must> be an single '=' character; it may not be anything +absolutely I<must> be a single '=' character; it may not be anything else (not even a regex meta-character) if it is supposed to match against the name of a POD command. |