spelling fixes (#389)

docs/plugins/tasks/version_control/gitlab.ipynb

@@ -84,9 +84,9 @@
     "\n",
     "In this example we will create a new file in a git repository on a gitlab server.\n",
     "\n",
-    "The contents that we will write to the file is a arbitary string, in a real world scenario this could be the running configuration of a device that we fetched using napalm or through another method.\n",
+    "The contents that we will write to the file is a arbitrary string, in a real world scenario this could be the running configuration of a device that we fetched using napalm or through another method.\n",
     "\n",
-    "First let's import the necessary methods & tasks, then we will create a variable called `content` which is an arbitary string."
+    "First let's import the necessary methods & tasks, then we will create a variable called `content` which is an arbitrary string."
    ]
   },
   {
@@ -334,7 +334,7 @@
     }
    },
    "source": [
-    "In this example we will update the contents of the hosts file that we created in the previous step. The new contents could come again from a remote host or device, but in this case we will use an arbitary value for the new contents of the file."
+    "In this example we will update the contents of the hosts file that we created in the previous step. The new contents could come again from a remote host or device, but in this case we will use an arbitrary value for the new contents of the file."
    ]
   },
   {

docs/tutorials/intro/grouping_tasks.ipynb

@@ -207,7 +207,7 @@
    "source": [
     "As you can see, pretty straightforward. We just call the function we defined earlier grouping the tasks we wanted to execute and then we leverage on `functions.text.print_title` and `tasks.text.print_result` to make things look pretty.\n",
     "\n",
-    "However, this was a `dry_run`. Let's set the `dry_run` variable to `False` so changes are commited and then run the code again:\n",
+    "However, this was a `dry_run`. Let's set the `dry_run` variable to `False` so changes are committed and then run the code again:\n",
     "\n",
     "<div class=\"alert alert-info\">\n",
     "**Note:** The `dry_run` value is shared between the main nornir objects and its children so in the snippet below `nr.data.dry_run = False` and `cmh.data.dry_run = False` are equivalent.\n",
@@ -300,7 +300,7 @@
    "cell_type": "markdown",
    "metadata": {},
    "source": [
-    "As the configuration should've been commited already, if we run it again the task \"Loading Configuration on the device\" should tell us that `changed : False` and should return an empty diff. Let's see if that's true:"
+    "As the configuration should've been committed already, if we run it again the task \"Loading Configuration on the device\" should tell us that `changed : False` and should return an empty diff. Let's see if that's true:"
    ]
   },
   {

nornir/core/__init__.py

@@ -90,7 +90,7 @@ def run(
         Arguments:
             task (``callable``): function or callable that will be run against each device in
               the inventory
-            num_workers(``int``): Override for how many hosts to run in paralell for this task
+            num_workers(``int``): Override for how many hosts to run in parallel for this task
             raise_on_error (``bool``): Override raise_on_error behavior
             on_good(``bool``): Whether to run or not this task on hosts marked as good
             on_failed(``bool``): Whether to run or not this task on hosts marked as failed

nornir/core/inventory.py

@@ -128,7 +128,7 @@ def items(self):
         return self._resolve_data().items()
 
     def has_parent_group(self, group):
-        """Retuns whether the object is a child of the :obj:`Group` ``group``"""
+        """Returns whether the object is a child of the :obj:`Group` ``group``"""
         if isinstance(group, str):
             return self._has_parent_group_by_name(group)