diff options
author | Gurusamy Sarathy <gsar@cpan.org> | 2000-02-04 07:54:04 +0000 |
---|---|---|
committer | Gurusamy Sarathy <gsar@cpan.org> | 2000-02-04 07:54:04 +0000 |
commit | 808e46e63f3614cadd44c8187e3ba1ff1a6d7721 (patch) | |
tree | 17b7829f061ea5f41d6a893516574e7edf90ed54 /lib | |
parent | 0548b47cfb19b6634dee797c7f5142864b6423ba (diff) | |
download | perl-808e46e63f3614cadd44c8187e3ba1ff1a6d7721.tar.gz |
pod typos (from Gregor N. Purdy <gregor@focusresearch.com>)
p4raw-id: //depot/perl@4982
Diffstat (limited to 'lib')
-rw-r--r-- | lib/Pod/Parser.pm | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/lib/Pod/Parser.pm b/lib/Pod/Parser.pm index c9c67bd8e2..c727142506 100644 --- a/lib/Pod/Parser.pm +++ b/lib/Pod/Parser.pm @@ -142,8 +142,8 @@ For the most part, the B<Pod::Parser> base class should be able to do most of the input parsing for you and leave you free to worry about how to intepret the commands and translate the result. -Note that all we have described here in this quick overview overview is -the simplest most striaghtforward use of B<Pod::Parser> to do stream-based +Note that all we have described here in this quick overview is +the simplest most straightforward use of B<Pod::Parser> to do stream-based parsing. It is also possible to use the B<Pod::Parser::parse_text> function to do more sophisticated tree-based parsing. See L<"TREE-BASED PARSING">. |