1 files changed, 2 insertions, 2 deletions
diff --git a/doc/man/gnunet-nat-server.1 b/doc/man/gnunet-nat-server.1
index bd1ab4167..dcf856e1c 100644
--- a/doc/man/gnunet-nat-server.1
+++ b/doc/man/gnunet-nat-server.1
@@ -1,4 +1,4 @@
-.TH GNUNET\-NAT\-SERVER 1 "Jan 4, 2012" "GNUnet"
+.TH GNUNET\-NAT\-SERVER 1 "25 Feb 2012" "GNUnet"
 .SH NAME
 gnunet\-nat\-server \- help GNUnet setup test network setup with NAT
@@ -17,7 +17,7 @@ This program will listen on the specified PORT for incoming requests to test a p
 The idea is that gnunet\-nat\-server will be run on some trusted hosts with unrestricted connectivity to allow GNUnet users to test their network configuration.  As written, the code allows any user on the Internet to cause the gnunet\-nat\-server to send 2-bytes of arbitrary data to any TCP or UDP port at any address.  We believe that this is generally harmless.
-When runnung gnunet\-nat\-server, make sure to use a configuration that disables most NAT options but enables 'enable_nat_client' and sets 'internal_address' to the global IP address of your local host.  Also, the gnunet\-helper\-nat\-client should be installed locally and run with root priviledges (SUID), otherwise the gnunet\-nat\-server will not work properly.
+When running gnunet\-nat\-server, make sure to use a configuration that disables most NAT options but enables 'enable_nat_client' and sets 'internal_address' to the global IP address of your local host.  Also, the gnunet\-helper\-nat\-client should be installed locally and run with root privileges (SUID), otherwise the gnunet\-nat\-server will not work properly.
 Note that gnunet\-nat\-server could be run via gnunet\-arm but typically is not.  Also, the name of the host and port that gnunet\-nat\-server is run on should be specified in the NATSERVER option in the [setup] section of the configuration file of hosts that are supposed to autoconfigure with this server.

diff --git a/doc/man/gnunet-nat-server.1 b/doc/man/gnunet-nat-server.1 index bd1ab4167..dcf856e1c 100644 --- a/doc/man/gnunet-nat-server.1 +++ b/doc/man/gnunet-nat-server.1
@@ -1,4 +1,4 @@
1	.TH GNUNET\-NAT\-SERVER 1 "Jan 4, 2012" "GNUnet"	1	.TH GNUNET\-NAT\-SERVER 1 "25 Feb 2012" "GNUnet"
2		2
3	.SH NAME	3	.SH NAME
4	gnunet\-nat\-server \- help GNUnet setup test network setup with NAT	4	gnunet\-nat\-server \- help GNUnet setup test network setup with NAT
@@ -17,7 +17,7 @@ This program will listen on the specified PORT for incoming requests to test a p
17		17
18	The idea is that gnunet\-nat\-server will be run on some trusted hosts with unrestricted connectivity to allow GNUnet users to test their network configuration. As written, the code allows any user on the Internet to cause the gnunet\-nat\-server to send 2-bytes of arbitrary data to any TCP or UDP port at any address. We believe that this is generally harmless.	18	The idea is that gnunet\-nat\-server will be run on some trusted hosts with unrestricted connectivity to allow GNUnet users to test their network configuration. As written, the code allows any user on the Internet to cause the gnunet\-nat\-server to send 2-bytes of arbitrary data to any TCP or UDP port at any address. We believe that this is generally harmless.
19		19
20	When runnung gnunet\-nat\-server, make sure to use a configuration that disables most NAT options but enables 'enable_nat_client' and sets 'internal_address' to the global IP address of your local host. Also, the gnunet\-helper\-nat\-client should be installed locally and run with root priviledges (SUID), otherwise the gnunet\-nat\-server will not work properly.	20	When running gnunet\-nat\-server, make sure to use a configuration that disables most NAT options but enables 'enable_nat_client' and sets 'internal_address' to the global IP address of your local host. Also, the gnunet\-helper\-nat\-client should be installed locally and run with root privileges (SUID), otherwise the gnunet\-nat\-server will not work properly.
21		21
22	Note that gnunet\-nat\-server could be run via gnunet\-arm but typically is not. Also, the name of the host and port that gnunet\-nat\-server is run on should be specified in the NATSERVER option in the [setup] section of the configuration file of hosts that are supposed to autoconfigure with this server.	22	Note that gnunet\-nat\-server could be run via gnunet\-arm but typically is not. Also, the name of the host and port that gnunet\-nat\-server is run on should be specified in the NATSERVER option in the [setup] section of the configuration file of hosts that are supposed to autoconfigure with this server.
23		23