MAGEDOC-3644: Post GA release docs cleanup

Fixes from review

Co-Authored-By: bdenham <bdenham@adobe.com>

Author: jeff-matthews

docs/create-custom-content-type/summary.md

@@ -3,7 +3,7 @@
 If you made it this far, congratulations! We hope this tutorial was useful for learning the basics of creating a completely new content type for your end users. 
 
 ## Next topics
-Here's a list of good next topics to learn more about customizing Page Builder:
+Review the following topics to learn more about customizing Page Builder:
 
 ### Tutorials
 

docs/extend-existing-content-type/overview.md

@@ -1,10 +1,10 @@
 # Overview
 
-One of the quickest ways to customize Page Builder is by changing how _existing_ content types look and behave. End-users can already use Page Builder's content types to customize their content using the form editor. But sometimes your end-users will want to change the structure or set properties that do not exist on the content type. In those cases, you can extend an existing content type by customizing its existing _appearance_ or adding a new _appearance_.
+One of the quickest ways to customize Page Builder is by changing how _existing_ content types look and behave. End users can already use Page Builder's content types to customize their content using the form editor. But your end users may want to change the structure or set properties that do not exist on the content type. In those cases, you can extend an existing content type by customizing its  _appearance_ or adding a new _appearance_.
 
 ## Appearances
 
-An **appearance** is an XML element (in the content type's config file) that defines a view for your content type. This view defines HTML templates, styles, form fields, and other elements, which you can customize in various ways. To extend existing Page Builder content types, you can either modify existing appearances or create new ones.
+An **appearance** is an XML element (in the content type's configuration file) that defines a view for your content type. This view defines HTML templates, styles, form fields, and other elements that you can customize in various ways. To extend existing Page Builder content types, you can either modify existing appearances or create new ones.
 
 Many of Page Builder's content types have only one `appearance` element. These include the Heading, Text, Image, Video, Tabs, and more. Other content types have several appearances. For example, the Banner content type has four appearances, as shown here:
 

docs/extend-existing-content-type/step-2-extend-appearances.md

@@ -1,6 +1,6 @@
 # Step 2: Extend appearances
 
-In this step, you will extend all four Banner appearances by adding a new `max_height` style to each. The max-height property stops the Banner from growing beyond a certain height as end-users enter banner text.
+In this step, you will extend all four Banner appearances by adding a new `max_height` style to each. The `max-height` property stops the Banner from growing beyond a certain height as end users enter banner text.
 
 ## Create a content configuration file
 
@@ -15,13 +15,13 @@ As mentioned before, Page Builder defines the Banner's appearances within the `b
 </appearances>
 ```
 
-To customize these appearances, we need to create a new configuration file named `banner.xml`. Our configuration file must be the same name as the Banner's configuration file. This ensures that Magento merges our appearance customizations with the Banner's existing configuration. Your file structure for the `banner.xml` extension should look like this:
+To customize these appearances, you must create a new configuration file named `banner.xml`. The configuration file must use the same name as the Banner's configuration file. This ensures that Magento merges the appearance customizations with the Banner's existing configuration. Your file structure for the `banner.xml` extension should look like this:
 
 ![Extension config file structure](../images/appearance-extension-config-file.png){:width="511px" height="auto"}
 
 ## Add properties to appearances
 
-In the Page Builder 1.0.0 release, you cannot extend just one appearance of a content type. You must extend them all. In our example, we are extending all four appearances of the Banner content type by adding a max-height style property to these appearances:
+In the Page Builder 1.0.0, you cannot extend just one appearance of a content type. You must extend them all. In the following example, we are extending all four appearances of the Banner content type by adding a `max-height` style property to these appearances:
 
 ```xml
 <?xml version="1.0"?>

docs/extend-existing-content-type/step-3-extend-forms.md

@@ -93,10 +93,10 @@ The following table describes some key elements:
 | `settings` | Provides the markup that gives your field a label, CSS styling, validation, and other properties as needed. |
 {:style="table-layout:auto"}
 
-After adding the max_height field, flush your cache, drag a banner to the Admin stage, open the editor, and see your new style property field being rendered in the Banner's form, as shown here:
+After adding the `max_height` field, flush your cache, drag a banner to the Admin stage, open the editor, and see your new style property field being rendered in the Banner's form, as shown here:
 
 ![Appearance fieldset](../images/appearance-fieldset.png){:width="934px" height="auto"}
 
 ## Conclusion
 
-That's it! You should now be familiar with the basics of extending an existing content type. There is much more to learn, but we hope this gives you a better understanding of how you can customize the existing Page Builder content types to fit your end-user's needs.
+That's it! You should now be familiar with the basics of extending an existing content type. There is much more to learn, but we hope this gives you a better understanding of how you can customize the existing Page Builder content types to fit your end-user's needs.

docs/reference/knockout-bindings.md

@@ -41,7 +41,7 @@ view/adminhtml/web/ts/js/binding/draggable.ts
 
 This binding serves as an interface for jQuery UI Draggable.
 
-Within Page Builder, we use this binding for the left panel's content types. The configuration and usage of the `draggable` binding can be seen in the Panel component. If you have access to the Page Builder repo, you can find the Panel component template here: https://github.com/magento/magento2-page-builder/blob/develop/app/code/Magento/PageBuilder/view/adminhtml/web/template/panel.html.
+Within Page Builder, we use this binding for the left panel's content types. You can see the configuration and usage of the `draggable` binding in the Panel component. If you have access to the Page Builder repo, you can find the Panel component template here: https://github.com/magento/magento2-page-builder/blob/develop/app/code/Magento/PageBuilder/view/adminhtml/web/template/panel.html.
 
 **Configuration:**
 
@@ -83,4 +83,4 @@ The binding has no configuration and must be passed an observable with a boolean
 
 ```html
 <div data-bind="hasFocusNoScroll: anObservable" />
-```
+```

docs/release-notes.md

@@ -6,7 +6,7 @@
 
 ### Documentation
 
-To start learning about Page Builder and Page Builder development:
+To learn more about Page Builder and Page Builder development:
 
  - For developers: [What is Page Builder?](https://devdocs.magento.com/page-builder/docs/index.html)
  - For end-users: [Page Builder User Guide](https://docs.magento.com/m2/ee/user_guide/cms/page-builder.html)