Skip to content

Commit cd59b36

Browse files
committed
Address comments
1 parent c8cff51 commit cd59b36

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

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

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -100,24 +100,24 @@ You can now use the chef-cli web UI to create initial domain mappings.
100100

101101
## Use the local UI to create initial domain mappings
102102

103-
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 will see when they are mapping the data.
103+
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.
104104

105105
Initial domain mappings differ from user mappings in two key ways:
106106

107-
1. **Multiple mapping options**: The developer can choose how external record types map to DevRev records (e.g., external *task* can map to either *issue* or *ticket*).
107+
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*).
108108
2. **Category-based defaults**: Mappings can apply to entire record type categories, automatically handling new record types.
109109

110110
<Steps>
111111

112112
### Map record types and fields
113113

114114
Use the chef-cli UI to map record types and fields.
115-
The UI will show you the record types that are available in the org and allow you to map them to the external record types.
115+
The UI shows you the record types that are available in the org and allows you to map them to the external record types.
116116
You should map one record type at a time.
117117

118118
### Specify fallback mappings
119119

120-
For most required DevRev fields we require a fallback. This is used on object creation if the extractor doesn't provide a value.
120+
For most required DevRev fields a fallback is required. This is used on object creation if the extractor doesn't provide a value.
121121

122122
The fallback should be a DevRev value that is valid for the field.
123123
For enum fields, the fallback should be the enum **value** as specified in [Supported object types](./supported-object-types.mdx).

0 commit comments

Comments
 (0)