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
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
|
Subject: Fix some spelling errors
Author: Olivier Sallou <olivier.sallou@irisa.fr>
Reviewed-by: gregor herrmann <gregoa@debian.org>
Last-Update: 2016-05-30
Forwarded: https://rt.cpan.org/Ticket/Display.html?id=114814
Bug: https://rt.cpan.org/Ticket/Display.html?id=114814
Description:
Remove spelling errors from man pages
--- a/DBIx/DBStag.pm
+++ b/DBIx/DBStag.pm
@@ -4048,7 +4048,7 @@
the API level.
The default algorithm is to nest each relation element under the
-relation element preceeding it in the FROM clause; for instance:
+relation element preceding it in the FROM clause; for instance:
SELECT * FROM a NATURAL JOIN b NATURAL JOIN c
@@ -4084,7 +4084,7 @@
Now b and c are siblings in the tree. The algorithm is similar to
before: nest each relation element under the relation element
-preceeding it; or, if the preceeding item in the FROM clause is a
+preceding it; or, if the preceding item in the FROM clause is a
bracketed structure, nest it under the first relational element in the
bracketed structure.
--- a/scripts/selectall_xml.pl
+++ b/scripts/selectall_xml.pl
@@ -398,7 +398,7 @@
=item DBSTAG_TEMPLATE_DIRS
-list of directories (seperated by B<:>s) to be searched when templates
+list of directories (separated by B<:>s) to be searched when templates
are requested
=back
@@ -462,7 +462,7 @@
sometimes it is preferable to return the results as a table rather
than xml or a similar nested structure. specifying -rows will fetch a
-table, one line per row, and columns seperated by tabs
+table, one line per row, and columns separated by tabs
=item -pre SQL
--- a/scripts/stag-storenode.pl
+++ b/scripts/stag-storenode.pl
@@ -351,7 +351,7 @@
stag-storenode.pl -u movie -d 'dbi:Pg:mydb' data.mog.xml
-You generally dont need extra metadata here; everything can be
+You generally don't need extra metadata here; everything can be
infered by introspecting the database.
The -u|unit switch controls when transactions are committed
@@ -359,7 +359,7 @@
You can omit the -u switch, and every node directly under the top node
will be stored. This will also be the transaction unit.
-If this works, you should now be able to retreive XML from the database, eg
+If this works, you should now be able to retrieve XML from the database, eg
selectall_xml.pl -d 'dbi:Pg:mydb' 'SELECT * FROM x NATURAL JOIN y'
--- a/DBIx/DBStag/SQLTemplate.pm
+++ b/DBIx/DBStag/SQLTemplate.pm
@@ -783,7 +783,7 @@
[movie.genre = &genre&] [star.lastname = &lastname&]
USE NESTING (set(studio(movie(star))))
-Thats all! However, there are ways to make your template more useful
+That's all! However, there are ways to make your template more useful
=item Example template 2
--- a/scripts/stag-pgslurp.pl
+++ b/scripts/stag-pgslurp.pl
@@ -109,7 +109,7 @@
The -u|unit switch controls when transactions are committed
-If this works, you should now be able to retreive XML from the database, eg
+If this works, you should now be able to retrieve XML from the database, eg
selectall_xml.pl -d 'dbi:Pg:mydb' 'SELECT * FROM x NATURAL JOIN y'
|
