MC-4272: Update content type docs

Updated overview and images.

Author: bdenham

README.md

@@ -31,13 +31,13 @@ We offer one method for installing PageBuilder:
 * [Install Page Builder](docs/getting-started/install-pagebuilder.md)
 * [Activate Page Builder](docs/getting-started/activate-pagebuilder.md)
 
-### Create a basic content type
+### Create a content type
 
 * [Overview](docs/create-basic-content-type/overview.md)
 * [Step 1: Add configuration](docs/create-basic-content-type/step-1-add-configuration.md)
 * [Step 2: Add templates](docs/create-basic-content-type/step-2-add-templates.md)
 * [Step 3: Add components](docs/create-basic-content-type/step-3-add-components.md)
-* [Step 4: Add editor](docs/create-basic-content-type/step-4-add-editor.md)
+* [Step 4: Add form editor](docs/create-basic-content-type/step-4-add-form-editor.md)
 * [Step 5: Add layout](docs/create-basic-content-type/step-5-add-layout.md)
 * [Step 6: Add styles and icons](docs/create-basic-content-type/step-6-add-styles-icons.md)
 * [Step 7: Add frontend widget](docs/create-basic-content-type/step-7-add-frontend-widget.md)

docs/create-basic-content-type/overview.md

@@ -16,13 +16,13 @@ The steps for creating a Page Builder content type are briefly outlined here. Th
 
 ![Creating Custom Content Types](../images/content-type-overview.png)
 
-1. **Add a configuration** as an XML file to setup all the other files that control the appearances and behaviors of your content type.  
-2. **Add templates** as HTML files to control the appearance of your content types on the Admin stage (preview.html) and the storefront (master.html).
-3. **Add a component** as a JavaScript file to control the behavior of your content type on the Admin stage (preview.js) and the storefront (master.js).
-4. **Add an editor** as a UI component (XML file) to give users the ability to add or edit content with your content type.
-5. **Add layout** as an XML file to add your editor to the stage. 
-6. **Add styles and icons** as LESS and image files (png, svg) to add specific styling and images to your content types as they appear on the Admin stage and the storefront. 
-7. **Add frontend widget** as a JavaScript file to control the UI behavior (user interactivity) of your content type on the storefront.  
+1. **Add configuration**: an XML file to setup all the other files that control the appearances and behaviors of your content type.  
+2. **Add templates**: HTML files to control the appearance of your content types on the Admin stage (preview.html) and the storefront (master.html).
+3. **Add component**: a JavaScript file to control the behavior of your content type on the Admin stage (preview.js) and the storefront (master.js).
+4. **Add form (editor)**: a UI component (XML file) to give users the ability to add or edit content using your content type.
+5. **Add layout**: an XML file to add your form editor to the stage. 
+6. **Add styles and icons**: LESS and image files (png, svg) to add specific styling and images to your content types as they appear on the Admin stage and the storefront. 
+7. **Add frontend widget**: a JavaScript file to control the UI behavior (user interactivity) of your content type on the storefront.  
 
 ![Before and after content type](../images/content-type-files.png)
 

docs/create-basic-content-type/step-4-add-editor.md

@@ -0,0 +1 @@
+# Step 4: Add form editor