summaryrefslogtreecommitdiffstats
path: root/doc
diff options
context:
space:
mode:
authorChristof Schulze <christof.schulze@gmx.net>2016-11-21 00:46:41 +0100
committerMatthias Schiffer <mschiffer@universe-factory.net>2016-11-21 10:22:42 +0100
commit441107e4165fe4af80764fee4d2b7fcd8f731c3d (patch)
treea89ab04b8b53b2d29afe65af9f5190113d7bdf73 /doc
parent2fa2187e68d24648bf77780aaf72c5708681632d (diff)
downloadfastd-441107e4165fe4af80764fee4d2b7fcd8f731c3d.tar
fastd-441107e4165fe4af80764fee4d2b7fcd8f731c3d.zip
typo: there is no word >chosed<, should be >chosen<.
Diffstat (limited to 'doc')
-rw-r--r--doc/source/manual/mtu.rst2
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/source/manual/mtu.rst b/doc/source/manual/mtu.rst
index 395a707..22bfb1a 100644
--- a/doc/source/manual/mtu.rst
+++ b/doc/source/manual/mtu.rst
@@ -4,7 +4,7 @@ The default MTU of fastd is 1500. This allows briding the fastd interface in TAP
mode with other interface with the same MTU, but will usually cause fastd's UDP
packets to be fragmented. Fragmentation can lower the
performance or even cause connectivity problems when broken routers filter ICMP packets,
-so if possible the MTU should be chosed small enough so that IP fragmentation can be avoided.
+so if possible the MTU should be chosen small enough so that IP fragmentation can be avoided.
Unlike OpenVPN, fastd doesn't support fragmentation itself, but relies on the IP stack to fragment packets when necessary.
Guidelines