From 5a0fe433b8127d9d11d2a252b1ce6d30bb783553 Mon Sep 17 00:00:00 2001 From: Greg Davidson Date: Fri, 6 Aug 2021 11:49:38 -0700 Subject: [PATCH] Update 2020-04-22-real-world-effectiveness-of-brotli.md Tiny typo fix. Thanks for this amazing deep-dive into brotli v.s. gzip Harry! --- _posts/2020-04-22-real-world-effectiveness-of-brotli.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/_posts/2020-04-22-real-world-effectiveness-of-brotli.md b/_posts/2020-04-22-real-world-effectiveness-of-brotli.md index 18ebd088..91486787 100644 --- a/_posts/2020-04-22-real-world-effectiveness-of-brotli.md +++ b/_posts/2020-04-22-real-world-effectiveness-of-brotli.md @@ -91,7 +91,7 @@ the speed at which those admittedly fewer chunks of data arrive will not change. ### TCP, Packets, and Round Trips Taking a very reductive and simplistic view of how files are transmitted from -server to client, we need to look at TCP. When we receive a file from a sever, +server to client, we need to look at TCP. When we receive a file from a server, we don’t get the whole file in one go. TCP, upon which HTTP sits, breaks the file up into segments, or _packets_. Those packets are sent, in batches, in order, to the client. They are each acknowledged before the next series of