Custom Error Mappings

Sometimes, a writing team has a style guide or preferences that go beyond grammatical correctness. Sapling's Custom Errors feature can be used to enforce brand guidelines or a specific writing style for you and your team.

Individual settings can be managed at https://sapling.ai/custom_mapping

Case Sensitivity

By default, Sapling will match errors in title case as well as all-caps. 

For example, for the entry:
yoghurt -> yogurt
Sapling will also suggest:
Yoghurt -> Yogurt 
YOGHURT -> YOGURT

For rules that are case-sensitive, make sure to check the "Case Sensitive" checkbox.  

Regular Expressions

There are currently a couple types of regular expression-like options:

• ^ and $ match the start and end of a sentence, respectively. Example: ^the will only match the at the start of a sentence and can be used to enforce capitalization.
• # will match a number; example: Gate # will match in Boarding is at Gate 5.
  
  

User and Team Errors

Individual Custom Error settings take precedence over Team settings. 

Description 

Team compliance notes can be specified in the "Description" field. This will show up when the edit is suggested to the end user. If a description field is specified, the user will not have the option to ignore the edit. 

CSV Uploads

Custom error mappings can be uploaded via CSV file format.

Format requirements:

• There should be no header/field labels or an empty row
• The first column will be parsed as the "Error" field
• The second column will be parsed as the "Change To" field
• The third column will be parsed as the "Description" field
• The fourth column will be parsed as the "Case Sensitive" field (use "T" or "F")

Upload Procedure:

• Select a file using the file picker.
• If necessary, check the "Case Sensitive" option for the upload
• Click the "Upload" button to upload the file.