Description: Add encoding, fix spellings
Forwarded: https://rt.cpan.org/Public/Bug/Display.html?id=102433
Author: Christopher Hoskin <mans0954@debian.org>
Reviewed-by: gregor herrmann <gregoa@debian.org>
Last-Update: 2019-11-16

--- a/lib/Thread/Tie.pm
+++ b/lib/Thread/Tie.pm
@@ -350,8 +350,8 @@
 The Thread::Tie module is a proof-of-concept implementation of another
 approach to shared variables.  Instead of having shared variables exist
 in all the threads from which they are accessible, shared variable exist
-as "normal", unshared variables in a seperate thread.  Only a tied object
-exists in each thread from which the shared variable is accesible.
+as "normal", unshared variables in a separate thread.  Only a tied object
+exists in each thread from which the shared variable is accessible.
 
 Through the use of a client-server model, any thread can fetch and/or update
 variables living in that thread.  This client-server functionality is hidden
@@ -373,7 +373,7 @@
 variable.  The same applies for this implementation you might say.  However,
 it B<is> possible to specify a non-standard tie implementation for use
 B<within> the thread.  So with this implementation you B<can> C<tie()> a
-shared variable.  So you B<could> tie a shared hash to a DBM file à la
+shared variable.  So you B<could> tie a shared hash to a DBM file à la
 dbmopen() with this module.
 
 =back
@@ -558,7 +558,7 @@
  my $module = tied( $variable )->module;
 
 The "module" object method returns the name of the module to which the
-variable is tied inside the thread.  It is the same as what was (implicitely)
+variable is tied inside the thread.  It is the same as what was (implicitly)
 specified with the "module" field when the variable was tied.
 
 =head2 thread