From 8553254867fa183915a2a0e640c50a62dd8b9cf6 Mon Sep 17 00:00:00 2001 From: bobcanthelpyou Date: Thu, 26 Sep 2019 04:16:38 +0200 Subject: [PATCH] docs: fix typos --- docs/package/gluon-hoodselector.rst | 4 ++-- docs/package/gluon-mesh-batman-adv.rst | 2 +- docs/releases/v2019.1.rst | 4 ++-- docs/user/site.rst | 4 ++-- 4 files changed, 7 insertions(+), 7 deletions(-) diff --git a/docs/package/gluon-hoodselector.rst b/docs/package/gluon-hoodselector.rst index 2600fc0f..13054924 100644 --- a/docs/package/gluon-hoodselector.rst +++ b/docs/package/gluon-hoodselector.rst @@ -36,7 +36,7 @@ example of a regional domain: Behaviour ------------------ -The following is an abstract state diagramm which gives an overview +The following is an abstract state diagram which gives an overview of the process: .. image:: ./gluon-hoodselector.svg @@ -61,7 +61,7 @@ It provides a fallback to the default domain. Domain shapes ------------- -There are two types of domains: the unique dehault one without a defined shape +There are two types of domains: the unique default one without a defined shape and others which contain shapes. * **default domain** diff --git a/docs/package/gluon-mesh-batman-adv.rst b/docs/package/gluon-mesh-batman-adv.rst index 70b55df7..29135324 100644 --- a/docs/package/gluon-mesh-batman-adv.rst +++ b/docs/package/gluon-mesh-batman-adv.rst @@ -61,7 +61,7 @@ Furthermore, by default IGMP and MLD messages are filtered. See :ref:`site.conf mesh section ` and :ref:`igmp-mld-domain-segmentation` for details. -To achieve some level of scalabilty for multicast, multicast group +To achieve some level of scalability for multicast, multicast group awareness is implemented and utilized in the following ways: Node-Local Multicast Handling diff --git a/docs/releases/v2019.1.rst b/docs/releases/v2019.1.rst index 1cd4f65c..9c1ce60b 100644 --- a/docs/releases/v2019.1.rst +++ b/docs/releases/v2019.1.rst @@ -91,7 +91,7 @@ to decide which module gets loaded and the scheduled domain switching functional the two versions. Note that if you were using ``gluon-mesh-batman-adv-14`` ("batman-adv-legacy") before you will need to update the -``mesh.batman_adv.routing_algo`` setting from from ``BATMAN_IV`` to ``BATMAN_IV_LEGACY`` if you want to +``mesh.batman_adv.routing_algo`` setting from ``BATMAN_IV`` to ``BATMAN_IV_LEGACY`` if you want to stay on v14 compat. See the :ref:`mesh ` section for the *site.conf* configuration of this feature. @@ -157,7 +157,7 @@ Bugfixes (`#1777 `_) * Fixes cross-domain leakage of respondd data by not joining the link-local multicast group on br-client. Nodes will - not be answering respondd queries on ``[ff02::2:1001]:1001`` anymore. Respondd queries using that adresss must be + not be answering respondd queries on ``[ff02::2:1001]:1001`` anymore. Respondd queries using that address must be updated to the new address ``[ff05::2:1001]:1001``. (`#1701 `_) diff --git a/docs/user/site.rst b/docs/user/site.rst index 0aabbc9c..c60f4d86 100644 --- a/docs/user/site.rst +++ b/docs/user/site.rst @@ -169,8 +169,8 @@ wifi5 \: optional Same as `wifi24` but for the 5Ghz radio. Additionally a range of channels that are safe to use outsides on the 5 GHz band can - be set up through ``outdoor_chanlist``, which allows for a space-seperated list of - channels and channel ranges, seperated by a hyphen. + be set up through ``outdoor_chanlist``, which allows for a space-separated list of + channels and channel ranges, separated by a hyphen. When set this offers the outdoor mode flag for 5 GHz radios in the config mode which reconfigures the AP to select its channel from outdoor chanlist, while respecting regulatory specifications, and disables mesh on that radio.