1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
|
From: Ansgar Burchardt <ansgar@43-1.org>
Date: Fri, 29 Jan 2010 17:25:42 +0900
Subject: Correct spelling errors
Bug: https://rt.cpan.org/Ticket/Display.html?id=54314
--- a/lib/XML/Grove/Path.pm
+++ b/lib/XML/Grove/Path.pm
@@ -93,7 +93,7 @@
=head1 DESCRIPTION
C<XML::Grove::Path> returns XML objects located at paths. Paths are
-strings of element names or XML object types seperated by slash ("/")
+strings of element names or XML object types separated by slash ("/")
characters. Paths must always start at the grove object passed to
`C<at_path()>'. C<XML::Grove::Path> is B<not> XPath, but it should
become obsolete when an XPath implementation is available.
@@ -117,7 +117,7 @@
essentially an index into the contents of the parent object.
The `C<#text>' object type treats text objects as if they are not
-normalized. Two consecutive text objects are seperate text objects.
+normalized. Two consecutive text objects are separate text objects.
=head1 AUTHOR
--- a/lib/XML/Grove.pm
+++ b/lib/XML/Grove.pm
@@ -398,7 +398,7 @@
package. Many extensions only need to add methods to
XML::Grove::Document and/or XML::Grove::Element.
-When you create an extension you should definitly provide a way to
+When you create an extension you should definitely provide a way to
invoke your module using objects from your package too. For example,
XML::Grove::AsString's `C<as_string()>' method can also be called
using an XML::Grove::AsString object:
|
