Merge pull request #362 from eakman/develop

Found a few other typos and so forth
nornir-automation · Mar 20, 2019 · dc4d94e · dc4d94e
2 parents 5827f4f + 913dcf5
commit dc4d94e
Show file tree

Hide file tree

Showing 4 changed files with 5 additions and 5 deletions.
diff --git a/docs/howto/transforming_inventory_data.ipynb b/docs/howto/transforming_inventory_data.ipynb
@@ -154,7 +154,7 @@
    "cell_type": "markdown",
    "metadata": {},
    "source": [
-    "Now everything we have to do is put the import path as the ``transform_function`` configuration option:"
+    "Now the only thing left to do is put the import path as the ``transform_function`` configuration option:"
    ]
   },
   {

diff --git a/docs/tutorials/intro/failed_tasks.ipynb b/docs/tutorials/intro/failed_tasks.ipynb
@@ -409,7 +409,7 @@
    "cell_type": "markdown",
    "metadata": {},
    "source": [
-    "To achieve this `nornir` keeps a list failed hosts in it's shared [data](../../ref/api/nornir.rst#nornir.core.state.GlobalState) object:"
+    "To achieve this `nornir` keeps a list of failed hosts in it's shared [data](../../ref/api/nornir.rst#nornir.core.state.GlobalState) object:"
    ]
   },
   {

diff --git a/docs/tutorials/intro/grouping_tasks.ipynb b/docs/tutorials/intro/grouping_tasks.ipynb
@@ -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 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:"
    ]
   },
   {

diff --git a/docs/tutorials/intro/task_results.ipynb b/docs/tutorials/intro/task_results.ipynb
@@ -209,7 +209,7 @@
    "cell_type": "markdown",
    "metadata": {},
    "source": [
-    "As you probably noticed, not all the tasks where printed. If you check the tests they all got a new argument `severity_level`. This let's us flag tasks with any of the logging levels. Then `print_result` is able to following logging rules to print the results. By default only tasks marked as `INFO` will be printed (this is also the default for the tasks if none is specified). Note that a failed task will have its severity level changed to `ERROR` regardless of the one specified by the user.\n",
+    "As you probably noticed, not all the tasks were printed. If you check the tests, they all got a new argument `severity_level`. This let's us flag tasks with any of the logging levels. Then `print_result` is able to following logging rules to print the results. By default only tasks marked as `INFO` will be printed (this is also the default for the tasks if none is specified). Note that a failed task will have its severity level changed to `ERROR` regardless of the one specified by the user.\n",
     "\n",
     "Now let's tell `print_result` to print tasks marked as `DEBUG`."
    ]
@@ -298,7 +298,7 @@
    "source": [
     "## The programmatic way\n",
     "\n",
-    "We have hinted already how to deal with result objects already but let's elaborate on that. To begin with, task groups will return an [AggregatedResult](../../ref/api/task.rst#nornir.core.task.AggregatedResult). This object is a dict-like object you can use to iterate over or access directly hosts:"
+    "We have hinted at how to deal with result objects already, but let's elaborate on that. To begin with, task groups will return an [AggregatedResult](../../ref/api/task.rst#nornir.core.task.AggregatedResult). This object is a dict-like object you can use to iterate over or access hosts directly:"
    ]
   },
   {