Update markup with simpler copyright and new-style asciidoctor.

1 files changed, 21 insertions, 26 deletions

diff --git a/docs/nng.adoc b/docs/nng.adoc
index 62482d09..21288fff 100644
--- a/docs/nng.adoc
+++ b/docs/nng.adoc
@@ -2,12 +2,11 @@
 :doctype: manpage
 :manmanual: nng
 :mansource: nng
-:copyright: Copyright 2018 Staysail Systems, Inc. <info@staysail.tech> \
-            Copyright 2018 Capitar IT Group BV <info@capitar.com> \
-            This software is supplied under the terms of the MIT License, a \
-            copy of which should be located in the distribution where this \
-            file was obtained (LICENSE.txt).  A copy of the license may also \
-            be found online at https://opensource.org/licenses/MIT.
+:copyright: Copyright 2018 mailto:info@staysail.tech[Staysail Systems, Inc.] + \
+            Copyright 2018 mailto:info@capitar.com[Capitar IT Group BV] + \
+            {blank} + \
+            This document is supplied under the terms of the \
+            https://opensource.org/licenses/MIT[MIT License].
 
 == NAME
 nng - nanomsg next generation
@@ -123,21 +122,21 @@ The URLs used in _nng_ are canonicalized as follows, mostly in
 accordance with
 https://tools.ietf.org/html/rfc3986#section-6.2.2[RFC 3986 6.2.2]:
 
-  1. The URL is parsed into scheme, userinfo, host, port, path, query and
-     fragment components.  (Not all of these members are necessarily present.)
-  2. The scheme, hostname, and port if present, are converted to lower case.
-  3. Percent-encoded values for
-     https://tools.ietf.org/html/rfc3986#section-2.3[unreserved characters]
-     converted to their unencoded forms.
-  4. Additionally URL percent-encoded values for characters in the path
-     and with numeric values larger than 127 (i.e. not ASCII) are decoded.
-  5. The resulting path is checked for invalid UTF-8 sequences, consisting
-     of surrogate pairs, illegal byte sequences, or overlong encodings.
-     If this check fails, then the entire URL is considered invalid.
-  6. Path segments consisting of `.` and `..` are resolved as per 
-     https://tools.ietf.org/html/rfc3986#section-6.2.2.3[RFC 3986 6.2.2.3].
-  7. Further, empty path segments are removed, meaning that duplicate
-     slash (`/`) separators are removed from the path.
+  . The URL is parsed into scheme, userinfo, host, port, path, query and
+    fragment components.  (Not all of these members are necessarily present.)
+  . The scheme, hostname, and port if present, are converted to lower case.
+  . Percent-encoded values for
+    https://tools.ietf.org/html/rfc3986#section-2.3[unreserved characters]
+    converted to their unencoded forms.
+  . Additionally URL percent-encoded values for characters in the path
+    and with numeric values larger than 127 (i.e. not ASCII) are decoded.
+  . The resulting path is checked for invalid UTF-8 sequences, consisting
+    of surrogate pairs, illegal byte sequences, or overlong encodings.
+    If this check fails, then the entire URL is considered invalid.
+  . Path segments consisting of `.` and `..` are resolved as per 
+    https://tools.ietf.org/html/rfc3986#section-6.2.2.3[RFC 3986 6.2.2.3].
+  . Further, empty path segments are removed, meaning that duplicate
+    slash (`/`) separators are removed from the path.
 
 Note that steps 4, 5, and 7 are not specified by RFC 3986, but performing
 them is believed to improve both the usability and security of _nng_
@@ -154,8 +153,4 @@ The library API is documented at <<libnng#,libnng(3)>>.
 
 == COPYRIGHT
 
-Copyright 2018 mailto:info@staysail.tech[Staysail Systems, Inc] +
-Copyright 2018 mailto:info@capitar.com[Capitar IT Group BV]
-
-This document is supplied under the terms of the
-https://opensource.org/licenses/MIT[MIT License].
+{copyright}
\ No newline at end of file