[Bps-public-commit] Test-Spelling branch, master, updated. f42e47ee8a557e4b0fa372eec59562fdc61aee96

[Shawn Moore]

The branch, master has been updated
       via  f42e47ee8a557e4b0fa372eec59562fdc61aee96 (commit)
      from  d25c546c09580524e745e51a1f766ae0c9cc0918 (commit)

Summary of changes:
 lib/Test/Spelling.pm |    4 ++--
 1 files changed, 2 insertions(+), 2 deletions(-)

- Log -----------------------------------------------------------------
commit f42e47ee8a557e4b0fa372eec59562fdc61aee96
Author: Shawn M Moore <sartak at bestpractical.com>
Date:   Mon Apr 25 12:28:36 2011 -0400

    Kill EOL whitespace

diff --git a/lib/Test/Spelling.pm b/lib/Test/Spelling.pm
index dad6e2d..d27fbee 100644
--- a/lib/Test/Spelling.pm
+++ b/lib/Test/Spelling.pm
@@ -39,7 +39,7 @@ sub pod_file_spelling_ok {
     $checker->parse_from_file($file, $Spell_temp);
 
     # run spell command and fetch output
-    open ASPELL, "$Spell_cmd < $Spell_temp|" 
+    open ASPELL, "$Spell_cmd < $Spell_temp|"
         or croak "Couldn't run spellcheck command '$Spell_cmd'";
     my @words = <ASPELL>;
     close ASPELL or die;
@@ -167,7 +167,7 @@ because there's no way of predicting if F<spell> will be available or the
 word list used will give the same results (what if it's in a different language,
 for example?). You can have the test, but don't add it to F<MANIFEST> (or add
 it to F<MANIFEST.SKIP> to make sure you don't add it by accident). Anyway,
-your users don't really need to run this test, as it is unlikely that the 
+your users don't really need to run this test, as it is unlikely that the
 documentation will acquire typos while in transit. :-)
 
 You can add your own stopwords (words that should be ignored by the spell

-----------------------------------------------------------------------