diff options
| author | Martin Lucina <mato@kotelna.sk> | 2010-03-10 23:20:43 +0100 |
|---|---|---|
| committer | Martin Lucina <mato@kotelna.sk> | 2010-03-10 23:20:43 +0100 |
| commit | 9fda070e4d66d538e3c709c6cb8934cbf4442c29 (patch) | |
| tree | 8ab4aa9b72cf7d04b6ce3c4233ae8d5b2ea3223e | |
| parent | 0a1e0beaa2849a51ea659eba0f142ce340d2cc6d (diff) | |
Typeset literal correctly
| -rw-r--r-- | doc/zmq_pgm.txt | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/doc/zmq_pgm.txt b/doc/zmq_pgm.txt index f4810aa..4017db2 100644 --- a/doc/zmq_pgm.txt +++ b/doc/zmq_pgm.txt @@ -90,8 +90,8 @@ data = *OCTET In order for late joining consumers to be able to identify message boundaries, each PGM datagram payload starts with a 16-bit unsigned integer in network byte order specifying either the offset of the first message 'frame' in the datagram -or containing the value 0xFFFF if the datagram contains solely an intermediate -part of a larger message. +or containing the value `0xFFFF` if the datagram contains solely an +intermediate part of a larger message. The following diagram illustrates the layout of a single PGM datagram payload: |