From 85ccb0066a86a3558ae81cd357463f8dc631f94b Mon Sep 17 00:00:00 2001
From: Garrett D'Amore <garrett@damore.org>
Date: Wed, 14 Mar 2018 15:40:46 -0700
Subject: fixes #289 nng_sockaddr could just be a union fixes #290 sockaddr
 improvements

---
 docs/man/nng_inproc.adoc | 10 +++++-----
 1 file changed, 5 insertions(+), 5 deletions(-)

(limited to 'docs/man/nng_inproc.adoc')

diff --git a/docs/man/nng_inproc.adoc b/docs/man/nng_inproc.adoc
index c0dc270d..5123c3a3 100644
--- a/docs/man/nng_inproc.adoc
+++ b/docs/man/nng_inproc.adoc
@@ -31,8 +31,7 @@ to slower transports when data must be moved within the same process.
 This transport tries hard to avoid copying data, and thus is very
 light-weight.
 
-Registration
-~~~~~~~~~~~~
+=== Registration
 
 The _inproc_ transport is generally built-in to the _nng_ core, so
 no extra steps to use it should be necessary.
@@ -52,7 +51,8 @@ that URI.
 === Socket Address
 
 When using an `nng_sockaddr` structure, the actual structure is of type
-`struct nng_sockaddr_inproc`.  This type has the following definition:
+`struct nng_sockaddr_inproc`.
+This type has the following definition:
 
 [source,c]
 --------
@@ -62,9 +62,9 @@ When using an `nng_sockaddr` structure, the actual structure is of type
 typedef nng_sockaddr_inproc {
     // <2>
     uint16_t sa_family;                  // must be NNG_AF_INPROC
-    char     sa_path[NNG_MAXADDRLEN];    // arbitrary "path"
+    char     sa_name[NNG_MAXADDRLEN];    // arbitrary "name"
     //
-}
+} nng_sockaddr_inproc;
 --------
 <1> The values of these macros may change, so applications
 should avoid depending upon their values and instead use them symbolically.
-- 
cgit v1.2.3-70-g09d2

