PB-427: Release notes 1.3

Rearranged order of features and updated content type upgrade library to clarify when content type developers should use the library.

Author: bdenham

docs/release-notes.md

@@ -9,23 +9,23 @@ The release notes include:
 
 ## **1.3.0** for Magento Commerce 2.3.5
 
-- {:.new}**Full Height Rows, Banners, and Sliders**<br/>
-   Page Builder Rows, Banners, and Sliders now have the option to set their heights to the full-height of the page using a number with any CSS unit (px, %, vh, em) or a calculation between units (100vh - 237px). These new features are documented here: [Rows](https://docs.magento.com/m2/ee/user_guide/cms/page-builder-layout-row.html), [Banners](https://docs.magento.com/m2/ee/user_guide/cms/page-builder-media-banner.html), [Sliders](https://docs.magento.com/m2/ee/user_guide/cms/page-builder-media-slider.html).
+- {:.new}**Templates**<br/>
+   Page Builder now has templates that can be created from existing content and applied to new content areas. Page Builder templates save both content and layouts of existing pages, blocks, dynamic blocks, product attributes, and category descriptions. For example, you can save an existing Page Builder CMS page as a template and then apply that template (with all its content and layouts) to quickly create new CMS Pages for your site. This new feature is documented here: [Templates](https://docs.magento.com/m2/ee/user_guide/cms/page-builder-templates.html).
 
 - {:.new}**Video Backgrounds for Rows, Banners, and Sliders**<br/>
    Page Builder Rows, Banners, and Sliders now have the option to use videos for their backgrounds. These new features are documented here: [Rows](https://docs.magento.com/m2/ee/user_guide/cms/page-builder-layout-row.html), [Banners](https://docs.magento.com/m2/ee/user_guide/cms/page-builder-media-banner.html), [Sliders](https://docs.magento.com/m2/ee/user_guide/cms/page-builder-media-slider.html).
 
 - {:.new}**Video support additions and enhancements**<br/>
    Page Builder now supports a wider variety of video formats. In addition to YouTube and Vimeo videos, the Video content type and the video backgrounds now support video URL links to video formats like `.mp4` and other browser-supported formats. The Video content type also adds an autoplay feature. These new features are documented here: [Video content type](https://docs.magento.com/m2/ee/user_guide/cms/page-builder-media-video.html).
 
-- {:.new}**Templates**<br/>
-   Page Builder now has templates that can be created from existing content and applied to new content areas. Page Builder templates save both content and layouts of existing pages, blocks, dynamic blocks, product attributes, and category descriptions. For example, you can save an existing Page Builder CMS page as a template and then apply that template (with all its content and layouts) to quickly create new CMS Pages for your site. This new feature is documented here: [Templates](https://docs.magento.com/m2/ee/user_guide/cms/page-builder-templates.html).
+- {:.new}**Full Height Rows, Banners, and Sliders**<br/>
+   Page Builder Rows, Banners, and Sliders now have the option to set their heights to the full-height of the page using a number with any CSS unit (px, %, vh, em) or a calculation between units (100vh - 237px). These new features are documented here: [Rows](https://docs.magento.com/m2/ee/user_guide/cms/page-builder-layout-row.html), [Banners](https://docs.magento.com/m2/ee/user_guide/cms/page-builder-media-banner.html), [Sliders](https://docs.magento.com/m2/ee/user_guide/cms/page-builder-media-slider.html).
 
 - {:.new}**Content type upgrade library**<br/>
-   We can now introduce new versions of Page Builder content types without introducing backward-incompatible issues with previous versions. Prior to this release, significant changes to content type configurations would create display and data-loss issues with previously saved Page Builder content types. Our new upgrade library eliminates these issues. The library upgrades previous versions of content types saved to the database to match the configuration changes of the new versions. The new upgrade library is documented here: [Upgrading content types](https://devdocs.magento.com/page-builder/docs/how-to/how-to-upgrade-content-types.html){:data-proofer-ignore='true'}.
+   We can now introduce new versions of Page Builder content types without introducing backward-incompatible issues with previous versions. Prior to this release, significant changes to content type configurations would create display and data-loss issues with previously saved Page Builder content types. Our new upgrade library eliminates these issues. We designed the library to upgrade previous versions of content types saved to the database so that they match the configuration changes in the new versions. Page Builder runs the upgrade library on native content types as needed for a new release. This ensures that the built-in Page Builder content types are always upgraded to match any changes we make to content types for a new release. Custom content type developers can also use this upgrade library when making configuration changes to new versions of their custom content types. More information and documentation for upgrading custom content types are provided here: [Upgrading content types](https://devdocs.magento.com/page-builder/docs/how-to/how-to-upgrade-content-types.html){:data-proofer-ignore='true'}.
 
    {: .bs-callout .bs-callout-info }
-   Page Builder automatically runs the upgrade library when we add a patch to a new release. This ensures that the _native_ Page Builder content types are always upgraded to match any changes made to content types for a new release. However, to upgrade previous versions of your _custom_ Page Builder content types requires additional development, as noted in the previous documentation link.
+   Unless you are a custom content type developer making configuration changes to your own custom Page Builder content types, there is no need to use the upgrade library. As with Page Builder's native content types, you only need to use the library when you make configuration changes that create display and data-loss issues with your previously saved custom content types.
 
 - {:.new}**Documentation on adding new Appearances**<br/>
    Everything you need to know about [adding appearances](https://devdocs.magento.com/page-builder/docs/how-to/how-to-add-appearance.html) for existing or custom content types.