Feature/reenable macos tests

.github/workflows/tests.yml

@@ -23,7 +23,7 @@ jobs:
           - { python: "3.9", os: "ubuntu-latest", session: "tests" }
           - { python: "3.8", os: "ubuntu-latest", session: "tests" }
           - { python: "3.11", os: "windows-latest", session: "tests" }
-          # - { python: "3.11", os: "macos-latest", session: "tests" }
+          - { python: "3.11", os: "macos-latest", session: "tests" }
           - { python: "3.11", os: "ubuntu-latest", session: "typeguard" }
           - { python: "3.11", os: "ubuntu-latest", session: "xdoctest" }
           - { python: "3.11", os: "ubuntu-latest", session: "docs-build" }

README.rst

@@ -70,7 +70,7 @@ When you install *Parasect* via pip_ its requirements will also be installed aut
 
 Currently *Parasect* has been tested:
 
-* in Continuous Integration servers for **Ubuntu Linux**, **Windows**
+* in Continuous Integration servers for **Ubuntu Linux**, **Windows** and **MacOS**.
 * manually in **Ubuntu Linux**.
 
 

docs/usage_ardupilot.rst

@@ -259,7 +259,7 @@ Still, they clutter the comparison. Let's use the ``-s`` option to ignore them.
     0 parameters differ
 
 Great! The produced parameter file is exactly as we wanted it!
-We can write it in our UAV as many times as we want to reset the parameters to their intended values, without fear of overwritign the calibration!
+We can write it in our UAV as many times as we want to reset the parameters to their intended values, without fear of overwriting the calibration!
 
 Another UAV Variant
 -------------------
@@ -343,7 +343,7 @@ Let's build the files anew and compare them.
 
 Excellent! That's just what we wanted!
 
-Let's give this new airframe to a friend! He needs a platform to brush up his flyig skills.
+Let's give this new airframe to a friend! He needs a platform to brush up his flying skills.
 
 Read-Only Parameters
 --------------------
@@ -413,7 +413,7 @@ Unfortunately, *apj_tool* can fit only 8 kilobytes of parameters in the ``.apj``
 
 We have to make a concession and strip our parameter file from the default parameters.
 The downside is that we can no longer use the same parameter file with our GCS to reset all the parameters to the intended value.
-But we can easily circumvent this issue by simply creating a parameter file exclusively for this use, and explicity setting defaults to ``None``.
+But we can easily circumvent this issue by simply creating a parameter file exclusively for this use, and explicitly setting defaults to ``None``.
 
 .. code-block:: yaml
     :caption: meals.yaml
@@ -462,7 +462,7 @@ The resulting parameter set is, as expected:
     MIS_OPTIONS	0
 
 We can now bake in the parameters in our ``.apj`` file with the `apj_tool`_.
-We assume that ``arducopter.apj`` and ``apj_tool.py`` has been copied into ``parasect_files``.
+We assume that ``arducopter.apj`` and ``apj_tool.py`` have been copied into ``parasect_files``.
 
 .. code-block:: bash
 

docs/usage_create_menu.rst

@@ -56,8 +56,8 @@ Finally, the third item is a string, where you can document why you chose to inc
    .. code:: yaml
 
       common:
-      ingredients:
-         - [RC\d+_TRIM, ~, Disregard channel trim values]
+         ingredients:
+            - [RC\d+_TRIM, ~, Disregard channel trim values]
 
 ``operator.yaml``: This is a Dish (with the usual Dish syntax) that contains the names of the operator parameters
 of your autopilot. List those parameters here to: a) not take them into account when comparing parameter sets and b)