requested changes

Author: alizgirl

docs/backend/upgrading/intro.md

@@ -20,7 +20,7 @@ Upgrading Plone includes the Plone application and its add-ons, as well as migra
 
 A *migration* is the process of taking a component in your Plone site, and moving it from its current version to a newer one.
 Migration is necessary because the internals of Plone sometimes change to support new functionality.
-When that's the case, the content that is stored in your Zope instance may not align with the requirements of the new version.
+When that's the case, the content that is stored in your Plone site may not align with the requirements of the new version.
 To handle this situation, Plone has a built-in tool that migrates existing content to the new structure.
 
 Before migrating you should read this entire document, as well as {ref}`introduction-version-specific-upgrade-guides-label`, to understand the potential impact migrating will have on your Plone site.

docs/backend/upgrading/troubleshooting.md

@@ -84,9 +84,9 @@ If the problem disappears, you will need to double-check the offending product.
     Re-install it and check the installation log.
 
 
-(upgrading-troubleshooting-test-with-a-fresh-plone-instance-label)=
+(upgrading-troubleshooting-test-with-a-fresh-plone-site-label)=
 
-## Test with a fresh Zope instance
+## Test with a fresh Plone site
 
 Create a new Plone site with your new version of Plone.
 You do not need a new Zope instance, because you can add another Plone site in the root of Zope.

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

@@ -36,7 +36,7 @@ As a pre-requisite, your Plone site must be {doc}`upgraded to Plone 6 <upgrade-t
 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.
-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 Zope instance.
+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 site.
 
 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.
 

docs/classic-ui/layers.md

@@ -20,8 +20,8 @@ Layers are useful in the following scenarios.
 Layers are marker interfaces applied to the {term}`HTTPRequest` object.
 They are usually used in conjunction with Zope Configuration Mark-up Language ({term}`ZCML`) directives to dynamically activate various parts of the configuration, such as theme files or add-on product functionality.
 
-Layers ensure that only one add-on product can override the specific Zope instance functionality in your site at a time, while still allowing you to have possibly conflicting add-on products in your buildout and ZCML.
-Multiple Plone site instances can share the same ZCML and code files.
+Layers ensure that only one add-on product can override the specific Zope view in your site at a time, while still allowing you to have possibly conflicting add-on products in your buildout and ZCML.
+Multiple Plone sites can share the same ZCML and code files.
 
 Many ZCML directives take the optional `layer` parameter.
 Layers are activated when an add-on product is installed or a certain theme is activated.