summaryrefslogtreecommitdiff
path: root/doc/api/dgram.md
diff options
context:
space:
mode:
Diffstat (limited to 'doc/api/dgram.md')
-rw-r--r--doc/api/dgram.md4
1 files changed, 2 insertions, 2 deletions
diff --git a/doc/api/dgram.md b/doc/api/dgram.md
index 38d9492be8..ef8cc69b7d 100644
--- a/doc/api/dgram.md
+++ b/doc/api/dgram.md
@@ -449,13 +449,13 @@ client.connect(41234, 'localhost', (err) => {
The maximum size of an `IPv4/v6` datagram depends on the `MTU`
(_Maximum Transmission Unit_) and on the `Payload Length` field size.
-- The `Payload Length` field is `16 bits` wide, which means that a normal
+* The `Payload Length` field is `16 bits` wide, which means that a normal
payload exceed 64K octets _including_ the internet header and data
(65,507 bytes = 65,535 − 8 bytes UDP header − 20 bytes IP header);
this is generally true for loopback interfaces, but such long datagram
messages are impractical for most hosts and networks.
-- The `MTU` is the largest size a given link layer technology can support for
+* The `MTU` is the largest size a given link layer technology can support for
datagram messages. For any link, `IPv4` mandates a minimum `MTU` of `68`
octets, while the recommended `MTU` for IPv4 is `576` (typically recommended
as the `MTU` for dial-up type applications), whether they arrive whole or in