-;; If things don't work, you can probably fix it with a field mapping variable.
-;; By default, we use a combination of all predefined mappings, and look for
-;; every known field. If you have data that is from something we've already
-;; tested, try using it's specific mapping table in case that works better.
-;; Here is a handy template to set each of the predefined mapping tables:
+;; If things don't work, you can probably fix it with a custom field mapping
+;; variable. It should not be too hard. Use the existing tables as an
+;; example. By default, we use a combination of all predefined mappings, and
+;; look for every known field, but it is probably best to avoid that kind of
+;; table when setting up your own as it is an unnecessary complexity in this
+;; case. If you have a problem with data from a supported export program, start
+;; by testing its specific mapping table instead of the combined one. Here is a
+;; handy template to set each of the predefined mapping tables: