aboutsummaryrefslogtreecommitdiff
path: root/network/libnatpmp
diff options
context:
space:
mode:
authorB. Watson <yalhcru@gmail.com>2022-03-13 18:06:57 -0400
committerB. Watson <yalhcru@gmail.com>2022-03-13 18:06:57 -0400
commitd93cf986e3dc08be8c9fd0919cb8ae14c3f962f5 (patch)
tree8eb367eae0017e636168a74ebb690c9b2fdb10f1 /network/libnatpmp
parentba1ab00ae8f64cd023c7c343a3dcede14599b8ce (diff)
network/libnatpmp: Wrap README at 72 columns.
Signed-off-by: B. Watson <yalhcru@gmail.com>
Diffstat (limited to 'network/libnatpmp')
-rw-r--r--network/libnatpmp/README11
1 files changed, 6 insertions, 5 deletions
diff --git a/network/libnatpmp/README b/network/libnatpmp/README
index ff8458a2200bf..f00f5b1c4d0fd 100644
--- a/network/libnatpmp/README
+++ b/network/libnatpmp/README
@@ -1,5 +1,6 @@
-NAT-PMP is the direct concurrent to the UPnP IGD specification. It is providing
-a way to do NAT traversal. libnatpmp is an attempt to make a portable and
-fully compliant implementation of the protocol for the client side. It is
-based on non blocking sockets and all calls of the API are asynchronous. It
-is therefore very easy to integrate the NAT-PMP code to any event driven code.
+NAT-PMP is the direct concurrent to the UPnP IGD specification. It
+is providing a way to do NAT traversal. libnatpmp is an attempt to
+make a portable and fully compliant implementation of the protocol for
+the client side. It is based on non blocking sockets and all calls of
+the API are asynchronous. It is therefore very easy to integrate the
+NAT-PMP code to any event driven code.