From 9fda070e4d66d538e3c709c6cb8934cbf4442c29 Mon Sep 17 00:00:00 2001 From: Martin Lucina Date: Wed, 10 Mar 2010 23:20:43 +0100 Subject: Typeset literal correctly --- doc/zmq_pgm.txt | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) (limited to 'doc') 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: -- cgit v1.2.3