From 194c894d888663843f6aac5475e45952f87fa09c Mon Sep 17 00:00:00 2001 From: Joachim Wiberg Date: Thu, 7 Jan 2021 05:34:39 +0100 Subject: [PATCH] Spell check man pages and README Signed-off-by: Joachim Wiberg --- README.md | 2 +- man/mrouted.8 | 4 ++-- man/mrouted.conf.5 | 6 +++--- 3 files changed, 6 insertions(+), 6 deletions(-) diff --git a/README.md b/README.md index 05555ca..9f06f12 100644 --- a/README.md +++ b/README.md @@ -75,7 +75,7 @@ larger than the default 20. mrouted needs 3x the number of interfaces (vifs) for the relevant control protocol groups. The kernel (Linux & BSD) *maximum* number of interfaces to use for multicast routing is 32. -**Note:** mrouted must run with suffient capabilities, or as root. +**Note:** mrouted must run with sufficient capabilities, or as root. Configuration diff --git a/man/mrouted.8 b/man/mrouted.8 index 9814cc6..aad5d4b 100644 --- a/man/mrouted.8 +++ b/man/mrouted.8 @@ -56,7 +56,7 @@ In order to support multicasting among subnets that are separated by GRE tunnels. However, .Nm includes (built-in) support for IP-in-IP tunnels, which are virtual -point-to-point links between pairs of DVMRP capable rotuers located +point-to-point links between pairs of DVMRP capable routers located anywhere in an internet. IP multicast packets are encapsulated for transmission through tunnels, so that they look like normal unicast datagrams to intervening routers and subnets. The encapsulation is @@ -73,7 +73,7 @@ support for multicast routing by the regular (unicast) routers. suffers from the well-known scaling problems of any distance-vector routing protocol, and does not support hierarchical multicast routing. .Pp -A more common practise today is to set up GRE tunnels between multicast +A more common practice today is to set up GRE tunnels between multicast capable routers and limit .Nm to run on a select number of interfaces listed in the configuration. diff --git a/man/mrouted.conf.5 b/man/mrouted.conf.5 index a2714f7..85ba3e3 100644 --- a/man/mrouted.conf.5 +++ b/man/mrouted.conf.5 @@ -159,7 +159,7 @@ disable all phyint (this setting), and then selectively enable only the ones needed. .It Cm phyint Ar Oo Cm disable | enable Oc Oo Cm passive Oc Oo Cm blaster Oc Oo Cm force-leaf Oc Oo Cm noflood Oc Oo Cm igmpv1 | igmpv2 | igmpv3 Oc Oo Cm static-group Ar group Oc Oo Cm altnet Ar network Ns / Ns Ar mask-len Oc Oo Cm boundary Ar boundary-name | scoped-addr Ns / Ns Ar mask-len Oc Oo Cm metric Ar <1-31> Oc Oo Cm advert-metric Ar <0-31> Oc Oo Cm prune-lifetime Ar sec Oc Oo Cm rexmit-prunes Oo Ar on | off Oc Oc Oo Cm allow-nonpruners Oc Oo Cm notransit Oc Oo Cm accept|deny Po Ar route Ns / Ns Ar mask-len Oo Cm exact Oc Pc Ns + Oo Cm bidir Oc Oc Oo Cm rate-limit Ar kbps Oc Oo Cm threshold Ar ttl Oc .Pp -This setting selects and alters properties of the phyiscal interfaces +This setting selects and alters properties of the physical interfaces .Nm mrouted operates on. Interfaces can be identified using their local IP address or their name. @@ -298,9 +298,9 @@ keyword. If the keyword follows a route, then only that route is matched; otherwise, that route and any more specific route is matched. For example, .Cm deny 0/0 -denys all routes, while +denies all routes, while .Cm deny 0/0 Ar exact -denys only the default route. The default route may also be specified +denies only the default route. The default route may also be specified with the .Cm default keyword.