MC-5769: Complete content type tutorial

Minor updates

Author: bdenham

docs/create-basic-content-type/step-1-add-configuration.md

@@ -11,7 +11,7 @@ Files referenced from the configuration include the HTML templates, the JavaScri
 
 ![configuration-hub](../images/configuration-hub.png)
 
-## Conventions
+## Configuration conventions
 
 By convention, Page Builder requires the configuration for a content type to be in the `adminhtml` area within a directory named `pagebuilder` and a subdirectory named `content_type` or `content-type`.
 
@@ -22,9 +22,9 @@ The name of your configuration file should reflect the name of your content type
 {: .bs-callout .bs-callout-info }
 The reason we suggest prefIxing your content type with your vendor name is to prevent Magento from merging your content type configuration file with another configuration file of the same name, or with a future content type published by Magento.
 
-## Example configuration
+## The `example_quote` configuration
 
-In this example, only a subset of configuration elements are described in our Quote example (enough to understand the basic role of the configuration file). For more details, refer to [Content type configurations](../configurations/content-type-configuration.md) and [Additional configurations](../configurations/additional-configurations.md).
+Only a subset of configuration elements are described in our Quote example (enough to understand the basic role of the configuration file). For more details, refer to [Content type configurations](../configurations/content-type-configuration.md) and [Additional configurations](../configurations/additional-configurations.md).
 
 
 The following configuration is from the Quote content type. An overview of these elements and attributes are described in the tables that follow.
@@ -119,7 +119,7 @@ Going further, each `appearance` is defined by exactly two HTML templates, one t
 
 ## The `elements` element
 
-The purpose of `<elements>` as defined within an appearance is to map the data from the content type's edit form to the content type's master format so that the values entered in the form can be stored and rendered correctly on the Admin stage and storefront. We will describe the `elements` in [Step 4: Add form](step-4-add-form.md)
+The `<elements>` element as defined within an `appearance` is to map the data from the content type's form editor to the content type's master format so that the values entered in the form can be stored and rendered correctly on the Admin stage and storefront. We discuss content type `elements` in [Step 4: Add form](step-4-add-form.md)
 
 ## Next
 

docs/create-basic-content-type/step-2-add-templates.md

@@ -68,9 +68,9 @@ The following table describes each `appearance` attribute in our example.
 | `render_template`  | References the `master.html` (the master format storefront template) for rendering the appearance of your content type on the storefront for customers to see. |
 | `reader`           | Reads content type data from the master format.      |
 
-## Quote `preview.html`
+## Quote `preview_template`
 
-The `preview.html` template defined for our Quote's appearance, is shown here in full followed by descriptions to help you understand the basics of this template.
+The Quote `preview_template`  (`preview.html`) is shown here in full, followed by the attribute descriptions to help you understand the basics of content type templates.
 
 ```html
 <!-- preview.html -->
@@ -171,9 +171,9 @@ The `liveEdit` binding enables end users to enter HTML content directly on the A
 
 The `event` attribute enables the options menu to be shown and hidden when users interact with the content type using the mouse. If you have a special circumstance with the way you wish to handle your option menus, you can modify this logic to suit your needs.
 
-## Quote `master.html`
+## Quote `render_template`
 
-The `master.html` template defined for the Quote appearance is shown here in full. The same attributes and descriptions from the Admin preview template apply to this template as well, with one addition, the `html` attribute. 
+The Quote `render_template` (`master.html`) is shown here in full. The same attributes and descriptions from the `preview.html` template apply to the `master.html` template as well. However, the  `master.html` template introduces one addition attribute, `html`, which is described after the code.
 
 ```html
 <!--master.html-->
@@ -200,17 +200,17 @@ The `master.html` template defined for the Quote appearance is shown here in ful
 
 ### html
 
-The `html` attribute applies the actual user-entered HTML to the template element. In our Quote example, the end-user enters their quote text either from the Admin stage using `liveEdit`, which is bound to the `quote_text` field, or from the form. 
+The `html` attribute applies the actual user-entered HTML content to the template element. In our Quote example, the end-user enters their quote text either on the Admin stage using `liveEdit` (which is bound to the `quote_text` field in the form editor) or on the form, directly into the`quote_text` field itself.
+
+For example, from the Quote `preview.html` template, the `liveEdit` binding on the `blockquote` is bound to the `quote_text` field that stores the HTML content, as shown here (`{ field: 'quote_text'...}`):
 
 ```html
 <!--preview.html-->
 <blockquote data-bind="liveEdit: { field: 'quote_text', placeholder: $t('Enter Quote') }">
 </blockquote>
 ```
 
-From `liveEdit`, we see that the content of `blockquote` is bound to the `quote_text` field that stores the html. 
-
-The master format storefront template uses the `html` attribute to retrieve the HTML content and display it in the `blockquote` element: 
+The master format storefront template uses the `html` attribute to retrieve the HTML content and display it in the `blockquote` element as follows: 
 
 ```html
 <!--master.html-->
@@ -223,6 +223,7 @@ The `html` value is derived from the configuration `element` name  (`quote`) and
 <element name="quote">
   <html name="quote_text" converter="Magento_PageBuilder/js/converter/html/tag-escaper"/>
 	...
+</element>
 ```
 
 ## Next