included odo lists throughout authoring stack docs

Author: jc-berger

docs/modules/user-guide/partials/proc_adding-a-name-to-a-devfile.adoc

@@ -2,7 +2,13 @@
 = Adding a name to a devfile
 
 [role="_abstract"]
-Adding a name to a devfile is mandatory. Use the `name` or `generateName` attributes (or both) to define the name.
+Adding a name to a devfile is mandatory. Use the `name` or `generateName` attributes to define the name. See the following list for metadata properties in a devfile:
+
+[horizontal]
+Key:: metadataObject
+Type:: metadataObject
+Required:: no
+Description:: metadata to be used
 
 .Prerequisites
 

docs/modules/user-guide/partials/proc_adding-commands-to-a-devfile.adoc

@@ -2,7 +2,13 @@
 = Adding commands to a devfile
 
 [role="_abstract"]
-A devfile allows to specify commands to be available for execution in a workspace. Every command can contain a subset of actions. These subsets are related to specific components and are executed in the component containers.
+A devfile allows to specify commands to be available for execution in a workspace. Every command can contain a subset of actions. These subsets are related to specific components and are executed in the component containers. See the following list for command properties in a devfile:
+
+[horizontal]
+Key:: commandObject
+Type:: commandObject
+Required:: no
+Description:: command to be executed in an existing component container
 
 .Prerequisites
 

docs/modules/user-guide/partials/proc_adding-components-to-a-devfile.adoc

@@ -2,7 +2,13 @@
 = Adding components to a devfile
 
 [role="_abstract"]
-Each component in a single devfile must have a unique name.
+Each component in a single devfile must have a unique name. See the following list for component properties in a devfile:
+
+[horizontal]
+Key:: componentObject
+Type:: componentObject
+Required:: no
+Description:: list of components to be used
 
 .Prerequisites
 

docs/modules/user-guide/partials/proc_adding-event-bindings.adoc

@@ -2,7 +2,13 @@
 = Adding event bindings
 
 [role="_abstract"]
-This section describes how to add an event to a v2.x devfile. An event specified in a v1.x devfile still works in a v2.x devfile.
+This section describes how to add an event to a v2.x devfile. An event specified in a v1.x devfile still works in a v2.x devfile. See the following list for event properties in a devfile:
+
+[horizontal]
+Key:: eventObject
+Type:: eventObject
+Required:: no
+Description:: events to be executed during a project lifecycle
 
 .Procedure
 

docs/modules/user-guide/partials/proc_adding-projects-to-a-devfile.adoc

@@ -2,8 +2,13 @@
 = Adding projects to a devfile
 
 [role="_abstract"]
-This section describes how to add one or more projects to a devfile.
+This section describes how to add one or more projects to a devfile. See the following list for project properties in a devfile:
 
+[horizontal]
+Key:: starterProjectObject
+Type:: starterProjectObject
+Required:: no
+Description:: list of starter projects to be used
 
 .Prerequisites
 

docs/modules/user-guide/partials/proc_adding-schema-version-to-a-devfile.adoc

@@ -2,8 +2,13 @@
 = Adding schema version to a devfile
 
 [role="_abstract"]
-The `schemaVersion` attribute is mandatory in a devfile.
+The `schemaVersion` attribute is mandatory in a devfile. See the following list for `schemaVersion` properties in a devfile:
 
+[horizontal]
+Key:: schemaVersion
+Type:: string
+Required:: yes
+Description:: v2.1.0 of the schema
 
 .Procedure