content updates

erikhatcher · erikhatcher · commit 2161325208ea · 2025-01-13T16:40:56.000-05:00
diff --git a/docs/10_About_workshop/2_lets_go.mdx b/docs/10_About_workshop/2_lets_go.mdx
@@ -1,12 +1,14 @@
-# 👐 Our first playground exercise
+# 👐 First 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 - 
+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"
-3. Notice the empty `[]` results
+3. Notice the empty array `[]` of results
 
 The objective with this exercise is to adjust the `FIX_ME` in the `$search` aggregation pipeline stage so that the document (in the Data Source pane) matches the query and appears in the Results pane.
 
diff --git a/docs/20_Intro_to_Atlas_Search/1_system.mdx b/docs/20_Intro_to_Atlas_Search/1_system.mdx
@@ -1,10 +1,11 @@
 # 📘 Atlas Search architecture
 
-Atlas Search provides powerful findability capabilities to your data collections. A flexible index configuration allows mapping and indexing only the fields needed, or dynamically mapping any and all fields supported. 
+Atlas Search provides powerful findability capabilities to your data collections.
+A flexible index configuration allows mapping and indexing only the fields needed,
+or dynamically mapping any and all fields supported. 
 
 ![big picture](/img/big_picture.png)
 
-
 ![system diagram](/img/system_diagram.png)
 
 Changes to a collection via updates, deletes, or additions are *eventually consistent*, meaning the
diff --git a/docs/30_Index_configuration/2_index_config.mdx b/docs/30_Index_configuration/2_index_config.mdx
@@ -10,7 +10,7 @@ Documents are mapped to an index through a flexible configuration.
 
 ## Configuring a real Atlas Search index
 
-* Atlas Search Visual Index Builder or JSON Editor
-* via Compass
-* Atlas CLI
-* Driver commands
+  * Atlas Search Visual Editor or JSON Editor
+  * via Compass
+  * Atlas CLI
+  * Driver commands
diff --git a/docs/30_Index_configuration/4_geo.mdx b/docs/30_Index_configuration/4_geo.mdx
@@ -4,6 +4,7 @@ GeoJSON and Points
 
 * https://www.mongodb.com/docs/atlas/atlas-search/geoWithin/
 * https://www.mongodb.com/docs/atlas/atlas-search/geoShape/
+* https://www.mongodb.com/docs/atlas/atlas-search/near/
 
 ### geo
 Dynamic mapping does not support geo-spatial fields, and require a manual/static mapping configuration.
diff --git a/docs/30_Index_configuration/5_nested_docs.mdx b/docs/30_Index_configuration/5_nested_docs.mdx
@@ -6,10 +6,11 @@ There are two distinct ways to map and index the contents of nested documents.
 
 ## `document`
 
-Default dynamic mapping behavior, flattens nested documents into “arrays” of values on main document
+Default dynamic mapping behavior, flattens nested documents into “arrays” of values on main document.
 
 ## `embeddedDocuments`
 
-Attribute pattern `elemMatch`-like matching, more nuanced and expensive than document type flattening
+Attribute pattern `elemMatch`-like matching, more nuanced and expensive than document type flattening.
+See also: https://www.mongodb.com/docs/atlas/atlas-search/field-types/embedded-documents-type/
 
 WARNING: Each nested document mapped as as `embeddedDocuments` counts as an additional "index object".
diff --git a/docs/30_Index_configuration/6_string.mdx b/docs/30_Index_configuration/6_string.mdx
@@ -36,3 +36,14 @@ Multiple language example: may not know the language of the content and each doc
 Example of being able to do ‘startsWith’ and ‘endsWith’ using wildcard and ‘reverse’ token filter:
 https://search-playground.mongodb.com/tools/code-playground/snapshots/6683c8bc4a45448733549bbc
 
+
+* Text: the heart and soul of your content
+* Strings are analyzed, tokenized into terms
+  * Multiple analyzers can be used for a single string field (multi)
+* Terms: words, fragments, atomic searchable units
+* An inverted index structure organizes terms lexicographically/alphabetically for quick lookup (aka a dictionary)
+* Term statistics:
+  * Posting list: document identifiers
+  * Term frequency (tf): how many occurrences of the term per document
+  * Document frequency (df): how many documents contain the term
+  * Positions: where in the document does this term occur
diff --git a/docs/40_Analysis/index.mdx b/docs/40_Analysis/index.mdx
@@ -4,4 +4,7 @@
 * Built-in analyzers from lucene.keyword to the others
 * Labs: lucene.standard, lucene.english, custom analyzer
 
-https://www.mongodb.com/docs/atlas/atlas-search/analyzers/
+https://www.mongodb.com/docs/atlas/atlas-search/analyzers/
+
+![Visual Editor standard analyzer output](/img/editor_analysis.png)
+
diff --git a/docs/99_TODO.md b/docs/99_TODO.md
@@ -2,11 +2,11 @@
 * Fire up ProcessCene and generate some analysis images, etc
 * Polish headers/footers
 * Fix publishing to GH Pages
-* rename .md's to .mdx's
-* rename Playground section to something else - it's the workshop practicals
 * should completed/solved playgrounds be saved and linked in here as well?
 * Add coverage of "index objects" counting
 * Add transition verbiage at the end of each page/section to lead into the next one
+* should all links back to mongodb.com have UTMs?  How to use the variables?
+* border around images?  click to make them larger?
 
 Cool Tricks
 Which clause matches?
