pod typo fixes (from Marcel Grunauer <marcel.grunauer@lovely.net>)

p4raw-id: //depot/perl@5823

3 files changed, 6 insertions, 6 deletions

diff --git a/pod/perlhack.pod b/pod/perlhack.pod
index 3a84e95513..c640870264 100644
--- a/pod/perlhack.pod
+++ b/pod/perlhack.pod
@@ -269,7 +269,7 @@ way to gain a precise understanding of the overall architecture of
 the language.
 
 If you build a version of the Perl interpreter with C<-DDEBUGGING>,
-Perl's B<-D> commandline flag will cause copious debugging information
+Perl's B<-D> command line flag will cause copious debugging information
 to be emitted (see the C<perlrun> manpage).  If you build a version of
 Perl with compiler debugging information (e.g. with the C compiler's
 C<-g> option instead of C<-O>) then you can step through the execution
diff --git a/pod/perlnumber.pod b/pod/perlnumber.pod
index 9f628cc9a8..c83e053203 100644
--- a/pod/perlnumber.pod
+++ b/pod/perlnumber.pod
@@ -36,7 +36,7 @@ The term "native" does not mean quite as much when we talk about native
 integers, as it does when native floating point numbers are involved.
 The only implication of the term "native" on integers is that the limits for
 the maximal and the minimal supported true integral quantities are close to
-powers of 2.  However, for "native" floats have a most fundamental
+powers of 2.  However, "native" floats have a most fundamental
 restriction: they may represent only those numbers which have a relatively
 "short" representation when converted to a binary fraction.  For example,
 0.9 cannot be respresented by a native float, since the binary fraction
diff --git a/pod/perlthrtut.pod b/pod/perlthrtut.pod
index 0314d9da6c..0f15d57de7 100644
--- a/pod/perlthrtut.pod
+++ b/pod/perlthrtut.pod
@@ -397,7 +397,7 @@ to get them.
 
 =head2 Ignoring A Thread
 
-join() does three things:it waits for a thread to exit, cleans up
+join() does three things: it waits for a thread to exit, cleans up
 after it, and returns any data the thread may have produced.  But what
 if you're not interested in the thread's return values, and you don't
 really care when the thread finishes? All you want is for the thread
@@ -443,10 +443,10 @@ more than one thread can be accessing this data at once.
 Perl's scoping rules don't change because you're using threads.  If a
 subroutine (or block, in the case of async()) could see a variable if
 you weren't running with threads, it can see it if you are.  This is
-especially important for the subroutines that create, and makes my
+especially important for the subroutines that create, and makes C<my>
 variables even more important.  Remember--if your variables aren't
-lexically scoped (declared with C<my>) you're probably sharing it between
-threads.
+lexically scoped (declared with C<my>) you're probably sharing them
+between threads.
 
 =head2 Thread Pitfall: Races