Hints are composed and maintained in a text file with the contents formatted as JSON. You can use any commonly available text editors to create the file. Meaningful file names representative of the hints are recommended, and the file must use the .hints extension.

Hints need only a single key followed by a value containing the list of hints to be used during transcription, as shown in the following example:

{
“other” : [  “Joe's Hardware”, 
“Electrolux vacuum”, 
“Abode Repository”, 
“John Deere”, 
“Whirlpool Corporation” ],
"templates" : ["<other>"]
}

The key in this example is "other" .

For easier maintenance and modification of hints, save the hints document in the native format of the tool being used to create it. The hints document is the master document from which subsequent deployment documents are derived.