7 files changed, 21 insertions, 21 deletions
diff --git a/man/man7/zmq.7 b/man/man7/zmq.7
index 61543a7..ed7e08b 100644
--- a/man/man7/zmq.7
+++ b/man/man7/zmq.7
@@ -16,7 +16,7 @@ throughputs are to be measured in millions of messages per second.
 0MQ is designed to be very thin. It requires no more than couple of
 pages in resident memory and is thus well suited for any environment ranging
 from small embedded devices, routers and cell phones to enterprise-scale
-datacenters.
+data centers.
 
 0MQ runs on a wide range of operating systems and supports variety of processor
 microarchitectures.
@@ -92,7 +92,7 @@ Poll for I/O events:
 .BR zmq_poll(3)
 
 .SH ERROR HANDLING
-0MQ defines couple of non-POSIX error codes. Use following fuctions to handle
+0MQ defines couple of non-POSIX error codes. Use following functions to handle
 them neatly.
 
 Convert error code into human readable string:
diff --git a/man/man7/zmq_cpp.7 b/man/man7/zmq_cpp.7
index 4df9157..63f6e79 100644
--- a/man/man7/zmq_cpp.7
+++ b/man/man7/zmq_cpp.7
@@ -56,7 +56,7 @@ is mapped to
 .BR zmq_msg_copy(3)
 etc.
 
-C++ provides an additional function not avialable with C API.
+C++ provides an additional function not available with C API.
 .IR zmq::message_t::rebuild
 is equivalent to calling
 .BR zmq_close(3)
diff --git a/man/man7/zmq_inproc.7 b/man/man7/zmq_inproc.7
index 0c84641..16abce6 100644
--- a/man/man7/zmq_inproc.7
+++ b/man/man7/zmq_inproc.7
@@ -1,6 +1,6 @@
 .TH zmq_inproc 7 "" "(c)2007-2010 iMatix Corporation" "0MQ User Manuals"
 .SH NAME
-In-process (inter-thread) tranport for 0MQ
+In-process (inter-thread) transport for 0MQ
 .SH SYNOPSIS
 
 In-process transport is optimised for passing messages between threads in the
diff --git a/man/man7/zmq_ipc.7 b/man/man7/zmq_ipc.7
index 28e57d0..e1731ad 100644
--- a/man/man7/zmq_ipc.7
+++ b/man/man7/zmq_ipc.7
@@ -1,14 +1,14 @@
 .TH zmq_ipc 7 "" "(c)2007-2010 iMatix Corporation" "0MQ User Manuals"
 .SH NAME
-Inter-process tranport for 0MQ
+Inter-process transport for 0MQ
 .SH SYNOPSIS
 
-In-process transport is optimised for passing messages between processes on the
-same physical machine.
+Inter-process transport is optimised for passing messages between processes on
+the same physical machine.
 
 .SH CONNECTION STRING
 
-Connection string for inproc transport is "inproc://" followed by a file name.
+Connection string for inproc transport is "ipc://" followed by a file name.
 The file will be used as placeholder for a message endpoint. (UNIX domain
 sockets associate a file with the listening socket in a similar way.)
 
diff --git a/man/man7/zmq_pgm.7 b/man/man7/zmq_pgm.7
index 39f639b..fb37735 100644
--- a/man/man7/zmq_pgm.7
+++ b/man/man7/zmq_pgm.7
@@ -1,6 +1,6 @@
 .TH zmq_pgm 7 "" "(c)2007-2010 iMatix Corporation" "0MQ User Manuals"
 .SH NAME
-PGM-based tranport for 0MQ
+PGM-based transport for 0MQ
 .SH SYNOPSIS
 
 PGM is a protocol for reliable multicast (RFC3208). 0MQ's PGM transport allows
@@ -20,11 +20,11 @@ PGM transport can be used only with ZMQ_PUB and ZMQ_SUB sockets.
 
 .SH CONNECTION STRING
 
-Connection string for PGM transport is "pgm://" 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 PGM transport is "pgm://" 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
     pgm://eth0:224.0.0.1:5555
diff --git a/man/man7/zmq_tcp.7 b/man/man7/zmq_tcp.7
index 41a116b..52bf0d2 100644
--- a/man/man7/zmq_tcp.7
+++ b/man/man7/zmq_tcp.7
@@ -1,6 +1,6 @@
 .TH zmq_tcp 7 "" "(c)2007-2010 iMatix Corporation" "0MQ User Manuals"
 .SH NAME
-TCP-based tranport for 0MQ
+TCP-based transport for 0MQ
 .SH SYNOPSIS
 
 TCP is an ubiquitous unicast transport. When connecting distributed
@@ -8,7 +8,7 @@ applications, you will mostly use TCP transport.
 
 .SH CONNECTION STRING
 
-Connection string for TCP transport is "tcp://" followed by an IP adress,
+Connection string for TCP transport is "tcp://" followed by an IP address,
 colon and port number. IP address can be either its numeric representation,
 a NIC name or a hostname (resolved by DNS):
 
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