docs/8.0/ayanova/docs/adm-import.md

@@ -52,7 +52,7 @@ You can easily remove the tag later if desired by using the [bulk tagger extensi
 
 Checkmarking "Update existing records" indicates you want to **update** matched records in AyaNova.
 
-AyaNova will attempt to match the records in the import file to existing records in the AyaNova database by comparing the "key" field (identified in each objects import specifications).
+AyaNova will attempt to match the records in the import file to existing records in the AyaNova database by comparing the "key" field (identified in each objects [import specifications](#import-specifications)).
 
 Usually the key field will be the `Name` field but in some cases it may be another field that is the primary unique identifier for that record type.
 
@@ -88,9 +88,11 @@ Internally AyaNova only imports .json data; a .csv file is converted to json for
 
 ### Import file format
 
-Each supported object type that can be imported has it's import specification and examples documented individually, click through the objects listed below to see the import file specifications for each type.
+Each supported object type that can be imported has it's [import specification](#import-specifications) and examples documented individually, click through the objects listed below to see the import file specifications for each type.
 
-Field names in .json or header row names in .csv files _must_ match exactly in case and spelling the field names in each object type's specification document. Any other fields included will be removed by AyaNova before sending to the server for import.
+Field names in .json or header row names in .csv files _must_ match exactly in case and spelling the field names in each object type's [import specification](#import-specifications) document. 
+
+Any other fields included will be removed by AyaNova before sending to the server for import.
 
 CSV files must have a header row as the first row containing the specified field names. It's ok to omit any non-required fields.
 
@@ -128,7 +130,7 @@ As a rough guideline we recommend keeping the import file under 300kb in size to
 
 ## Can I import an AyaNova export file?
 
-JSON export files created with the [Export extension](ay-ex-export.md) can be imported into AyaNova however not all fields exported are importable, any fields not found in the import specification will be ignored.
+JSON export files created with the [Export extension](ay-ex-export.md) can be imported into AyaNova however not all fields exported are importable, any fields not found in the [import specifications](#import-specifications) will be ignored.
 
 The export extension exports many more object types and includes more fields than the import process supports.
 
@@ -142,10 +144,22 @@ The following listed types of AyaNova objects can currently be imported / update
 
 Types not listed may be added in future; for needs beyond what is provided with the import feature, you can always import **any** data now into AyaNova via software written using the [AyaNova developers API](api-intro.md).
 
-Each item below links to a page showing the specific format required for the import file and special notes about importing that specific object:
+Each object type listed below links to a page showing the specific format required for the import file and special notes about importing that specific object:
 
-- [Customer specifications](adm-import-customer.md)
+- [Customers](adm-import-customer.md)
 
 ## Import form
 
+#### Type
+
+AyaNova object types that can currently be imported / updated. 
+
+Here you select the desired destination object type to be imported or updated.
+
+If a type of object is not on this list it is not importable through this import form however any object that can be created or edited in AyaNova can be imported via the [AyaNova developers API](api-intro.md).
+
+Other controls on this form are hidden until a type is selected.
+
+#### 
+
 ### Menu options