summaryrefslogtreecommitdiff
path: root/pod/perlipc.pod
diff options
context:
space:
mode:
authorGurusamy Sarathy <gsar@cpan.org>2000-03-03 18:58:45 +0000
committerGurusamy Sarathy <gsar@cpan.org>2000-03-03 18:58:45 +0000
commitc47ff5f1a1ef5d0daccf1724400a446cd8e93573 (patch)
tree8a136c0e449ebac6ea6e35898b5ae06788800c41 /pod/perlipc.pod
parent10c8fecdc2f0a2ef9c548abff5961fa25cd83eca (diff)
downloadperl-c47ff5f1a1ef5d0daccf1724400a446cd8e93573.tar.gz
whitespace and readabiliti nits in the pods (from Michael G Schwern
and Robin Barker) p4raw-id: //depot/perl@5493
Diffstat (limited to 'pod/perlipc.pod')
-rw-r--r--pod/perlipc.pod4
1 files changed, 2 insertions, 2 deletions
diff --git a/pod/perlipc.pod b/pod/perlipc.pod
index 3649e4f883..3ddea3e41b 100644
--- a/pod/perlipc.pod
+++ b/pod/perlipc.pod
@@ -1024,7 +1024,7 @@ something to the server before fetching the server's response.
The web server handing the "http" service, which is assumed to be at
its standard port, number 80. If your the web server you're trying to
connect to is at a different port (like 1080 or 8080), you should specify
-as the named-parameter pair, C<PeerPort =E<gt> 8080>. The C<autoflush>
+as the named-parameter pair, C<< PeerPort => 8080 >>. The C<autoflush>
method is used on the socket because otherwise the system would buffer
up the output we sent it. (If you're on a Mac, you'll also need to
change every C<"\n"> in your code that sends data over the network to
@@ -1142,7 +1142,7 @@ well.
As always, setting up a server is little bit more involved than running a client.
The model is that the server creates a special kind of socket that
does nothing but listen on a particular port for incoming connections.
-It does this by calling the C<IO::Socket::INET-E<gt>new()> method with
+It does this by calling the C<< IO::Socket::INET->new() >> method with
slightly different arguments than the client did.
=over