Update doc/guide/Guide_Exception_Logging.ipynb

Co-authored-by: leonie-villiger <[email protected]>

doc/guide/Guide_Exception_Logging.ipynb

@@ -151,7 +151,7 @@
     "- In CLIMADA, you cannot use printing. Any output must go into the LOGGER. \n",
     "\n",
     "\n",
-    "- For any logging messages, always think about the audience. What would a user or developer need for information? This also implies to carefully think about the correct LOGGER level. For instance, some information is for debugging, then use the debug level. In this case, make sure that the message actually helps the debugging process! Some message might just to inform the user about certain default parameters, then use the inform level. See below for more details about logger levels.\n",
+    "- For any logging messages, always think about the audience. What would a user or developer need for information? This also implies to carefully think about the correct LOGGER level. For instance, some information is for debugging, then use the debug level. In this case, make sure that the message actually helps the debugging process! Some message might just inform the user about certain default parameters, then use the inform level. See below for more details about logger levels.\n",
     "\n",
     "\n",
     "- Do not overuse the LOGGER. Think about which level of logging. Logging errors must be useful for debugging."