5 files changed, 8 insertions, 8 deletions
diff --git a/man/man3/zmq_bind.3 b/man/man3/zmq_bind.3
index b8f2102..61d97fa 100644
--- a/man/man3/zmq_bind.3
+++ b/man/man3/zmq_bind.3
@@ -8,7 +8,7 @@ The function binds socket
 .IR s
 to a particular transport. Actual semantics of the 
 command depend on the underlying transport mechanism, however, in cases where
-peers connect in an asymetric manner,
+peers connect in an asymmetric manner,
 .IR zmq_bind
 should be called first,
 .IR zmq_connect
diff --git a/man/man3/zmq_connect.3 b/man/man3/zmq_connect.3
index dd0b5d8..925b66e 100644
--- a/man/man3/zmq_connect.3
+++ b/man/man3/zmq_connect.3
@@ -9,7 +9,7 @@ The function connect socket
 to the peer identified by
 .IR addr .
 Actual semantics of the  command depend on the underlying transport mechanism,
-however, in cases where peers connect in an asymetric manner,
+however, in cases where peers connect in an asymmetric manner,
 .IR zmq_bind
 should be called first,
 .IR zmq_connect
diff --git a/man/man3/zmq_recv.3 b/man/man3/zmq_recv.3
index 37d43d9..8a961bb 100644
--- a/man/man3/zmq_recv.3
+++ b/man/man3/zmq_recv.3
@@ -33,7 +33,7 @@ it's a non-blocking receive and there's no message available at the moment.
 function isn't supported by particular socket type.
 .IP "\fBEFSM\fP"
 function cannot be called at the moment, because socket is not in the
-approprite state. This error may occur with sockets that switch between
+appropriate state. This error may occur with sockets that switch between
 several states (e.g. ZMQ_REQ).
 .SH EXAMPLE
 .nf
diff --git a/man/man3/zmq_send.3 b/man/man3/zmq_send.3
index 4924ce0..c6644fc 100644
--- a/man/man3/zmq_send.3
+++ b/man/man3/zmq_send.3
@@ -41,7 +41,7 @@ it's a non-blocking send and message cannot be sent at the moment.
 function isn't supported by particular socket type.
 .IP "\fBEFSM\fP"
 function cannot be called at the moment, because socket is not in the
-approprite state. This error may occur with sockets that switch between
+appropriate state. This error may occur with sockets that switch between
 several states (e.g. ZMQ_REQ).
 .SH EXAMPLE
 .nf
diff --git a/man/man3/zmq_socket.3 b/man/man3/zmq_socket.3
index 9eb77c8..3574421 100644
--- a/man/man3/zmq_socket.3
+++ b/man/man3/zmq_socket.3
@@ -21,7 +21,7 @@ single bind. There's no message routing or message filtering involved.
 Compatible peer sockets: ZMQ_P2P.
 
 .IP "\fBZMQ_PUB\fP"
-Socket to distribute data. Recv fuction is not implemented for this socket
+Socket to distribute data. Recv function is not implemented for this socket
 type. Messages are distributed in fanout fashion to all the peers.
 
 Compatible peer sockets: ZMQ_SUB.
@@ -50,7 +50,7 @@ Compatible peer sockets: ZMQ_REQ, ZMQ_XREQ.
 .IP "\fBZMQ_XREQ\fP"
 Special socket type to be used in request/reply middleboxes such as
 .BR zmq_queue(7) .
-Requests forwarded using this socket type should be tagged by a proper postix
+Requests forwarded using this socket type should be tagged by a proper prefix
 identifying the original requester. Replies received by this socket are tagged
 with a proper postfix that can be use to route the reply back to the original
 requester.
@@ -60,9 +60,9 @@ Compatible peer sockets: ZMQ_REP, ZMQ_XREP.
 .IP "\fBZMQ_XREP\fP"
 Special socket type to be used in request/reply middleboxes such as
 .BR zmq_queue(7) .
-Requests received using this socket are already properly tagged with postfix
+Requests received using this socket are already properly tagged with prefix
 identifying the original requester. When sending a reply via XREP socket the
-message should be tagged with a postfix from a corresponding request.
+message should be tagged with a prefix from a corresponding request.
 
 Compatible peer sockets: ZMQ_REQ, ZMQ_XREQ.