aboutsummaryrefslogtreecommitdiff
path: root/content
diff options
context:
space:
mode:
Diffstat (limited to 'content')
-rw-r--r--content/en/blog/20220212-tcp-ip-architecture.md6
1 files changed, 3 insertions, 3 deletions
diff --git a/content/en/blog/20220212-tcp-ip-architecture.md b/content/en/blog/20220212-tcp-ip-architecture.md
index ca4f58a..49fea7a 100644
--- a/content/en/blog/20220212-tcp-ip-architecture.md
+++ b/content/en/blog/20220212-tcp-ip-architecture.md
@@ -152,7 +152,7 @@ Layer 1: At the physical layer, Ethernet has a minimum frame size,
which is required to accurately detect collisions. For 10/100Mbit this
is 64 bytes. Shorter frames must be _padded_. How to distinguish the
padding from a packet which actually has zeros at the end of its data?
-Well, Ethernet has a _length_ field_ in the MAC header. But in DIX
+Well, Ethernet has a _length_ field in the MAC header. But in DIX
Ethernet that is an Ethertype, so a _length_ field in the IP header is
used (both IPv4 as IPv6). A Layer 1 problem is actually propagated
into Layer 2 and even Layer 3. Gigabit Ethernet has an even larger
@@ -196,7 +196,7 @@ consequences of these seemingly insignificant pet peeves of mine.
The term _ossification of the Internet_ is sometimes used to describe
difficulties in making sizeable changes within the TCP/IP network
-_stack -- a lack of _evolvability_. For most technologies, there is a
+stack -- a lack of _evolvability_. For most technologies, there is a
steady cycle of innovation, adoption and deprecation. Remember DOS,
OS/2, Windows 3.1, Windows 95? Right, that's what they are: once
ubiquitous, now mostly memories. In contrast, "Next Generation
@@ -446,4 +446,4 @@ Dimitri
-- fixes for urgent problems and improvements in the short
term. I want to stress that we were never treated unfairly by
any reviewer, and this section should not be read as a complaint
- of any sort. \ No newline at end of file
+ of any sort.