Fix typos in 04_transpiler_passes_and_passmanager.ipynb (#1494)

Built on top of #1239.

---------

Co-authored-by: Bochen "Daniel" Tan <[email protected]>

Author: Eric-Arellano

tutorials/circuits_advanced/04_transpiler_passes_and_passmanager.ipynb

@@ -797,7 +797,7 @@
    "cell_type": "markdown",
    "metadata": {},
    "source": [
-    "Each node is an instance of the ``DAGOpNode`` class. Let's examine the information stored in the second op node."
+    "Each node is an instance of the ``DAGOpNode`` class. Let's examine the information stored in the fourth op node."
    ]
   },
   {
@@ -1293,7 +1293,7 @@
    "cell_type": "markdown",
    "metadata": {},
    "source": [
-    "The `basicConfig()` function (see the docs here: https://docs.python.org/3/library/logging.html#logging.basicConfig) configures a root handler and formatter. We also specify the [log level](https://docs.python.org/3/library/logging.html#levels) to display with the `level` kwarg. Setting it to a level will also include and higher levels. For example, if you set it to `'INFO'` in addition to the `INFO` level this will also include the `WARNING`, `ERROR`, and `CRITICAL` log levels.\n",
+    "The `basicConfig()` function (see the docs here: https://docs.python.org/3/library/logging.html#logging.basicConfig) configures a root handler and formatter. We also specify the [log level](https://docs.python.org/3/library/logging.html#levels) to display with the `level` kwarg. Setting it to a level will also include and higher levels. For example, if you set it to `'INFO'`, in addition to the `INFO` level, this will also include the `WARNING`, `ERROR`, and `CRITICAL` log levels.\n",
     "\n",
     "Now the python environment in this notebook is configured to emit log messages to stderr when you run the transpiler. For example:"
    ]
@@ -2119,7 +2119,7 @@
    "cell_type": "markdown",
    "metadata": {},
    "source": [
-    "As you can see here we get log messages from all 3 circuits being transpiled together. There is no way to know which pass is part of which circuit's transpilation.  Luckily Python logging provides tools to deal with this. The simplest one is to just change the [log formatter](https://docs.python.org/3/library/logging.html#logging.Formatter) so that includes additional information so we can associate a log message with the process it came from."
+    "As you can see here we get log messages from both circuits being transpiled together. There is no way to know which pass is part of which circuit's transpilation.  Luckily Python logging provides tools to deal with this. The simplest one is to just change the [log formatter](https://docs.python.org/3/library/logging.html#logging.Formatter) so that includes additional information so we can associate a log message with the process it came from."
    ]
   },
   {