Skip to content

Commit bab6893

Browse files
authored
Update README.md
Hi, I noticed three typos in this doc and propose changes accordingly: 1- Original: ...if successfull -- results in an authenticated and secure link... Issue: Spelling error. Correction: ...if successful -- results in an authenticated and secure link... 2- Original: ...one to continously read incoming data... Issue: Spelling error. Correction: ...one to continuously read incoming data... 3- Original: ...the connection is considered slow and unhealty and will be dropped... Issue: Spelling error. Correction: ...the connection is considered slow and unhealthy and will be dropped...
1 parent 3eb02fa commit bab6893

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

cliquenet/README.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -25,7 +25,7 @@ undergo a series of stages.
2525

2626
If the TCP listener accepts a new inbound connection it creates a handshake task which
2727
attempts to perform a Noise handshake which involves a Diffie-Hellman key exchange and
28-
-- if successfull -- results in an authenticated and secure link with an identified
28+
-- if successful -- results in an authenticated and secure link with an identified
2929
peer.
3030

3131
### Connect task
@@ -53,7 +53,7 @@ peer a node drops the one whose associated public key is smaller than its own.
5353

5454
### I/O tasks
5555

56-
After successful connection establishment, two tasks are created, one to continously
56+
After successful connection establishment, two tasks are created, one to continuously
5757
read incoming data and one to send application data. The data is split and encrypted
5858
into frames of 64 KiB (the maximum size of a Noise package) or less. Failure of either
5959
task results in the termination of both and a new connect task is created to
@@ -77,7 +77,7 @@ channel to the respective write task. The capacity of every channel is bounded.
7777
If the one the application uses is full, backpressure is exercised, i.e. the
7878
application has to wait. This can happen for example, if no connection is available
7979
for some time. The channel to an I/O write task is also bounded, but if full, the
80-
connection is considered slow and unhealty and will be dropped, resulting in a new
80+
connection is considered slow and unhealthy and will be dropped, resulting in a new
8181
connect task to re-establish the connection.
8282

8383
## Data frame

0 commit comments

Comments
 (0)