From 5b6ab7e1d247cb9dcd1127af65d096ff98ac93c6 Mon Sep 17 00:00:00 2001 From: Tilka Date: Mon, 19 Mar 2012 14:00:37 +0100 Subject: [PATCH] minimal documentation fixes --- doc/architecture.txt | 4 ++-- doc/extensions.txt | 2 +- 2 files changed, 3 insertions(+), 3 deletions(-) diff --git a/doc/architecture.txt b/doc/architecture.txt index 8007d3f..19d1163 100644 --- a/doc/architecture.txt +++ b/doc/architecture.txt @@ -1,13 +1,13 @@ = Architecture of uHub = -uHub is single threaded and handles network and timer events using the +uHub is single-threaded and handles network and timer events using the libevent library. For each state there is a read event (and sometimes a write event) and timeout event in case an expected read (or write) event does not occur. == Protocol overview == -uHub use "speak" the ADC protocol, which works in short as follows: +uHub "speaks" the ADC protocol, which works in short as follows: (C = client, S = server aka uHub). C: HSUP ADBASE diff --git a/doc/extensions.txt b/doc/extensions.txt index 7cfc0b3..a72b85e 100644 --- a/doc/extensions.txt +++ b/doc/extensions.txt @@ -31,7 +31,7 @@ The hub should send a packet containing the token back: 'IECH {token} {host:port}', aswell as the same message via TCP. If the client receives the message via UDP, it should now be able to determine the type of NAT. -If the client receives the message via TCP only it knows it has a firewall blocking icomming communication. +If the client receives the message via TCP only it knows it has a firewall blocking incomming communication. If the client does not receive the message, it should assume a firewall is blocking all UDP communication, and resume in passive mode.