diff --git a/docs/docs/how_to/output_parser_custom.ipynb b/docs/docs/how_to/output_parser_custom.ipynb
index d77e1ff9c6a..1949e3dd067 100644
--- a/docs/docs/how_to/output_parser_custom.ipynb
+++ b/docs/docs/how_to/output_parser_custom.ipynb
@@ -12,7 +12,7 @@
     "There are two ways to implement a custom parser:\n",
     "\n",
     "1. Using `RunnableLambda` or `RunnableGenerator` in [LCEL](/docs/concepts/lcel/) -- we strongly recommend this for most use cases\n",
-    "2. By inherting from one of the base classes for out parsing -- this is the hard way of doing things\n",
+    "2. By inheriting from one of the base classes for out parsing -- this is the hard way of doing things\n",
     "\n",
     "The difference between the two approaches are mostly superficial and are mainly in terms of which callbacks are triggered (e.g., `on_chain_start` vs. `on_parser_start`), and how a runnable lambda vs. a parser might be visualized in a tracing platform like LangSmith."
    ]
@@ -200,7 +200,7 @@
    "id": "24067447-8a5a-4d6b-86a3-4b9cc4b4369b",
    "metadata": {},
    "source": [
-    "## Inherting from Parsing Base Classes"
+    "## Inheriting from Parsing Base Classes"
    ]
   },
   {
@@ -208,7 +208,7 @@
    "id": "9713f547-b2e4-48eb-807f-a0f6f6d0e7e0",
    "metadata": {},
    "source": [
-    "Another approach to implement a parser is by inherting from `BaseOutputParser`, `BaseGenerationOutputParser` or another one of the base parsers depending on what you need to do.\n",
+    "Another approach to implement a parser is by inheriting from `BaseOutputParser`, `BaseGenerationOutputParser` or another one of the base parsers depending on what you need to do.\n",
     "\n",
     "In general, we **do not** recommend this approach for most use cases as it results in more code to write without significant benefits.\n",
     "\n",