From: Jesse Luehrs <doy@tozt.net>
Date: Thu, 18 Nov 2010 05:07:17 +0000 (-0600)
Subject: typo fixes and reformatting
X-Git-Tag: 1.21~16
X-Git-Url: http://git.shadowcat.co.uk/gitweb/gitweb.cgi?a=commitdiff_plain;h=1ade5e062234f592830284d6c56fe67212c629db;p=gitmo%2FMoose.git

typo fixes and reformatting
(cherry picked from commit a02149068eb26c669bc3dbd875ebf695b9d3b32e)
---

diff --git a/lib/Moose/Manual/Support.pod b/lib/Moose/Manual/Support.pod
index f27d72c..87cf54b 100644
--- a/lib/Moose/Manual/Support.pod
+++ b/lib/Moose/Manual/Support.pod
@@ -7,33 +7,38 @@ compatibility.
 
 =head1 SUPPORT POLICY
 
-There are two principles to Moose's Policy of Supported Behavior
+There are two principles to Moose's policy of supported behavior.
 
 1. Moose favors correctness over everything.
-2. Moose supports documented and tested behavior, not accidental behavior or side effects.
+2. Moose supports documented and tested behavior, not accidental behavior or
+side effects.
 
-If a behavior has never been documented or tested, the behavior is I<officially> undefined. Relying
-upon undocumented and untested behavior is done at your own risk.
+If a behavior has never been documented or tested, the behavior is
+I<officially> undefined. Relying upon undocumented and untested behavior is
+done at your own risk.
 
-If a behavior is documented or tested but found to be incorrect later, the behavior will go through a
-deprecation period in which it warns before being removed.
+If a behavior is documented or tested but found to be incorrect later, the
+behavior will go through a deprecation period in which it warns before being
+removed.
 
 =head1 RELEASE SCHEDULE
 
-Moose uses the release early, release often philosophy. 
+Moose uses the release early, release often philosophy.
 
-Moose is on a system of weekly minor releases, and quarterly major releases. A minor release is
-deifined as one that makes every attempt to not break backwards compatibility. Currently this means
-that the dependency conflict lists, and test suite did not change substantially, or that any changes
-were additive.
+Moose is on a system of weekly minor releases and quarterly major releases. A
+minor release is defined as one that makes every attempt to not break
+backwards compatibility. Currently this means that the dependency conflict
+lists and test suite did not change substantially, or that any changes were
+additive.
 
-Major releases are potentially backwards incompatibiliy. Moose prioritizes correcness over backwards
-compatibility or performance, see the Deprecation Policy below for how backwards incompatible changes
-are announced.
+Major releases are potentially backwards incompatible. Moose prioritizes
+correctness over backwards compatibility or performance; see the Deprecation
+Policy below for how backwards incompatible changes are announced.
 
-Before a major release, a series of Development Releases will be made so that users can test the
-upcoming major release before it is distributed to CPAN. It is in the best interests of everyone
-involved if these releases are tested as widely as possible.
+Before a major release, a series of development releases will be made so that
+users can test the upcoming major release before it is distributed to CPAN. It
+is in the best interests of everyone involved if these releases are tested as
+widely as possible.
 
 =head1 DEPRECATION POLICY