Clean up migrate-to-volto.md

Author: stevepiercy

docs/backend/upgrading/version-specific-migration/migrate-to-volto.md

@@ -30,36 +30,37 @@ This document discusses these differences.
 It also informs administrators and developers of how to migrate their existing Plone 6 site with Classic UI to instead become compatible with Volto for its frontend.
 
 ```{important}
-
-As a pre-requisite, your Plone site must be {ref}`upgraded to Plone 6<backend-upgrade-plone-v60-label>` before migrating to Volto for the frontend.
-
+As a pre-requisite, your Plone site must be {doc}`upgraded to Plone 6 <upgrade-to-60>` before migrating to Volto for the frontend.
 ```
 
 Plone provides a form `/@@migrate_to_volto` that allows you to run all the required changes to your existing site to make it compatible with Volto.
 
-You can access this form in the browser when you are logged in as an administrator.
+You can access this form in the browser when you are logged in as an Administrator.
 Open `http://localhost:8080/Plone/@@migrate_to_volto`, where `localhost` is your hostname, `8080` is the port on which Plone runs, and `Plone` is the name of the Plone instance.
 
-Additionally, after upgrading an existing site to Plone 6 (see {ref}`backend-upgrade-plone-v60-label`), a message will appear, **You can prepare your site for Volto, the default frontend of Plone 6!**, with a link to that form.
+Additionally, after upgrading an existing site to Plone 6 (see {doc}`upgrade-to-60`), a message will appear, **You can prepare your site for Volto, the default frontend of Plone 6!**, with a link to that form.
 
 ```{warning}
 Test all migrations thoroughly before applying them on a production environment!
 
 A site that is made compatible with Volto will be accessible with Plone Classic UI, but it will behave differently.
-For example, editors can only effectively work with the content using Volto because HTML is no longer editable in the TinyMCE editor used in Classic UI.
+For example, Editors can only effectively work with the content using Volto because HTML is no longer editable in the TinyMCE editor used in Classic UI.
 ```
 
+
+## Upgrade to Volto steps
+
 The required steps are:
 
 1.  **Install the packages {py:mod}`plone.volto` and {py:mod}`plone.restapi`.**
 
     {py:mod}`plone.restapi` is the RESTful API for Plone that allows the frontend Volto to communicate with the backend.
     {py:mod}`plone.volto` configures Plone to work with Volto, the new default frontend for Plone 6.
 
-1.  **Migrate RichText fields to Volto blocks**
+1.  **Migrate `RichText` fields to Volto blocks**
 
     Volto has a new editor called Slate, whereas Classic UI uses TinyMCE.
-    This step converts the HTML stored in RichText fields to text blocks, allowing you to edit them in Volto.
+    This step converts the HTML stored in `RichText` fields to text blocks, allowing you to edit them in Volto.
     Images, links, and most kinds of HTML formatting are preserved.
 
     For this you need to have `blocks-conversion-tool` running on an accessible URL.
@@ -84,20 +85,19 @@ The required steps are:
     This step turns all folders into folderish pages.
     If the folder shows a listing of the content, an appropriate listing block will be added.
     If the folder shows a default page, then it will be handled in the next step.
-    You can re-enable Folders by checking the box {guilabel}`Implicitly addable?` in ``/portal_types/Folder/manage_propertiesForm``.
+    You can re-enable Folders by checking the box {guilabel}`Implicitly addable?` in `/portal_types/Folder/manage_propertiesForm`.
 
 1.  **Default Pages of Folders are merged with the Folderish Pages that replace the Folder**
 
     Volto does not have a concept of default pages.
-    Instead folderish pages can show text, a listing of all the content inside that page, or both.
+    Instead, folderish pages can show text, a listing of all the content inside that page, or both.
     This step takes the content of the default page (such as text or the query of a collection), and adds that to the folderish page that replaces the folder.
     Metadata (subjects, author, rights, and so on) and relations are moved to the folderish page.
 
-
 1.  **Collections are migrated to Pages with Listing Blocks**
 
     In Volto adding Collections is disabled by default.
-    Instead folderish pages with listing blocks are used.
+    Instead, folderish pages with listing blocks are used.
     This step turns all collections into folderish pages.
     The criteria of the collection are used to configure a listing block in that page.