diff --git a/docs/docs_skeleton/docs/modules/memory/types/buffer.mdx b/docs/docs_skeleton/docs/modules/memory/types/buffer.mdx
index d417b63174..0ffd152f73 100644
--- a/docs/docs_skeleton/docs/modules/memory/types/buffer.mdx
+++ b/docs/docs_skeleton/docs/modules/memory/types/buffer.mdx
@@ -1,6 +1,6 @@
 # Conversation Buffer
 
-This notebook shows how to use `ConversationBufferMemory`. This memory allows for storing of messages and then extracts the messages in a variable.
+This notebook shows how to use `ConversationBufferMemory`. This memory allows for storing messages and then extracts the messages in a variable.
 
 We can first extract it as a string.
 
diff --git a/docs/extras/guides/debugging.md b/docs/extras/guides/debugging.md
index 2527034dcb..9b23137250 100644
--- a/docs/extras/guides/debugging.md
+++ b/docs/extras/guides/debugging.md
@@ -2,7 +2,7 @@
 
 If you're building with LLMs, at some point something will break, and you'll need to debug. A model call will fail, or the model output will be misformatted, or there will be some nested model calls and it won't be clear where along the way an incorrect output was created.
 
-Here's a few different tools and functionalities to aid in debugging.
+Here are a few different tools and functionalities to aid in debugging.
 
 
 
@@ -18,9 +18,9 @@ For anyone building production-grade LLM applications, we highly recommend using
 
 If you're prototyping in Jupyter Notebooks or running Python scripts, it can be helpful to print out the intermediate steps of a Chain run. 
 
-There's a number of ways to enable printing at varying degrees of verbosity.
+There are a number of ways to enable printing at varying degrees of verbosity.
 
-Let's suppose we have a simple agent and want to visualize the actions it takes and tool outputs it receives. Without any debugging, here's what we see:
+Let's suppose we have a simple agent, and want to visualize the actions it takes and tool outputs it receives. Without any debugging, here's what we see:
 
 
 ```python
diff --git a/docs/extras/integrations/vectorstores/zep.ipynb b/docs/extras/integrations/vectorstores/zep.ipynb
index 0354da3210..4456aece0b 100644
--- a/docs/extras/integrations/vectorstores/zep.ipynb
+++ b/docs/extras/integrations/vectorstores/zep.ipynb
@@ -167,7 +167,7 @@
       "Tables necessary to determine the places of the planets are not less\r\n",
       "necessary than those for the sun, moon, and stars. Some notion of the\r\n",
       "number and complexity of these tables may be formed, when we state that\r\n",
-      "the positions of the two principal planets, (and these the most\r\n",
+      "the positions of the two principal planets, (and these are the most\r\n",
       "necessary for the navigator,) Jupiter and Saturn, require each not less\r\n",
       "than one hundred and sixteen tables. Yet it is not only necessary to\r\n",
       "predict the position of these bodies, but it is likewise expedient to  ->  0.8998482592744614 \n",