X-Git-Url: http://git.shadowcat.co.uk/gitweb/gitweb.cgi?p=scpubgit%2FObject-Remote.git;a=blobdiff_plain;f=lib%2FObject%2FRemote.pm;h=ee9309e5511437811874c1cd7d68197ac3a72a1d;hp=2c8c096ff2ccd8a343f5a4be83e398f4e6e95583;hb=55c0d0209fa9d9265ff178f54ae9fe5fdddef3c1;hpb=5ccce2d5c1fb651f83c73c811069003e4a591a53

diff --git a/lib/Object/Remote.pm b/lib/Object/Remote.pm
index 2c8c096..ee9309e 100644
--- a/lib/Object/Remote.pm
+++ b/lib/Object/Remote.pm
@@ -163,7 +163,7 @@ See L<Object::Remote::Logging::Router>.
 
 =head1 KNOWN ISSUES
 
-=over 4 
+=over 4
 
 =item Large data structures
 
@@ -204,7 +204,7 @@ timeouts taking longer than configured.
 
 =item Deadlocks
 
-Deadlocks can happen quite easily because of flaws in programs that use Object::Remote or 
+Deadlocks can happen quite easily because of flaws in programs that use Object::Remote or
 Object::Remote itself so the C<Object::Remote::WatchDog> is available. When used the run
 loop will periodically update the watch dog object on the remote Perl interpreter. If the
 watch dog goes longer than the configured interval with out being updated then it will