diff --git a/examples/Assistants_API_overview_python.ipynb b/examples/Assistants_API_overview_python.ipynb
index 6051147..c3a52c4 100644
--- a/examples/Assistants_API_overview_python.ipynb
+++ b/examples/Assistants_API_overview_python.ipynb
@@ -7,6 +7,13 @@
     "# Assistants API Overview (Python SDK)"
    ]
   },
+  {
+   "cell_type": "markdown",
+   "metadata": {},
+   "source": [
+    "The new [Assistants API](https://platform.openai.com/docs/assistants/overview) is a stateful evolution of our [Chat Completions API](https://platform.openai.com/docs/guides/text-generation/chat-completions-api) meant to simplify the creation of assistant-like experiences, and enable developer access to powerful tools like Code Interpreter and Retrieval."
+   ]
+  },
   {
    "cell_type": "markdown",
    "metadata": {},
@@ -18,9 +25,6 @@
    "cell_type": "markdown",
    "metadata": {},
    "source": [
-    "\n",
-    "The new [Assistants API](https://platform.openai.com/docs/assistants/overview) is a stateful evolution of our [Chat Completions API](https://platform.openai.com/docs/guides/text-generation/chat-completions-api) meant to simplify the creation of assistant-like experiences, and enable developer access to powerful tools like Code Interpreter and Retrieval.\n",
-    "\n",
     "## Chat Completions API vs Assistants API\n",
     "\n",
     "The primitives of the **Chat Completions API** are `Messages`, on which you perform a `Completion` with a `Model` (`gpt-3.5-turbo`, `gpt-4`, etc). It is lightweight and powerful, but inherently stateless, which means you have to manage conversation state, tool definitions, retrieval documents, and code execution manually.\n",
diff --git a/images/assistants_overview_diagram.png b/images/assistants_overview_diagram.png
index 5720443..3ac068a 100644
Binary files a/images/assistants_overview_diagram.png and b/images/assistants_overview_diagram.png differ