small changes

Author: Alexis Cook

notebooks/llmu/Rerank_Endpoint.ipynb

@@ -5,7 +5,7 @@
    "id": "56b0e523",
    "metadata": {},
    "source": [
-    "# Rerank Endpoint\n",
+    "# Reranking Unstructured and Semi-Structured Data\n",
     "\n",
     "Enterprise data is often complex, and current systems have difficulty searching through multi-aspect and semi-structured data sources. The most useful data at companies is not often in simple document format, and semi-structured data formats such as JSON are common across enterprise applications.\n",
     "\n",
@@ -65,7 +65,7 @@
    "source": [
     "## Step 1: Define a JSON Dataset\n",
     "\n",
-    "We begin by creating our dataset, which is a Python list.  Each item is a different email represented as a Python dictionary with five fields. "
+    "We begin by creating our dataset, which is a Python list of JSON objects.  Each JSON object is a different email with five fields. "
    ]
   },
   {
@@ -150,7 +150,7 @@
     "\n",
     "Now we are ready to call the Rerank endpoint, which will help us to find emails that are relevant to a particular query.\n",
     "\n",
-    "We'll begin with a query about pricing from Mircosoft (MS). To pull relevant emails, the model needs to combine information from the `\"to\"` field (e.g., `\"[email protected]\"`) and the `\"text\"` field (e.g., `\"Sorry, but here is the pricing you asked for ...\"`)."
+    "We'll begin with a query about pricing from Microsoft (MS). "
    ]
   },
   {
@@ -168,6 +168,8 @@
    "id": "28664c16",
    "metadata": {},
    "source": [
+    "To pull relevant emails, the model needs to combine information from the `\"to\"` field (e.g., `\"[email protected]\"`) and the `\"text\"` field (e.g., `\"Sorry, but here is the pricing you asked for ...\"`). \n",
+    "\n",
     "We call the Rerank endpoint with `co.rerank()` and use five parameters: \n",
     "- `query` - The query that we will use to find relevant documents\n",
     "- `documents` -  The set of documents (or, in this case, emails) to rerank\n",