errors remove a couple notes (#8)

Author: rlanzafame

book/08/error_types.ipynb

@@ -228,15 +228,6 @@
     "The difference between the 2 results is nearly 0.75, which can be very high depending on its use."
    ]
   },
-  {
-   "cell_type": "markdown",
-   "metadata": {},
-   "source": [
-    "```{note}\n",
-    "For now you are only expected to recognize what a logical error is and how it is different than a Syntax error or Exception. When we learn how to address this type of error later, for example when we incorporate tests into our code.\n",
-    "```"
-   ]
-  },
   {
    "cell_type": "markdown",
    "metadata": {},

book/08/handling_errors.ipynb

@@ -7,7 +7,7 @@
     "# Handling errors: the `try - except` block <a id='try_except'></a>\n",
     "If exceptions are not handled properly, the application will crash during execution as we have seen in the examples above. As a result, handling exceptions is important, because we want to minimise application crashes. Sometimes this is called \"catching\" errors.\n",
     "\n",
-    "It is important to also think about *when* we should catch errors: this is when you expect the error to be _recoverable_. In other words, dealing with isthe error should not affect future code that will run. Some errors are _fatal_ and should be left to crash the program since things won't work out anyways (we will learn how to distinguish this behavior in the logging section).\n",
+    "It is important to also think about *when* we should catch errors: this is when you expect the error to be _recoverable_. In other words, dealing with isthe error should not affect future code that will run. Some errors are _fatal_ and should be left to crash the program since things won't work out anyways.\n",
     "\n",
     "To handle exceptions, we can make use of `try - except` block, where we can catch exceptions and handle them in the way we wish. Thus, if an exception is *raised*, the application is not going to crash.\n",
     "\n",