corrected spelling

dotnet/notebooks/10-Agentic-tutorial.ipynb

@@ -380,7 +380,7 @@
    "cell_type": "markdown",
    "metadata": {},
    "source": [
-    "With the function delared, let's try it out! Make the prompt anything you want below. This is a good opportunity to play with image generation prompts to get a better feel for the system. Learnings from this section can directly translate to better engineered prompts within your agentic system, since you can help the LLM agent learn how you prefer to prompt image generation tools."
+    "With the function declared, let's try it out! Make the prompt anything you want below. This is a good opportunity to play with image generation prompts to get a better feel for the system. Learnings from this section can directly translate to better engineered prompts within your agentic system, since you can help the LLM agent learn how you prefer to prompt image generation tools."
    ]
   },
   {
@@ -548,7 +548,7 @@
    "cell_type": "markdown",
    "metadata": {},
    "source": [
-    "Lets exctract the following data from the above table:\n",
+    "Lets extract the following data from the above table:\n",
     "\n",
     "Filter by time (lookback)\n",
     "\n",

dotnet/notebooks/11-RAG with sliding window.ipynb

@@ -55,7 +55,7 @@
     "\n",
     "The way it works is: \n",
     "1. Add your own knowledge (in the form of documents or data snippets) to a vector database\n",
-    "2. Call that database to extract relevent data when the LLM is called\n",
+    "2. Call that database to extract relevant data when the LLM is called\n",
     "3. Feed your data into the LLM's prompt alongside the user query\n",
     "\n",
     "Knowing the specifics of vector retrieval is outside the scope of this exercise, but at a broad level, it is not a simple string match. Instead, searching vector space enables searching for _semantic_ similarities, or searching by meaning instead of specific text."
@@ -127,7 +127,7 @@
    "id": "2f7ef1a0",
    "metadata": {},
    "source": [
-    "1. Instanciate Embeddings"
+    "1. Instantiate Embeddings"
    ]
   },
   {
@@ -496,6 +496,9 @@
    "execution_count": 15,
    "id": "a05a090f",
    "metadata": {
+    "polyglot_notebook": {
+     "kernelName": "csharp"
+    },
     "vscode": {
      "languageId": "polyglot-notebook"
     }
@@ -517,9 +520,12 @@
   },
   {
    "cell_type": "code",
-   "execution_count": 16,
+   "execution_count": null,
    "id": "5a00277a",
    "metadata": {
+    "polyglot_notebook": {
+     "kernelName": "csharp"
+    },
     "vscode": {
      "languageId": "polyglot-notebook"
     }
@@ -538,7 +544,7 @@
     "// 1. Create collection\n",
     "\n",
     "var createCollectionUrl = $\"{qdrantUrl}/collections/{collectionName}\";\n",
-    "//Side of each vector in the colleciton\n",
+    "//Side of each vector in the collection\n",
     "// The size of the vector must match the dimension of your vectors\n",
     "var embeddingSize = 1536; //\n",
     "\n",
@@ -602,6 +608,9 @@
    "execution_count": 18,
    "id": "df51e725",
    "metadata": {
+    "polyglot_notebook": {
+     "kernelName": "csharp"
+    },
     "vscode": {
      "languageId": "polyglot-notebook"
     }
@@ -631,7 +640,7 @@
    "id": "af10c328",
    "metadata": {},
    "source": [
-    "Retreive chunks most similar to the user question"
+    "Retrieve chunks most similar to the user question"
    ]
   },
   {

dotnet/notebooks/config/long_document.txt

@@ -18,7 +18,7 @@ Small, common fragments or strings proceeded by complex BM escape sequences shou
 
 Using the same strings, or subsets of the same strings will cause multiple hits and can cause false positives.
 e.g. {1, s'Explorer'}, {1, s'Internet Explorer'},
-Ensure code fragments are unique and likely to appear in future variants. As a good rule of thumb, if you can't explain what it does in your comments, then probably don't use it. There is a high likelyhood of library code.
+Ensure code fragments are unique and likely to appear in future variants. As a good rule of thumb, if you can't explain what it does in your comments, then probably don't use it. There is a high likelihood of library code.
 
 Smaller, precise fragments are preferred over slabs of code
 
@@ -105,7 +105,7 @@ d - 'dynamic'. That is, the attribute/string must be matched in 'dynamically' al
 r - 'RPF'. That is, when the attribute/string is matched, we'll invoke all the routines in the database matching the routine type __RPF_ROUTINEID_HSTR_LOGIC__. a RPF routine gets the ID of the string matched and can do extra checks to 'validate' the match (freedom is the middle name 😃)
 c - 'code': this modifier is matched on fragments found in pages allocated specifically with PAGE_EXECUTE during emulation. This should help for short fragments where you explicitly want to match them in the code.
 o - collect the match offsets for each escape. See Lua hstr for more details.
-m - save the macro source to make it avaliable in Lua. Macro only. See Lua hstr.
+m - save the macro source to make it available in Lua. Macro only. See Lua hstr.
 G - force include the fragment. The compiler checks the fragment to not be too weak (e.g. 'exe') or perf killer. With this modifier the compiler check is bypassed. Use with care.
 string - The string to match.  By default, this is matched case-insensitively.  These string may contain binary data (using the '\x<hex value>' escape sequence and other C-like escape sequences.