gnunet-handbook

The GNUnet Handbook
Log | Files | Refs

commit 2fff8cb90359da47cb0fd4de77c5dc8e770c0c0f
parent 9c5b9d9040d21542eff792e26624cf9669b127aa
Author: marshall <stmr@umich.edu>
Date:   Mon,  3 Apr 2023 15:44:41 -0400

transport-ng: fix typos

Diffstat:
Mdevelopers/subsystems/transport-ng/transport-ng.rst | 6+++---
1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/developers/subsystems/transport-ng/transport-ng.rst b/developers/subsystems/transport-ng/transport-ng.rst @@ -65,7 +65,7 @@ In order to address the above issues, we want to: *communicators*. Communicators connect as clients to the transport service. -- TRANSPORT should be able to utilize any number of communcators to the +- TRANSPORT should be able to utilize any number of communicators to the same peer at the same time. - TRANSPORT should be responsible for fragmentation, retransmission, @@ -73,7 +73,7 @@ In order to address the above issues, we want to: configure bandwidth limits: TRANSPORT should detect what is available and use it. -- Commnunicators should be allowed to be uni-directional and +- Communicators should be allowed to be uni-directional and unreliable. TRANSPORT shall create bi-directional channels from this whenever possible. @@ -92,7 +92,7 @@ In order to address the above issues, we want to: should consider those options when scheduling messages for transmission. -- HELLOs should be in a humman-readable format with monotonic time +- HELLOs should be in a human-readable format with monotonic time expirations. The new architecture is planned as follows: