Introduce Chef UI, better explain fallbacks

Author: tilenkavcic

fern/docs/pages/airdrop/initial-domain-mapping.mdx

@@ -11,17 +11,17 @@ system is triggered.
 
 You can create initial domain mappings using two methods:
 
-1. **Chef-cli UI**: Interactive web interface for comprehensive mapping creation
+1. **Chef UI**: Interactive web interface for comprehensive mapping creation
 2. **Model Context Protocol (MCP)**: AI-assisted mapping creation for developers (experimental)
 
-Choose the chef-cli UI for manual control or use MCP for rapid prototyping with AI assistance.
+Choose the Chef UI for manual control or use MCP for rapid prototyping with AI assistance.
 MCP is an experimental feature and works locally without requiring a sync to be created.
 
 <Info>
 For AI-assisted mapping creation, see the [Model Context Protocol integration guide](./mcp.mdx).
 </Info>
 
-## Chef-cli initial domain mapping setup
+## Chef UI setup
 
 ### Prerequisites
 
@@ -70,7 +70,7 @@ Or you can use the interactive helper of the CLI:
 eval $(chef-cli ctx init); chef-cli ctx show > ctx.json
 ```
 
-### Use the local UI to create a recipe blueprint for your initial import
+### Use the Chef UI
 
 ```bash
 chef-cli configure-mappings --env prod
@@ -88,21 +88,21 @@ ACTIVE_PARTITION=dvrv-in-1 chef-cli configure-mappings --env prod
 
 The options are: `dvrv-us-1`, `dvrv-eu-1`, `dvrv-in-1`, and `dvrv-de-1`.
 
-The first function of the local UI is to assemble a *blueprint* for a concrete import running in the test-org, allowing the mapping to be tested out and evaluated.
-After it is used for the import, the mappings become immutable, but the chef-cli UI offers a button to make a draft clone, which can be edited again for refinements.
+The first function of the Chef UI is to assemble a *blueprint* for a concrete import running in the test-org, allowing the mapping to be tested out and evaluated.
+After it is used for the import, the mappings become immutable, but the Chef UI offers a button to make a draft clone, which can be edited again for refinements.
 
 ### Continue to initial domain mapping
 
-When you are done, you should have the chef-cli context set up and have the chef-cli local UI running in your browser.
-You can now use the chef-cli web UI to create initial domain mappings.
+When you are done, you should have the chef-cli context set up and have the Chef UI running in your browser.
+You can now use the Chef UI to create initial domain mappings.
 
 </Steps>
 
-## Use the local UI to create initial domain mappings
+## Use the Chef UI to create initial domain mappings
 
-The chef-cli UI generates an `initial_domain_mapping.json` file that must be embedded in your extractor. This defines the options that the end-user sees when they are mapping the data.
+The Chef UI generates an `initial_domain_mapping.json` file that must be embedded in your extractor. This defines the options that the end-user sees when they are mapping the data.
 
-Initial domain mappings differ from user mappings in two key ways:
+Initial domain mappings provide two key configuration capabilities:
 
 1. **Multiple mapping options**: The developer can choose how external record types map to DevRev records (for example, external *task* can map to either *issue* or *ticket*).
 2. **Category-based defaults**: Mappings can apply to entire record type categories, automatically handling new record types.
@@ -111,26 +111,26 @@ Initial domain mappings differ from user mappings in two key ways:
 
 ### Map record types and fields
 
-Use the chef-cli UI to map record types and fields.
-The UI shows you the record types that are available in the org and allows you to map them to the external record types.
-You should map one record type at a time.
+Use the Chef UI to map record types and fields.
+The UI displays the external record types you defined in external domain metadata and allows you to map them to DevRev objects.
+Map one record type at a time, ensuring you map all required fields and as many optional fields as possible.
 
 ### Specify fallback mappings
 
-For most required DevRev fields a fallback is required. This is used on object creation if the extractor doesn't provide a value.
+For some required DevRev fields a fallback is required.
 
-The fallback should be a DevRev value that is valid for the field. 
-For enum fields, the fallback should be the enum **value** as specified in [Supported object types](./supported-object-types.mdx).
+The fallback you choose will be used on item creation if the extractor doesn't provide a value for the required DevRev field. 
+This is useful for fields that are required by DevRev but optional in the external system.
 
 ### Install the blueprint
 
-Click **Install in this org** to access the initial domain mapping creation screen.
+Apply the mappings and **install them in your org** to access the initial domain mapping creation screen.
 Follow the instructions to create your initial domain mapping.
 
 ### Merge configurations
 
 You can repeat the process for different record types and fields to create multiple mappings.
-In the install screen, you can merge your mappings with existing initial mappings.
+In the install screen, you can merge new mappings with existing initial domain mappings.
 
 ### Export the mapping file