Updated docs with Bradford's suggestions.

docs/dev_guide/custom_field.rst

@@ -42,5 +42,5 @@ The rest of this section will walk you through these steps.
 
    custom_field/select_vocab_terms
    custom_field/manual_field_creation
-   custom_field/tripal_field_generator
    custom_field/custom_widget
+   custom_field/tripal_field_generator

docs/dev_guide/custom_field/custom_widget.rst

@@ -110,4 +110,4 @@ For our ``obi__organism`` example, the drop-down returns the chado organism_id o
 
 Drupal typically does not provide a submit hook for fields because, as mentioned above, saving should be done by the storage backend. However, the TripalField provides a ``TripalFieldWidget::submit()`` to allow for behind-the-scenes actions to occur. This function should never be used for updates, deletes or inserts for the Chado table associated with the field as these actions should be handled by the storage backend. 
 
-However, it is permissible to perform inserts, updates or deletions within Chado using this function.  Those operations can be performed if needed but on other tables not directly associated with the field. An example is the chado.feature_synonym table.  The chado_linker__synonym field allows the user to provide a brand new synonynm and it must add it to the chado.synonym table prior to the record in the chado.feature_synonym table.  
+However, it is permissible to perform inserts, updates or deletions within Chado using this function.  Those operations can be performed if needed but on other tables not directly associated with the field. An example is the ``chado.feature_synonym`` table.  The ``chado_linker__synonym`` field allows the user to provide a brand new synonynm and it must add it to the chado.synonym table prior to the record in the chado.feature_synonym table.