rearranging sections

Author: erikhatcher

docs/15_Playground/1_intro.md renamed to docs/10_Playground/1_intro.md

@@ -3,14 +3,14 @@
 The Atlas Search Playground (or just Playground) is used for the exercises in this workshop.  The Playground is a self-contained lightweight, yet feature-rich Atlas Search environment which does not require an Atlas account to use.
 
 There are two tools in the Playground:
-  * Code Sandbox: your data, an index configuration, an aggregation pipeline, and results
-  * Search Demo Builder: a configurable search UI on your data
+  * `Code Sandbox`: your data, an index configuration, an aggregation pipeline, and results
+  * `Search Demo Builder`: a configurable search UI on your data
 
-The exercises will use the Code Sandbox, as it allows saving and sharing links to the full environment and corresponds directly to the configuration and pipeline one would use in a real application.
+The exercises will use the Code Sandbox, as it allows saving and sharing links to the full environment and allows us to work on one topic at a time.
 
 ## Code Sandbox layout
 
-To begin, please navigate to the [Atlas Search Playground](https://search-playground.mongodb.com/). In the next section, you'll work through the first exercise to get familiar with the Playground's Code Sandbox.
+To begin, navigate to the [Atlas Search Playground](https://search-playground.mongodb.com/). In the next section, you'll work through the first exercise to get familiar with the Playground's Code Sandbox.
 
 Let's dive into the world of Atlas Search using this convenient and powerful playground!
 

docs/15_Playground/2_lets_go.mdx renamed to docs/10_Playground/2_lets_go.mdx

@@ -1,5 +1,8 @@
 # 👐 Our first playground exercise
 
+Here's a gentle first exercise to get you started with the playground. You'll see an index configuration and an aggregation pipeline stage that hasn't been introduced yet, but no worries - 
+we'll get there next. See if you can solve it with what you already know or expect.
+
 1. Navigate to this Playground snapshot: 
    https://search-playground.mongodb.com/tools/code-sandbox/snapshots/6782aea0667feaaf06324b87
 2. Press "Run" (TODO: bring in the Run graphic)
@@ -10,8 +13,9 @@ The objective with this exercise is to adjust the `FIX_ME` in the `$search` aggr
 TODO: insert un-fixed playground screenshot
 
 <details>
-<summary>Here's a solution</summary>
+<summary>Here's a solution...</summary>
 <div>
+You can copy this pipeline and paste it in to the playground's Query panel and press Run.
 ```js
 [
   {
@@ -29,7 +33,7 @@ TODO: insert un-fixed playground screenshot
 </details>
 
 <details>
-<summary>There are other possible solutions too</summary>
+<summary>There are other possible solutions too, such as:</summary>
 <div>
 `atlas` or `fundamentals` or other case variations of any `title` field words
 </div>

docs/10_Architecture/1_system.md renamed to docs/15_Overview/1_system.md

@@ -2,7 +2,6 @@
 
 ![system diagram](/img/system_diagram.png)
 
-
 ## Coupled nodes
 ![coupled nodes](/img/coupled.png)
 

docs/10_Architecture/2_index_config.md renamed to docs/15_Overview/2_index_config.md

@@ -1,16 +1,16 @@
 # Field types
 
 ## boolean
-equals: https://search-playground.corp.mongodb.com/tools/code-playground/snapshots/669e6ab1d49ef6fad98118b4
+equals: https://search-playground.mongodb.com/tools/code-playground/snapshots/669e6ab1d49ef6fad98118b4
 
 ## date
-range: https://search-playground.corp.mongodb.com/tools/code-playground/snapshots/669e6b18d49ef6fad98118b6
+range: https://search-playground.mongodb.com/tools/code-playground/snapshots/669e6b18d49ef6fad98118b6
 
 ## number
-range: https://search-playground.corp.mongodb.com/tools/code-playground/snapshots/669e6b4ad49ef6fad98118b8
+range: https://search-playground.mongodb.com/tools/code-playground/snapshots/669e6b4ad49ef6fad98118b8
 
 ## geo
-geoWithin: https://search-playground.corp.mongodb.com/tools/code-playground/snapshots/669e6b762ce7658e786edbfa
+geoWithin: https://search-playground.mongodb.com/tools/code-playground/snapshots/669e6b762ce7658e786edbfa
 Requires explicit geo type mapping, since dynamic mappings don’t support geo.
 
 ## autocomplete
@@ -36,9 +36,9 @@ lucene.standard matching case-insensitive: https://search-playground.mongodb.com
 ## Custom analyzers
 Last 4 digit of phone number matching (regex extraction during indexing, keyword analysis at query time): https://search-playground.corp.mongodb.com/tools/code-playground/snapshots/669e6c98d49ef6fad98118ba
 Example of being able to do ‘startsWith’ and ‘endsWith’ using wildcard and ‘reverse’ token filter:
-https://search-playground.corp.mongodb.com/tools/code-playground/snapshots/6683c8bc4a45448733549bbc
+https://search-playground.mongodb.com/tools/code-playground/snapshots/6683c8bc4a45448733549bbc
 
-Example of being able to do ‘startsWith’, ‘endsWith’ and ‘contains’ using nGrams: https://search-playground.corp.mongodb.com/tools/code-playground/snapshots/6683c999934a05d9b585b6e7 
+Example of being able to do ‘startsWith’, ‘endsWith’ and ‘contains’ using nGrams: https://search-playground.mongodb.com/tools/code-playground/snapshots/6683c999934a05d9b585b6e7 
 Relevancy
 Example of an as-you-type suggest configuration; sophisticated use of multi and several weighted query clauses: https://search-playground.mongodb.com/tools/code-playground/snapshots/66473b744e0a3f240a5de9e1
 $project score?
@@ -49,5 +49,5 @@ Why?
 Relevancy example: boost each multi uniquely
 Multiple language example: may not know the language of the content and each document could be different - multi across all possible languages, query across them as desired at query-time, let relevancy sort it out
 Example of being able to do ‘startsWith’ and ‘endsWith’ using wildcard and ‘reverse’ token filter:
-https://search-playground.corp.mongodb.com/tools/code-playground/snapshots/6683c8bc4a45448733549bbc
+https://search-playground.mongodb.com/tools/code-playground/snapshots/6683c8bc4a45448733549bbc
 

docs/15_Playground/3_data_types renamed to docs/15_Overview/3_data_types

@@ -1,4 +1,4 @@
-# Summary
+# 🎯 Summary
 
 Congratulations!