File: fix-pod-spelling.patch

package info (click to toggle)
libpod-abstract-perl 0.26-1
  • links: PTS, VCS
  • area: main
  • in suites: forky, sid
  • size: 340 kB
  • sloc: perl: 2,373; makefile: 2
file content (63 lines) | stat: -rw-r--r-- 1,855 bytes parent folder | download
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
Description: fix POD spelling errors
Origin: vendor
Forwarded: https://rt.cpan.org/Ticket/Display.html?id=125781
 not the current version
Author: Jonathan Yu <jawnsy@cpan.org>
Reviewed-by: gregor herrmann <gregoa@debian.org>
Last-Update: 2025-11-16

--- a/lib/Pod/Abstract/Filter/clear_podcmds.pm
+++ b/lib/Pod/Abstract/Filter/clear_podcmds.pm
@@ -8,7 +8,7 @@
 =head1 NAME
 
 Pod::Abstract::Filter::clear_podcmds - Remove =pod commands from the
-begining of Pod blocks.
+beginning of Pod blocks.
 
 =cut
 
--- a/lib/Pod/Abstract/Filter/add_podcmds.pm
+++ b/lib/Pod/Abstract/Filter/add_podcmds.pm
@@ -8,7 +8,7 @@
 
 =head1 NAME
 
-Pod::Abstract::Filter::add_podcmds - Insert explict =pod commands
+Pod::Abstract::Filter::add_podcmds - Insert explicit =pod commands
 before each Pod block in a document.
 
 =head1 METHODS
--- a/t/05_pod_detailed.t
+++ b/t/05_pod_detailed.t
@@ -71,7 +71,7 @@
 
 These I<should> be parsed.
 
-It's a special trait of POD that : at the begining of a POD block is
+It's a special trait of POD that : at the beginning of a POD block is
 meant to have its internals parsed as POD.
 
 =end
--- a/lib/Pod/Abstract.pm
+++ b/lib/Pod/Abstract.pm
@@ -49,7 +49,7 @@
 
 =head2 USAGE
 
-C<Pod::Abstract> allows easy manupulation and traversal of POD or Perl
+C<Pod::Abstract> allows easy manipulation and traversal of POD or Perl
 files containing POD, without having to manually do any string
 manipulation.
 
--- a/lib/Pod/Abstract/Path.pm
+++ b/lib/Pod/Abstract/Path.pm
@@ -197,7 +197,7 @@
 =head1 PERFORMANCE
 
 Pod::Abstract::Path is not designed to be fast. It is designed to be
-expressive and useful, but it involves sucessive
+expressive and useful, but it involves successive
 expand/de-duplicate/linear search operations and doing this with large
 documents containing many nodes is not suitable for high performance
 systems.