renumbering config sections and some content updates

Author: erikhatcher

docs/20_Intro_to_Atlas_Search/2_aggregation_stages.mdx

@@ -2,16 +2,24 @@
 
 ## $search
 
-where the magic happens
+Returns matching documents.
+
+Search metadata (count and facets) are available via the $$SEARCH_META aggregation variable.
+Results are returned in descending **score** order or in an optional `sort` order.
 
 ## $searchMeta
 
+Returns a single document of search result metadata including count of matching documents
+and facets requested. No actual collection documents are returned.
+
 The `$searchMeta` stage performs the same search that `$search` does,
 but only returns the results metadata, not actual matching documents.
 Results metadata includes the count of matching results and facets.
 This same metadata is available when using `$search` too, 
 accessible in the $$SEARCH_META context variable.
 
+
+
 ## Exercises: search pipeline stages
 
 ### Step 1

docs/30_Index_configuration/2_index_config.mdx renamed to docs/30_Index_configuration/1_index_config.mdx

@@ -17,4 +17,8 @@ such as fields of type `document`, to be dynamically mapped.
   * via Compass
   * Atlas CLI
   * Driver commands
-  
+
+## Configuration options
+
+  * `storedSource`
+  * `synonyms`

docs/30_Index_configuration/3_field_mapping.mdx renamed to docs/30_Index_configuration/2_basic_types.mdx

@@ -2,7 +2,7 @@
 
 Document fields are mapped to a search index based on their BSON data type.
 
-When `dynamic: "true"`, a field is indexed if its field type is supported.
+When `dynamic: "true"`, a field is indexed if its field type is supported. 
 
 When a field name is explicitly/statically mapped, it will be indexed if the field type also matches the
 mapped type.

docs/30_Index_configuration/4_geo.mdx renamed to docs/30_Index_configuration/3_geo.mdx

@@ -47,3 +47,5 @@ lucene.english: standard tokenization plus de-pluralization, stop word removal,
 lucene.keyword: Tokenizes text as a single term; suitable for wildcard or regex matching over entire value
 Many language-specific analyzers built-in: (lucene.)arabic, armenian, basque, bengali, brazilian, bulgarian, catalan, chinese, cjk, czech, danish, dutch, english, finnish, french, galician, german, greek, hindi, hungarian, indonesian, irish, italian, japanese, korean, kuromoji, latvian, lithuanian, morfologik, nori, norwegian, persian, polish, portuguese, romanian, russian, smartcn, sorani, spanish, swedish, thai, turkish, ukrainian
 
+`searchAnalyzer` vs. `analyzer`
+

docs/30_Index_configuration/5_nested_docs.mdx renamed to docs/30_Index_configuration/4_nested_docs.mdx

@@ -1,5 +1,5 @@
 {
-  "label": "Operators",
+  "label": "Search operators",
   "link": {
       "type": "generated-index"
   }