From adf9b2cab7b64b22c15fc494584dece43e65c023 Mon Sep 17 00:00:00 2001 From: Dimitri Staessens Date: Sat, 2 May 2020 15:12:25 +0200 Subject: content: Fix network byte order --- content/en/blog/news/20200502-frcp.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'content/en/blog') diff --git a/content/en/blog/news/20200502-frcp.md b/content/en/blog/news/20200502-frcp.md index 094565e..28c5794 100644 --- a/content/en/blog/news/20200502-frcp.md +++ b/content/en/blog/news/20200502-frcp.md @@ -233,4 +233,4 @@ Dimitri [^1]: Don't you love standards? One of the key design objectives for Ouroboros is exactly to avoid such shenanigans. Modify/abuse a header and Ouroboros should reject it because it _cannot work_, not because some standard says one shouldn't do it. [^2]: Lesser known fact: Gigabit Ethernet has a 512 byte minimum frame size; but _carrier extension_ handles this transparently. -[^3]: As you have figured out, the loopback is not in _network byte order_. \ No newline at end of file +[^3]: In _network byte order_. \ No newline at end of file -- cgit v1.2.3