From 4ceb83935062bb84fd5da702679a126d12aed8be Mon Sep 17 00:00:00 2001 From: Martin Sustrik Date: Mon, 18 Jan 2010 13:16:14 +0100 Subject: typos in man pages fixed --- man/man7/zmq_udp.7 | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) (limited to 'man/man7/zmq_udp.7') diff --git a/man/man7/zmq_udp.7 b/man/man7/zmq_udp.7 index d0bf46c..0425817 100644 --- a/man/man7/zmq_udp.7 +++ b/man/man7/zmq_udp.7 @@ -1,22 +1,22 @@ .TH zmq_udp 7 "" "(c)2007-2010 iMatix Corporation" "0MQ User Manuals" .SH NAME -UDP-based tranport for 0MQ +UDP-based transport for 0MQ .SH SYNOPSIS UDP transport is exactly the same as PGM transport except that PGM packets are encapsulated in UDP packets. Rationale for this transport is that user-space implementation of PGM requires right to create raw sockets (PGM is located -directly on top of IP layer in the netwroking stack), which is often not +directly on top of IP layer in the networking stack), which is often not available. UDP encapsulation solves this problem, however, it adds some overhead related to creating and transferring UDP packet headers. .SH CONNECTION STRING -Connection string for UDP transport is "udp://" followed by an IP adress -of the NIC to use, semicolon, IP adress of the multicast group, colon and -port numbrt. IP address of the NIC can be either its numeric representation +Connection string for UDP transport is "udp://" followed by an IP address +of the NIC to use, semicolon, IP address of the multicast group, colon and +port number. IP address of the NIC can be either its numeric representation or the name of the NIC as reported by operating system. IP address of the -mutlicast group should be specified in the numeric representation. For example: +multicast group should be specified in the numeric representation. For example: .nf udp://eth0:224.0.0.1:5555 -- cgit v1.2.3