From fd8088e6f7cc8ef14b09299aa9fe8d8d0a6316c6 Mon Sep 17 00:00:00 2001 From: haskal Date: Sat, 14 Mar 2020 18:48:35 -0400 Subject: [PATCH] Fix readme typos --- README.md | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/README.md b/README.md index 7704c86..b7ddd8f 100644 --- a/README.md +++ b/README.md @@ -9,13 +9,13 @@ ## High level approach For this assignment we developed a new protocol that would be particularly efficient at -transferring a file over an unreliable connection. The protocol devides the input file +transferring a file over an unreliable connection. The protocol divides the input file into fixed-length "segments", numbers them sequentially, and attempts to transfer them to the receiver. It repeatedly retransmits segments that it is not confident that the -receiever has obtained. The receiever periodically sends batched-acknowledgements that -list receieved segments. The segments are compressed using state-of-the-art compression +receiver has obtained. The receiver periodically sends batched-acknowledgements that +list received segments. The segments are compressed using state-of-the-art compression algorithms to ensure expedient delivery. The rate of sending and acknowledgement is -continuously tuned to optimize for network conditions. +continuously tuned to optimize for network conditions using coding and algorithms. ## Challenges @@ -30,7 +30,7 @@ We faced many challenges implementing this protocol, such as the following: ## Testing -Various internal algorithms and datastructures were tested using simple unit tests. For +Various internal algorithms and data structures were tested using simple unit tests. For instance, we have unit tests to check that our packet encoding/decoding schemes work correctly.