aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorB. Watson <yalhcru@gmail.com>2022-03-14 03:54:27 -0400
committerB. Watson <yalhcru@gmail.com>2022-03-14 03:54:27 -0400
commit5d2cb106b78fea39b5baa9644a20aaa16ea4934d (patch)
treeebbed9a61386293486e8a759348f091a076d73a4
parente47c3c0954a8636d9eb2acd273c65d5812e93e4e (diff)
perl/perl-CPAN-Changes: Wrap README at 72 columns.
Signed-off-by: B. Watson <yalhcru@gmail.com>
-rw-r--r--perl/perl-CPAN-Changes/README10
1 files changed, 5 insertions, 5 deletions
diff --git a/perl/perl-CPAN-Changes/README b/perl/perl-CPAN-Changes/README
index 6772088c198e..9838f44b55a8 100644
--- a/perl/perl-CPAN-Changes/README
+++ b/perl/perl-CPAN-Changes/README
@@ -1,10 +1,10 @@
-It is standard practice to include a Changes file in your distribution. The
-purpose the Changes file is to help a user figure out what has changed since
-the last release.
+It is standard practice to include a Changes file in your
+distribution. The purpose the Changes file is to help a user figure
+out what has changed since the last release.
People have devised many ways to write the Changes file. A preliminary
specification has been created (CPAN::Changes::Spec) to encourage module
authors to write clear and concise Changes.
-This module will help users programmatically read and write Changes files that
-conform to the specification.
+This module will help users programmatically read and write Changes
+files that conform to the specification.