-Many terms in networking can be interpreted with multiple meanings, and several terms used
-in this document are RMR specific.
-The following definitions are the meanings of terms used within this document and should
-help the reader to understand the intent of meaning.
-
-&beg_dlist( &1.0i Helvetica-bold )
-&term(application) A programme which uses RMR to send and/or receive messages to/from another RMR based application.
-
-&term(Critical error) An error that RMR has encountered which will prevent further successful processing by
- RMR. Critical errors usually indicate that the application should abort.
-
-&term(Endpoint) An RMR based application that is defined as being capable of receiving one or more types of messages
- (as defined by a &ital(message key.) .sm )
-
-&term(Environment variable) A key/value pair which is set externally to the application, but which is available
- to the application (and referenced libraries) through the &cw(getenv) system call. Environment variables
- are the main method of communicating information such as port numbers to RMR.
-
-&term(Error) An abnormal condition that RMR has encountered, but will not affect the overall processing by RMR,
- but may impact certain aspects such as the ability to communicate with a specific endpoint.
- Errors generally indicate that something, usually external to RMR, must be addressed.
-
-&term(Host name) The name of the host as returned by the &cw(gethostbyname) system call. In a containerised
- environment this might be the container or service name depending on how the container is started.
- From RMR's point of view, a host name can be used to resolve an &ital(endpoint) definition in
- a &ital(route table.)
-
-&term(IP) Internet protocol. A low level transmission protocol which governs the transmission of datagrams
+Many terms in networking can be interpreted with multiple meanings,
+and several terms used in various RMR documentation are RMR specific.
+The following definitions are the meanings of terms used within RMR
+documentation and should help the reader to understand the intent of
+meaning.
+
+&beg_dlist( &1.0i Helvetica-bold : : 25,70 )
+&ditem(application) A programme which uses RMR to send and/or receive
+ messages to/from another RMR based application.
+
+&ditem(Critical error) An error that RMR has encountered which will
+ prevent further successful processing by
+ RMR. Critical errors usually indicate that the
+ application should abort.
+
+&ditem(Endpoint) An RMR based application that is defined as being
+ capable of receiving one or more types of
+ messages (as defined by a &ital(routing key.)
+ .sm )
+
+&ditem(Environment variable) A key/value pair which is set externally
+ to the application, but which is available to
+ the application (and referenced libraries)
+ through the &cw(getenv) system
+ call. Environment variables are the main
+ method of communicating information such as
+ port numbers to RMR.
+
+&ditem(Error) An abnormal condition that RMR has encountered, but will
+ not affect the overall processing by RMR, but
+ may impact certain aspects such as the ability
+ to communicate with a specific endpoint.
+ Errors generally indicate that something,
+ usually external to RMR, must be addressed.
+
+&ditem(Host name) The name of the host as returned by the
+ &cw(gethostbyname) system call. In a
+ containerised environment this might be the
+ container or service name depending on how the
+ container is started. From RMR's point of
+ view, a host name can be used to resolve an
+ &ital(endpoint) definition in a &ital(route
+ table.)
+
+&ditem(IP) Internet protocol. A low level transmission protocol
+ which governs the transmission of datagrams