-The ``rmr_wh_open`` function creates a direct link for
-sending, a wormhole, to another RMR based process. Sending
-messages through a wormhole requires that the connection be
-established overtly by the user application (via this
-function), and that the ID returned by ``rmr_wh_open`` be
-passed to the ``rmr_wh_send_msg`` function.
-
-*Vctx* is the RMR void context pointer that was returned by
-the ``rmr_init`` function. *Target* is the *name and port,*
-or *IP-address and port,* combination for the process that
-the wormhole should be connected to. For example,
-"localhost:6123".
-
-When invoked, this function immediately attempts to connect
-to the target process. If the connection cannot be
-established, an error is returned to the caller, and no
-direct messages can be sent to the target. Once a wormhole is
-connected, the underlying transport mechanism (e.g. NNG) will
-provide reconnects should the connection be lost, however the
-handling of messages sent when a connection is broken is
-undetermined as each underlying transport mechanism may
-handle buffering and retries differently.
+The ``rmr_wh_open`` function creates a direct link for
+sending, a wormhole, to another RMR based process. Sending
+messages through a wormhole requires that the connection be
+established overtly by the user application (via this
+function), and that the ID returned by ``rmr_wh_open`` be
+passed to the ``rmr_wh_send_msg`` function.
+
+*Vctx* is the RMR void context pointer that was returned by
+the ``rmr_init`` function. *Target* is the *name and port,*
+or *IP-address and port,* combination for the process that
+the wormhole should be connected to. For example,
+"localhost:6123".
+
+When invoked, this function immediately attempts to connect
+to the target process. If the connection cannot be
+established, an error is returned to the caller, and no
+direct messages can be sent to the target. Once a wormhole is
+connected, the underlying transport mechanism (e.g. NNG) will
+provide reconnects should the connection be lost, however the
+handling of messages sent when a connection is broken is
+undetermined as each underlying transport mechanism may
+handle buffering and retries differently.