more work tidying up the exercises

Author: erikhatcher

docs/30_Index_configuration/8_Exercises/1_.mdx

@@ -126,7 +126,7 @@ What numeric value can be used to match one of the documents?
 
 <Playground url="https://search-playground.corp.mongodb.com/tools/code-sandbox/snapshots/679c2313d0df60f0254e5d31">🔗 Playground link:  `range`</Playground>
 
-There are *two* issues to fix in this exercises. What's the correct field name? And what's wrong with 
+There are *two* issues to fix in this exercise. What's the correct field name? And what's wrong with 
 the one of the range values?
 
 <details>

docs/40_Analysis/8_Exercises/2_.mdx

@@ -1,15 +1,17 @@
 # Exercises: English
 
-Adjust the index configuration without touching the pipeline or query
+<Playground url="https://search-playground.corp.mongodb.com/tools/code-sandbox/snapshots/679c721ee97570c2714a07ee">🔗 Playground link: "searches" query does not match "Search"</Playground>
+
+Adjust the index configuration without touching the pipeline or query.
+The default `lucene.standard` does basic, language-insensitive, analysis. There's a better language-specific analyzer choice that will solve this challenge.
 
-<Playground url="https://search-playground.corp.mongodb.com/tools/code-sandbox/snapshots/679c721ee97570c2714a07ee">“searches” query does not match “Search” with `lucene.standard`</Playground>
 <details>
   <summary>Solution</summary>
   <div>
     ```js
     "analyzer": "lucene.english"
     ```
-    <Playground url="https://search-playground.corp.mongodb.com/tools/code-sandbox/snapshots/679c3f2ae97570c2714a07ea">solution using `lucene.english` analyzer</Playground>
+    🔗 <Playground url="https://search-playground.corp.mongodb.com/tools/code-sandbox/snapshots/679c3f2ae97570c2714a07ea">solution using `lucene.english` analyzer</Playground>
   </div>
 </details>
 

docs/40_Analysis/8_Exercises/3_.mdx

@@ -1,20 +1,12 @@
-# Exercises: Various languages
+# Exercises: Non-English languages
 
-<Playground url="https://search-playground.corp.mongodb.com/tools/code-sandbox/snapshots/679c70b3d0df60f0254e5d43">configure an appropriate analyzer</Playground>
+<Playground url="https://search-playground.corp.mongodb.com/tools/code-sandbox/snapshots/679c70b3d0df60f0254e5d43">🔗 Playground link: configure an appropriate analyzer</Playground>
 <details>
   <summary>Solution</summary>
   <div>
     ```js
     "analyzer": "lucene.portuguese"
     ```
-    <Playground url="https://search-playground.corp.mongodb.com/tools/code-sandbox/snapshots/679c7123d0df60f0254e5d45">solution using the `lucene.portuguese` analyzer</Playground>
+    🔗 <Playground url="https://search-playground.corp.mongodb.com/tools/code-sandbox/snapshots/679c7123d0df60f0254e5d45">solution using the `lucene.portuguese` analyzer</Playground>
   </div>
 </details>
-
-## TODO
-
-Add more language examples:
-  * Chinese
-  * Diacritic handling (spanish)
-  * Arabic: https://search-playground.mongodb.com/tools/code-sandbox/snapshots/67c8851a5bc7a2f8060be53f
-  

docs/50_Querying/8_Exercises/1_.mdx

@@ -5,27 +5,30 @@ in looser/fuzzier ways, then tackle these exercises.
 
 # matchCriteria
 
-Loosen up this query so the document matches: <Playground url="https://search-playground.corp.mongodb.com/tools/code-sandbox/snapshots/679c8e77e97570c2714a07f2">all terms do no match</Playground> 
+<Playground url="https://search-playground.corp.mongodb.com/tools/code-sandbox/snapshots/679c8e77e97570c2714a07f2">🔗 Playground link: all terms do no match</Playground> 
+
+Loosen up this query so the document matches.
+
 <details>
   <summary>Solution</summary>
   <div>
     ```js
     "matchCriteria": "any"
     ```
-    <Playground url="https://search-playground.corp.mongodb.com/tools/code-sandbox/snapshots/679c8ef8e97570c2714a07f4">solution</Playground>
+    <Playground url="https://search-playground.corp.mongodb.com/tools/code-sandbox/snapshots/679c8ef8e97570c2714a07f4">🔗 solution</Playground>
   </div>
 </details>
 
 
 # fuzzy
 
-<Playground url="https://search-playground.corp.mongodb.com/tools/code-sandbox/snapshots/679c915dd0df60f0254e5d51">Adjust the `text` operator settings so that this document matches</Playground>
+<Playground url="https://search-playground.corp.mongodb.com/tools/code-sandbox/snapshots/679c915dd0df60f0254e5d51">🔗 Playground link: Adjust the `text` operator settings so that this document matches</Playground>
 <details>
   <summary>Solution</summary>
   <div>
     ```js
     "fuzzy": {}
     ```
   </div>
-  <Playground url="https://search-playground.mongodb.com/tools/code-sandbox/snapshots/67b58ffb3cface474919d054">solution</Playground>
+  <Playground url="https://search-playground.mongodb.com/tools/code-sandbox/snapshots/67b58ffb3cface474919d054">🔗 solution</Playground>
 </details>

docs/50_Querying/8_Exercises/2_.mdx

@@ -4,7 +4,7 @@ Phrases match terms in proximity to one another, either exact order with no word
 
 HINT: See the [`phrase` operator docs](https://www.mongodb.com/docs/atlas/atlas-search/phrase/) for these exercises.
 
-Fix this <Playground url="https://search-playground.corp.mongodb.com/tools/code-sandbox/snapshots/679c8ff7e97570c2714a07f8">not close enough phrase match</Playground> 
+<Playground url="https://search-playground.corp.mongodb.com/tools/code-sandbox/snapshots/679c8ff7e97570c2714a07f8">🔗 Playground link: not close enough phrase match</Playground> 
 <details>
   <summary>Solution</summary>
   <div>
@@ -16,10 +16,6 @@ Fix this <Playground url="https://search-playground.corp.mongodb.com/tools/code-
     But you can't adjust what the users query for, so the configuration or search operators need
     to be adjusted.
 
-    <Playground url="https://search-playground.corp.mongodb.com/tools/code-sandbox/snapshots/679c909ad0df60f0254e5d49">solution using phrase `slop`</Playground>
+    <Playground url="https://search-playground.corp.mongodb.com/tools/code-sandbox/snapshots/679c909ad0df60f0254e5d49">🔗 solution using phrase `slop`</Playground>
   </div>
 </details>
-
-# TODO
-
-There's another setting than "slop" which allows out of order. It looks like we need to add it to the exercise/solution

docs/50_Querying/8_Exercises/3_.mdx

@@ -2,7 +2,7 @@
 
 ## `wildcard`
 
-<Playground url="https://search-playground.mongodb.com/tools/code-sandbox/snapshots/67d1e0cd20b1632e508742aa">words that starts-with not matching as expected</Playground>
+<Playground url="https://search-playground.mongodb.com/tools/code-sandbox/snapshots/67d1e0cd20b1632e508742aa">🔗 Playground link: words that starts-with not matching as expected</Playground>
 <details>
   <summary>Solution</summary>
   <div>
@@ -13,13 +13,13 @@
 
   And `allowAnalyzedField: true` needs to be set, allowing searches when using a tokenizing analyzer.
 
-  <Playground url="https://search-playground.corp.mongodb.com/tools/code-sandbox/snapshots/67d1e0f5643f61797f19d31b">solution</Playground>
+  <Playground url="https://search-playground.corp.mongodb.com/tools/code-sandbox/snapshots/67d1e0f5643f61797f19d31b">🔗 solution</Playground>
   </div>
 </details>
 
 ## ``regex``
 
-<Playground url="https://search-playground.corp.mongodb.com/tools/code-sandbox/snapshots/67d1dff6643f61797f19d319">Full string regex not working as expected</Playground>
+<Playground url="https://search-playground.corp.mongodb.com/tools/code-sandbox/snapshots/67d1dff6643f61797f19d319">🔗 Playground link: Full string regex not working as expected</Playground>
 <details>
   <summary>Solution</summary>
   <div>
@@ -29,7 +29,7 @@
   Matching needs to occur across the full string, and thus needs to be `lucene.keyword`
   analyzed so that the full string is indexed as a single unit.
 
-  <Playground url="https://search-playground.mongodb.com/tools/code-sandbox/snapshots/679caadcd0df60f0254e5d62">solution</Playground>
+  <Playground url="https://search-playground.mongodb.com/tools/code-sandbox/snapshots/679caadcd0df60f0254e5d62">🔗 solution</Playground>
   </div>
 </details>
 

docs/60_Relevancy/8_Exercises.mdx

@@ -2,24 +2,28 @@
 
 ## project the score
 
+<Playground url="https://search-playground.mongodb.com/tools/code-sandbox/snapshots/67d2ef3c808223b17a90bd7a">🔗 Playground link: score not projected</Playground>
+
 Fix this Playground so that the `score` being projected is the relevancy score Atlas Search uses for default sorting.
 
-<Playground url="https://search-playground.mongodb.com/tools/code-sandbox/snapshots/67d2ef3c808223b17a90bd7a">score not projected</Playground>
 <details>
   <summary>Solution</summary>
   <div>
     The score is available in the pipeline `$meta` context as `searchScore`. 
     ```js
     {"$meta": "searchScore"}
     ```
-    <Playground url="https://search-playground.mongodb.com/tools/code-sandbox/snapshots/67d2ef7e643f61797f19d33e">solution</Playground>
+    <Playground url="https://search-playground.mongodb.com/tools/code-sandbox/snapshots/67d2ef7e643f61797f19d33e">🔗 solution</Playground>
   </div>
 </details>
 
 
 ## project the score details
 
-<Playground url="https://search-playground.mongodb.com/tools/code-sandbox/snapshots/67d2ee9b643f61797f19d33c">add the score details into the results</Playground>
+<Playground url="https://search-playground.mongodb.com/tools/code-sandbox/snapshots/67d2ee9b643f61797f19d33c">🔗 Playground link: add the score details into the results</Playground>
+
+Enable the score details and project them into the results.
+
 <details>
   <summary>Solution</summary>
   <div>
@@ -34,13 +38,16 @@ Fix this Playground so that the `score` being projected is the relevancy score A
       "$meta": "searchScoreDetails"
     }
     ```
-    <Playground url="https://search-playground.mongodb.com/tools/code-sandbox/snapshots/67d2eec2808223b17a90bd78">solution</Playground>
+    <Playground url="https://search-playground.mongodb.com/tools/code-sandbox/snapshots/67d2eec2808223b17a90bd78">🔗 solution</Playground>
   </div>
 </details>
 
 ## score/sort by the `weight` field
 
-<Playground url="https://search-playground.corp.mongodb.com/tools/code-sandbox/snapshots/67d2eddb643f61797f19d33a">task: set the search (relevance) score to the value of our custom `weight` field</Playground>
+<Playground url="https://search-playground.corp.mongodb.com/tools/code-sandbox/snapshots/67d2eddb643f61797f19d33a">🔗 Playground link: task: score documents by document field</Playground>
+
+Set the search (relevance) score to the value of the `weight` field.
+
 <details>
   <summary>Solution</summary>
   <div>
@@ -52,6 +59,6 @@ Fix this Playground so that the `score` being projected is the relevancy score A
       }
     }
     ```
-    <Playground url="https://search-playground.corp.mongodb.com/tools/code-sandbox/snapshots/679cb6fdd0df60f0254e5d6a">solution</Playground>
+    <Playground url="https://search-playground.corp.mongodb.com/tools/code-sandbox/snapshots/679cb6fdd0df60f0254e5d6a">🔗 solution</Playground>
   </div>
 </details>

docs/70_Data_Modeling/8_Exercises.mdx

@@ -2,7 +2,10 @@
 
 ## Only make searchable a specific subset of fields
 
-First, see how <Playground url="https://search-playground.corp.mongodb.com/tools/code-sandbox/snapshots/67b5ccc0828ad15116bcce21">a string field is automatically searchable</Playground> but now make it so only fields under the `metadata` structure are indexed (and thus this query would then fail to find any matching documents)
+<Playground url="https://search-playground.corp.mongodb.com/tools/code-sandbox/snapshots/67b5ccc0828ad15116bcce21">🔗 Playground link: a dynamic string field is automatically searchable</Playground>
+
+Make it so only fields under the `metadata` structure are indexed (and thus this query would then fail to find any matching documents). This is an exercise where no matching documents (an empty array `[]`) is the goal, rather than matching on a field that should not be indexed.
+
 <details>
   <summary>Solution</summary>
   <div>
@@ -22,6 +25,6 @@ First, see how <Playground url="https://search-playground.corp.mongodb.com/tools
       }
     }
     ```
-    <Playground url="https://search-playground.corp.mongodb.com/tools/code-sandbox/snapshots/67b5cd163cface474919d070">solution</Playground>
+    <Playground url="https://search-playground.corp.mongodb.com/tools/code-sandbox/snapshots/67b5cd163cface474919d070">🔗 solution</Playground>
   </div>
 </details>