Merge pull request #3244 from bobidle/fix_typos

docs: fix typos

docs/dev/uplink.rst

@@ -12,7 +12,7 @@ After the VPN connection has been established, the node should be able to reach
 the mesh's DNS servers and use these for all other name resolution.
 
 If a device has only a single Ethernet port (or group of ports), it will be
-used as an uplink port even when it is not labelled as "WAN" by default. This
+used as an uplink port even when it is not labeled as "WAN" by default. This
 behavior can be controlled using the ``interfaces.single.default_roles``
 site.conf option. It is also possible to alter the interface assignment after
 installation by modifying ``/etc/config/gluon`` and running

docs/package/gluon-mesh-wireless-sae.rst

@@ -34,7 +34,7 @@ wifi.mesh.sae_passphrase \: optional
   - sets a shared secret used to authenticate any two mesh nodes,
     crucial for private mesh networks
   - should not be set, if the shared secret is shared with untrusted
-    third parties, like in a publish mesh network
+    third parties, like in a public mesh network
   - defaults to an autogenerated value derived from ``prefix6``
 
 

docs/releases/v2018.2.1.rst

@@ -47,26 +47,26 @@ Bugfixes
   This was visible on the status page and several map implementations.
   The new implementation uses netlink instead of parsing `/proc/net/if_inet6`.
 
-* Fixes a localization issue in gluon-config-mode-geo-location which 
+* Fixes a localization issue in gluon-config-mode-geo-location which
   resulted in a partial translation of the wizard's location section
   text. (`#1611 <https://github.com/freifunk-gluon/gluon/issues/1611>`_)
 
 * Fixes the display of the improved memory usage estimation in gluon-status-page
 
-  This change was actually already merged in time for v2018.2 but the 
+  This change was actually already merged in time for v2018.2 but the
   JavaScript was not rebuilt.
 
-* Fixes automatic updates for several devices by adding and updating 
+* Fixes automatic updates for several devices by adding and updating
   the autoupdater image names
 
   This affects the following devices:
 
-  * GL.iNet GL-AR150, 
+  * GL.iNet GL-AR150
   * GL.iNet GL-AR300M
   * GL.iNet GL-AR750
   * Raspberry Pi Model B+ Rev 1.2
 
-* Fixes the primary MAC address selection for Unifi AC 
+* Fixes the primary MAC address selection for Unifi AC
   Lite/Mesh/Pro/Mesh Pro (`#1629 <https://github.com/freifunk-gluon/gluon/issues/1629>`_)
 
 * Fixes low data rate selection for multicast and management frames on
@@ -74,7 +74,7 @@ Bugfixes
 
   A patchset has been backported that notifies these drivers of requested data rate changes
 
-* Fixes the data rate selection in ath10k and ath10k-ct when no 
+* Fixes the data rate selection in ath10k and ath10k-ct when no
   `mcast_rate` is configured (`#1657 <https://github.com/freifunk-gluon/gluon/pull/1657>`_)
 
   Previously a missing mcast_rate could result in broken 5 GHz connectivity
@@ -86,7 +86,7 @@ Scheduled domain switch
 ^^^^^^^^^^^^^^^^^^^^^^^
 
 Gluon has support for multiple domains since its v2018.1 release.
-The scheduled domain switch allows for reliable migrations between 
+The scheduled domain switch allows for reliable migrations between
 domains at a preconfigured time.
 This can be useful for communities that, among other things, plan to
 
@@ -98,7 +98,7 @@ Improved frequency band distribution of dual-band radios
 
 A new algorithm that improves the distribution of dual-band radios was
 added. They will now be evenly distributed between the 2.4 and 5 GHz
-band, with a preference towards 2.4 GHz. 
+band, with a preference towards 2.4 GHz.
 
 If a device has only a single dual-band radio, like the AVM FRITZ!WLAN
 Repeater 300E, it will be configured for 2.4 GHz.

docs/releases/v2019.1.rst

@@ -158,7 +158,7 @@ Bugfixes
   (`#1777 <https://github.com/freifunk-gluon/gluon/issues/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 address 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 <https://github.com/freifunk-gluon/gluon/issues/1701>`_)
 
 
@@ -176,7 +176,7 @@ site.mk
 * The variable ``DEVICES`` that controls which devices to build images for has been renamed to ``GLUON_DEVICES``.
   (`#1686 <https://github.com/freifunk-gluon/gluon/pull/1686>`_)
 
-* The ``gluon-radvd`` package is now included by default and can be dropped from *FEATURES* and  *GLUON_SITE_PACKGES*.
+* The ``gluon-radvd`` package is now included by default and can be dropped from *FEATURES* and *GLUON_SITE_PACKAGES*.
 
 site.conf
 =========

docs/user/site.rst

@@ -424,7 +424,7 @@ interfaces \: optional
     },
 
   For devices that have two distinct Ethernet ports or port groups (often
-  labelled WAN and LAN), the ``lan`` and ``wan`` sections are used. When there
+  labeled WAN and LAN), the ``lan`` and ``wan`` sections are used. When there
   is only one port (group), ``single`` is used instead.
 
   Available interface roles:
@@ -658,7 +658,7 @@ flags using a flexible ruleset defined in the Gluon repo or site package feeds.
 To some extent, it will even allow us to further modularize existing Gluon packages,
 without necessitating changes to existing site configurations.
 
-It is still possible to override such automatic rules by removing them using 
+It is still possible to override such automatic rules by removing them using
 *packages* in the ``image-customization.lua`` file
 (e.g., ``features { '-gluon-status-page-mesh-batman-adv' }`` to remove
 the automatically added package *gluon-status-page-mesh-batman-adv*).
@@ -728,7 +728,7 @@ disable_factory()
   Disables factory image generation. Sysupgrade images are still generated and stored in the image
   output directory.
 
-Technically, the image customzation file is evaluated once for each device, allowing
+Technically, the image customization file is evaluated once for each device, allowing
 to make use of regular Lua *if* statements for device-specific configuration as
 can be seen in the example.