From: Robin Barker <RMBarker@cpan.org>
Date: Fri, 14 Sep 2001 16:01:11 +0000 (+0100)
Subject: Re: unterminated C<...> at line 426 in file perlport.pod
X-Git-Url: http://git.shadowcat.co.uk/gitweb/gitweb.cgi?a=commitdiff_plain;h=518ae4c95f8ef92666562e878220b3968c4e5cd6;p=p5sagit%2Fp5-mst-13.2.git

Re: unterminated C<...> at line 426 in file perlport.pod
Message-Id: <200109141501.QAA13044@tempest.npl.co.uk>

p4raw-id: //depot/perl@12019
---

diff --git a/pod/perlport.pod b/pod/perlport.pod
index 48f8084..b8a5a2a 100644
--- a/pod/perlport.pod
+++ b/pod/perlport.pod
@@ -424,7 +424,7 @@ The Unix System V IPC (C<msg*(), sem*(), shm*()>) is not available
 even on all Unix platforms.
 
 Do not use either the bare result of C<pack("N", 10, 20, 30, 40)>
-or bare v-strings (such as C<v10.20.30.40>) or the to represent
+or bare v-strings (such as C<v10.20.30.40>) or to represent
 IPv4 addresses: both forms just pack the four bytes into network order.
 That this would be equal to the C language C<in_addr> struct (which is
 what the socket code internally uses) is not guaranteed.  To be