Changed plone instances to zope instances

alizgirl · alizgirl · commit 49ca1a14853c · 2025-01-17T15:34:26.000+02:00
diff --git a/docs/_inc/_create-classic-ui-instance.md b/docs/_inc/_create-classic-ui-instance.md
@@ -11,5 +11,5 @@ Enter values in the form, and click the button {guilabel}`Create Plone Site`.
 
 You will be redirected to your new Classic UI Plone site.
 
-To stop the Plone instance in foreground mode, type {kbd}`ctrl-c`.
+To stop the Zope instance in foreground mode, type {kbd}`ctrl-c`.
 
diff --git a/docs/backend/upgrading/intro.md b/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 Plone instance may not align with the requirements of the new version.
+When that's the case, the content that is stored in your Zope instance 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.
diff --git a/docs/backend/upgrading/troubleshooting.md b/docs/backend/upgrading/troubleshooting.md
@@ -86,7 +86,7 @@ If the problem disappears, you will need to double-check the offending product.
 
 (upgrading-troubleshooting-test-with-a-fresh-plone-instance-label)=
 
-## Test with a fresh Plone instance
+## Test with a fresh Zope instance
 
 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.
diff --git a/docs/backend/upgrading/version-specific-migration/migrate-to-volto.md b/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 Plone 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 Zope instance.
 
 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.
 
diff --git a/docs/backend/upgrading/version-specific-migration/p4x-to-p5x-upgrade.md b/docs/backend/upgrading/version-specific-migration/p4x-to-p5x-upgrade.md
@@ -74,7 +74,7 @@ When the email addresses are not unique, for example you have both `joe@example.
 It is best is to fix this in your site in Plone 4
 Change email addresses or remove no longer needed users.
 When there are only a few users, you can do this manually.
-To assist you in sites with many users, in Plone 4.1 and higher, you can add the [collective.emaillogin4](https://pypi.org/project/collective.emaillogin4) package to the eggs of your Plone instance.
+To assist you in sites with many users, in Plone 4.1 and higher, you can add the [collective.emaillogin4](https://pypi.org/project/collective.emaillogin4) package to the eggs of your Zope instance.
 
 With that package, even without installing it in the add-ons control panel, you can call the `@@migrate-to-emaillogin` page to look for duplicate email addresses.
 
diff --git a/docs/backend/upgrading/version-specific-migration/plone5-minor-upgrade.md b/docs/backend/upgrading/version-specific-migration/plone5-minor-upgrade.md
@@ -51,7 +51,7 @@ Save your changes.
 
 ### Upgrading
 
-Stop your Plone instance:
+Stop your Zope instance:
 
 ```console
 bin/plonectl stop
@@ -65,7 +65,7 @@ bin/buildout
 
 This may take a some time, as Plone downloads new releases.
 
-When buildout finishes running, restart your Plone instance:
+When buildout finishes running, restart your Zope instance:
 
 ```console
 bin/plonectl start
diff --git a/docs/backend/upgrading/version-specific-migration/upgrade-to-61.md b/docs/backend/upgrading/version-specific-migration/upgrade-to-61.md
@@ -54,7 +54,7 @@ To upgrade your plugin implementation to TinyMCE 7, see the [upgrade guides](htt
         bin/buildout
         ```
     
-1.  Start your Plone instance.
+1.  Start your Zope instance.
 
     ```shell
     bin/instance fg
diff --git a/docs/classic-ui/csrf.md b/docs/classic-ui/csrf.md
@@ -171,7 +171,7 @@ def some_function(request):
     # modify the database here
 ```
 
-Disabling all CSRF protection for the whole Plone instance is possible by starting Plone with the environment variable `PLONE_CSRF_DISABLED=true` set.
+Disabling all CSRF protection for the whole Zope instance is possible by starting Plone with the environment variable `PLONE_CSRF_DISABLED=true` set.
 This is not recommended but can be handy temporarily in special situations.
 
 
diff --git a/docs/classic-ui/images.md b/docs/classic-ui/images.md
@@ -78,7 +78,7 @@ This is useful for caching URLs in Varnish or the browser.
 In case the uploaded image or scale definitions have changed, they will be saved again under a different UID.
 This changes the URL and forces either the browser, or a cache proxy such as Varnish, to fetch it again.
 When a scale has changed, the old stored entry in the annotation will be deleted after 24 hours.
-If one changes an image which is used in multiple pages, the updated versions will only be shown after a restart of the Plone instance, saving the pages again, or after 24 hours.
+If one changes an image which is used in multiple pages, the updated versions will only be shown after a restart of the Zope instance, saving the pages again, or after 24 hours.
 
 
 (classic-ui-images-image-tag-label)=
diff --git a/docs/classic-ui/layers.md b/docs/classic-ui/layers.md
@@ -20,7 +20,7 @@ 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 Plone instance functionality in your site at a time, while still allowing you to have possibly conflicting add-on products in your buildout and ZCML.
+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.
 
 Many ZCML directives take the optional `layer` parameter.
diff --git a/docs/deployment/caching/enable.md b/docs/deployment/caching/enable.md
@@ -125,7 +125,7 @@ When the caching control panel is not there, there can be various reasons for th
 
 If you want to install it in an existing Plone Site:
 
-1.  Make sure the package is available in the Plone instance by adding `plone.app.caching` or `Plone` to your installation.
+1.  Make sure the package is available in the Zope instance by adding `plone.app.caching` or `Plone` to your installation.
 2.  From the Plone Site Setup, under the {guilabel}`Advanced` heading or navigation item, select the <img alt="Management Interface" src="/_static/caching/icon-management-interface.svg" class="inline"> {guilabel}`Management Interface` control panel.
 3.  Click {guilabel}`portal_setup`, and then click the {guilabel}`Import` tab.
 4.  Select the profile by title {guilabel}`HTTP caching support`, or by id {guilabel}`profile-plone.app.caching:default`.
diff --git a/docs/install/containers/examples/haproxy-plone-zeo.md b/docs/install/containers/examples/haproxy-plone-zeo.md
@@ -17,7 +17,7 @@ We will use the image [`plone/plone-haproxy`](https://github.com/plone/plone-hap
 
 ## Setup
 
-Create a directory for your project, and inside it create a `docker-compose.yml` file that starts your Plone instance and the ZEO instance with volume mounts for data persistence.
+Create a directory for your project, and inside it create a `docker-compose.yml` file that starts your Zope instance and the ZEO instance with volume mounts for data persistence.
 
 ```yaml
 version: "3"
diff --git a/docs/install/containers/images/zeo.md b/docs/install/containers/images/zeo.md
@@ -26,7 +26,7 @@ docker run -p 8100:8100 plone/plone-zeo:latest
 
 ### Service configuration with Docker Compose
 
-Create a directory for your project, and inside it create a `docker-compose.yml` file that starts your Plone instance and the ZEO instance with volume mounts for data persistence:
+Create a directory for your project, and inside it create a `docker-compose.yml` file that starts your Zope instance and the ZEO instance with volume mounts for data persistence:
 
 ```yaml
 version: "3"

Original file line number	Diff line number	Diff line change
@@ -11,5 +11,5 @@ Enter values in the form, and click the button {guilabel}`Create Plone Site`.
`11`	`11`
`12`	`12`	`You will be redirected to your new Classic UI Plone site.`
`13`	`13`
`14`		-To stop the Plone instance in foreground mode, type {kbd}`ctrl-c`.
	`14`	+To stop the Zope instance in foreground mode, type {kbd}`ctrl-c`.
`15`	`15`