Merge branch 'MAGEDOC-3583' of github.com:magento-devdocs/magento2-page-builder into MAGEDOC-3583

Author: bdenham

docs/getting-started/install-pagebuilder-examples.md

@@ -1,25 +1,25 @@
 # Install Page Builder Examples
 
-You can find the code examples used and referred to within this documentation on GitHub in the [pagebuilder-examples repo](https://github.com/magento-devdocs/pagebuilder-examples).
+You can find the code examples used, and referred to, within this documentation on GitHub in the [pagebuilder-examples repo](https://github.com/magento-devdocs/pagebuilder-examples).
 This repo contains two types of examples:
 
 - Fully functional content type modules
 - Files for how-to topics
 
 ## Fully functional content type modules
 
-The custom content type modules are here for you to download and install so you can learn by example. These content type modules include the following three:
+The following custom content type modules are here for you to download and install so you can learn by example:
 
-- **[PageBuilderQuote](https://github.com/magento-devdocs/pagebuilder-examples/tree/master/PageBuilderQuote)** — This is the completed module featured in the [content type tutorial](../create-custom-content-type/overview.md). This module provides an example of a simple content type that provides stylized quotations you can use for things like customer testimonials.
-- **[PageBuilderGrid](https://github.com/magento-devdocs/pagebuilder-examples/tree/master/PageBuilderGrid)** — This module shows how you can create a content type to rebuild the Magento Luma home page using a grid structure with grid items.
-- **[PageBuilderFaq](https://github.com/magento-devdocs/pagebuilder-examples/tree/master/PageBuilderFaq)** — This module shows how you can create a content type for an FAQ page that uses an accordion for the questions and answers.
+- **[PageBuilderQuote](https://github.com/magento-devdocs/pagebuilder-examples/tree/master/PageBuilderQuote)**—This module shows you how to use a simple content type to stylize quotations for things like customer testimonials. This is the completed module featured in the [content type tutorial](../create-custom-content-type/overview.md).
+- **[PageBuilderGrid](https://github.com/magento-devdocs/pagebuilder-examples/tree/master/PageBuilderGrid)**—This module shows you how to create a content type to rebuild the Magento Luma home page using a grid structure with grid items.
+- **[PageBuilderFaq](https://github.com/magento-devdocs/pagebuilder-examples/tree/master/PageBuilderFaq)**—This module shows you how to create a content type for an FAQ page that uses an accordion for the questions and answers.
 
 ## Files for how-to topics
 
-This documentation contains several how-to topics for adding features to your content type. The corresponding how-to directories in the repo provide the code changes required for adding the feature to the PageBuilderQuote module.
+This documentation contains several how-to topics for adding features to your content type. The corresponding how-to directories in the repo provide the code changes required for adding the feature to the `PageBuilderQuote` module.
 
-For example, the topic [How to add a custom toolbar](../how-to/how-to-add-custom-toolbar.md), has a corresponding directory within the [pagebuilder-examples repo](https://github.com/magento-devdocs/pagebuilder-examples) called [how-to-add-custom-toolbar](https://github.com/magento-devdocs/pagebuilder-examples/tree/master/how-to-add-custom-toolbar). This directory provides the files with the code changes you need to make in order to add a custom toolbar to the PageBuilderQuote module.
+For example, the topic [How to add a custom toolbar](../how-to/how-to-add-custom-toolbar.md), has a corresponding directory within the [pagebuilder-examples repo](https://github.com/magento-devdocs/pagebuilder-examples) called [how-to-add-custom-toolbar](https://github.com/magento-devdocs/pagebuilder-examples/tree/master/how-to-add-custom-toolbar). This directory provides the files with the code changes you need to make in order to add a custom toolbar to the `PageBuilderQuote` module.
 
 
 
- 
+ 

docs/how-to/how-to-add-block-chooser.md

@@ -17,7 +17,7 @@ Extends all `abstract` configuration.
   <tr>
     <td><code>dataUrlConfigPath</code></td>
     <td>String</td>
-    <td>The path inside the Page Builder configuration object that points to the controller URL used to request data for display in the grid. </br>For example, if you utilize the <code>additional_data</code> configuration feature and you add the URL you could specify <code>content_types.mycontenttype.additional_data.my_cusom_property.my_data_url</code>.</td>
+    <td>The path inside the Page Builder configuration object that points to the controller URL used to request data for display in the grid. </br>For example, if you use the <code>additional_data</code> configuration feature and add the URL, you could specify <code>content_types.mycontenttype.additional_data.my_cusom_property.my_data_url</code>.</td>
   </tr>
   <tr>
     <td><code>requestParameter</code></td>

docs/how-to/how-to-add-icons-images.md

@@ -6,7 +6,7 @@ Page Builder Admin icons follow the same design principles as the core [Magento
 
 ## Page Builder icons
 
-Here are the available Page Builder Admin font icons (with class names) for use within your content type as needed:
+Here are the available Page Builder Admin font icons (with class names) for use within your content type:
 
 ![Page Builder admin icons](../images/pagebuilder-icons.png){:width="870px" height="auto"}
 
@@ -106,7 +106,7 @@ The following CSS rule set shows one general way to link your icons through CSS:
 }
 ```
 
-If you are creating an icon for the panel, replace the `background-image` attribute with `content` (as described in the content type tutorial, [Step 6: Add an icon](../create-custom-content-type/step-6-add-icon.md)).
+If you create an icon for the panel, replace the `background-image` attribute with `content` (as described in the content type tutorial, [Step 6: Add an icon](../create-custom-content-type/step-6-add-icon.md)).
 
 | Attribute              | Description                                                  |
 | ---------------------- | ------------------------------------------------------------ |

docs/how-to/how-to-deactivate-pagebuilder.md

@@ -1,8 +1,8 @@
 # How to deactivate Page Builder
 
-We recommend you deactivate the Page Builder editor through the Admin UI instead of disabling the module through the CLI using `bin/magento`. If you use the CLI, you could break various layouts, for example, the full-width layouts. Deactivating from the Admin UI allows the Page Builder module to continue rendering the content on the storefront even if the editor is not used in the Admin.
+We recommend deactivating the Page Builder editor through the Admin UI instead of disabling the module through the CLI using `bin/magento`. If you use the CLI, you could break various layouts, for example, the full-width layouts. Deactivating from the Admin UI allows the Page Builder module to continue rendering the content on the storefront even if the editor is not used in the Admin.
 
-Follow these steps to deactivate Page Builder within the Admin UI:
+Follow these steps to deactivate Page Builder in the Admin UI:
 
 1. In the **Stores** tab, select **Configuration** under the Settings group.
 2. In the **General** group on the page, select **Content Management**.

docs/index.md

@@ -1,7 +1,7 @@
 # What is Page Builder?
 
 Page Builder is a Magento extension for creating content with drag-and-drop controls. 
-We call these controls content types, which provide several key features including:
+We call these controls content types, which provide several key features, including:
 
 - **Dragging-and-dropping** of UI controls to build a page.
 - **Live previews** of how the content will look on the storefront.

docs/reference/architecture.md

@@ -55,7 +55,7 @@ The following is a simple overview of the data flow:
 
 1. Page Builder's reader() reads the data from associated elements in the persisted rendered output of the master format. It does this by traversing through the content type's DOM tree and searching for the associated elements declared in the content types definition XML. Then it uses the various attributes, styles, and other configurations to read the data from the specific area of the DOM element.
 2. Page Builder's element converters convert the data for each data mapping entry () to an internal supported format if required, this ensures the data collected from the DOM nodes is compatible with Page Builder's internal data store and UI component fields.
-3. Page Builder's mass converters can change data for all content type elements, not just one. For more details see [converter interface](configurations.md).
+3. Page Builder's mass converters can change data for all content type elements, not just one. For more details, see [converter interface](configurations.md).
 4. Page Builder creates its content types and populates the `Magento_PageBuilder/js/data-store` with data.
 5. End-users change the data in the data store within the form editor or when using the various live-editing options on the stage.
 6. Page Builder converts the data using mass converters.
@@ -129,14 +129,14 @@ For example:
 
 Page Builder stores data for content types in a simple object called the DataStore: `Magento_PageBuilder/js/data-store`.
 
-The parameter `name` from [content type configuration](configurations.md) is the name of a parameter in the DataStore.
+The `name` parameter from the [content type configuration](configurations.md) is the name of a parameter in the `DataStore`.
 You can use the `subscribe` method to listen for changes in the DataStore and perform custom actions on the data.
 
 This is how the system binds the data from the DataStore to your elements attribute or style. When you include a new attribute or style, you must specify where it should retrieve its data from the content type. These `name` values normally bind to the field names within UI component forms. The field names are the keys we use to save the data.
 
 ## Content type configuration
 
-Please see [content type configuration](configurations.md) for more information.
+See [content type configuration](configurations.md) for more information.
 
 ## Appearances
 

docs/reference/configurations.md

@@ -15,7 +15,7 @@ Use the content type and menu section configuration to add new content types, ex
 | `children`          | List of children content types that can accept this type as a parent.                                                                       |
 | `appearances`       | Appearance configuration.                                                                                                                   |
 | `is_system`        | Determines menu visibility for the component. System components should not be visible in the menu. Default value is true.                   |
-| `additional_data`   | Allows to specify additional data for component, see [additional configurations](../how-to/how-to-add-additional-configurations.md) for more information. |
+| `additional_data`   | Allows you to specify additional data for the component. See [additional configurations](../how-to/how-to-add-additional-configurations.md) for more information. |
 {:style="table-layout:auto"}
 
 | Attribute           | Description                                                                                                                                 |
@@ -518,4 +518,4 @@ Individual appearances may have different uiComponent forms in order to use diff
 |`fieldsToIgnoreOnRemove`| array containing field names to ignore when evaluating whether an element has been configured. The default value is an empty array. | `["tab_name"]` |
 {:style="table-layout:auto"}
 
-<!-- {% endraw %} -->
+<!-- {% endraw %} -->