update links to use versions for docs

Author: stevepiercy

docs/backend/upgrading/preparations.md

@@ -57,7 +57,7 @@ Always back up your Plone site before upgrading.
 ```
 
 ```{seealso}
-See Plone 5.2 documentation, [Backing up your Plone deployment](https://docs.plone.org/manage/deploying/backup.html).
+See Plone 5.2 documentation, [Backing up your Plone deployment](https://5.docs.plone.org/manage/deploying/backup.html).
 ```
 
 ```{todo}

docs/backend/upgrading/troubleshooting.md

@@ -44,7 +44,7 @@ Watch for error messages in the console.
 You may be able to find more information about the error messages in the following documents.
 
 -   {doc}`Version-specific migration tips </backend/upgrading/version-specific-migration/index>` for your version of Plone
--   [Error Reference](https://docs.plone.org/appendices/error-reference.html)
+-   [Error Reference](https://5.docs.plone.org/appendices/error-reference.html)
 
 ```{todo}
 See https://github.com/plone/documentation/issues/1323

docs/backend/upgrading/version-specific-migration/p4x-to-p5x-upgrade.md

@@ -219,7 +219,7 @@ See https://github.com/smcmahon/Products.PloneFormGen/blob/master/Products/Plone
 ## Resource registry
 
 ```{seealso}
-https://docs.plone.org/adapt-and-extend/theming/resourceregistry.html
+https://5.docs.plone.org/adapt-and-extend/theming/resourceregistry.html
 ```
 
 Plone 5 introduces some new concepts, for some, with working with JavaScript in Plone.
@@ -247,7 +247,7 @@ It also would combine and minify them for you in deployment mode.
 
 #### Registration Changes
 
-Prior to Plone 5, JavaScript files were added to the registry by using a [`GenericSetup` Profile](https://docs.plone.org/develop/addons/components/genericsetup.html) and including a `jsregistry.xml` file to it.
+Prior to Plone 5, JavaScript files were added to the registry by using a [`GenericSetup` Profile](https://5.docs.plone.org/develop/addons/components/genericsetup.html) and including a `jsregistry.xml` file to it.
 
 This would add your JavaScript to the registry, with some options and potentially set ordering.
 

docs/backend/upgrading/version-specific-migration/upgrade-addons-to-51.md

@@ -32,7 +32,7 @@ If you must use the old way, you can still use the `portal_quickinstaller` in th
 In a lot of cases, you can configure XML files instead of using Python code.
 In other cases you may need to write custom installer code (`setuphandlers.py`).
 
-See https://docs.plone.org/develop/addons/components/genericsetup.
+See https://5.docs.plone.org/develop/addons/components/genericsetup.
 
 
 ### Default Profile

docs/backend/upgrading/version-specific-migration/upgrade-to-51.md

@@ -61,7 +61,7 @@ To make use of this, you should register your resource bundle to merge with the
 ```
 
 ```{seealso}
-See https://docs.plone.org/adapt-and-extend/theming/resourceregistry.html#resource-bundle-aggregation.
+See https://5.docs.plone.org/adapt-and-extend/theming/resourceregistry.html#resource-bundle-aggregation.
 ```
 
 
@@ -81,7 +81,7 @@ Actions can be re-ordered, hidden, or displayed.
 ```
 
 ```{seealso}
-See https://docs.plone.org/develop/plone/functionality/actions.html#creating-actions-through-the-web.
+See https://5.docs.plone.org/develop/plone/functionality/actions.html#creating-actions-through-the-web.
 ```
 
 
@@ -283,7 +283,7 @@ The [collective.indexing](https://pypi.org/project/collective.indexing) package
 This makes sure that objects are only indexed once per transaction.
 
 It also gives {term}`hooks` for calling external indexers, like Solr and Elasticsearch.
-See https://docs.plone.org/develop/plone/searching_and_indexing/external-catalogs.html.
+See https://5.docs.plone.org/develop/plone/searching_and_indexing/external-catalogs.html.
 
 There is a workaround when you get {ref}`catalog-errors-during-upgrades-label`.
 

docs/backend/upgrading/version-specific-migration/upgrade-to-52.md

@@ -313,7 +313,7 @@ Nothing changes.
 Support for old-style resource registries (`cssregistry.xml` and `jsregistry.xml`) was removed completely, along with the tools `portal_css` or `portal_javascript`.
 
 You need to add resources using the new Resource Registry.
-See https://docs.plone.org/adapt-and-extend/theming/resourceregistry.html#resources for detailed instructions.
+See https://5.docs.plone.org/adapt-and-extend/theming/resourceregistry.html#resources for detailed instructions.
 
 
 ### Restructure `CMFPlone` static resources

docs/backend/upgrading/version-specific-migration/upgrade-to-python3.md

@@ -150,7 +150,7 @@ Check this [Cheat Sheet](https://python-future.org/compatible_idioms.html) with
 `python-modernize` adds an import of the compatibility library `six` if needed.
 The import is added as the last import, therefore it is often necessary to reorder the imports.
 The easiest way is to use [isort](https://pypi.org/project/isort), which does this for you automatically.
-Check the [Python style guide for Plone](https://docs.plone.org/develop/styleguide/python.html#grouping-and-sorting) for information about the order of imports and an example configuration for `isort`.
+Check the [Python style guide for Plone](https://5.docs.plone.org/develop/styleguide/python.html#grouping-and-sorting) for information about the order of imports and an example configuration for `isort`.
 
 If `six` is used in the code, make sure that `six` is added to the `install_requires` list in the `setup.py` of the package.
 

docs/install/install-from-packages.md

@@ -183,7 +183,7 @@ We install Plone 6 with {term}`pip`, {term}`Cookiecutter`, {term}`mxdev`, {term}
 ```{note}
 We do not maintain documentation for installing Plone 6 or later with `buildout`.
 For Plone 5, `buildout` was the preferred installation method.
-You can read the [documentation of how to install Plone 5 with `buildout`](https://docs.plone.org/manage/installing/installation_minimal_buildout.html), and adapt it to your needs for Plone 6.
+You can read the [documentation of how to install Plone 5 with `buildout`](https://5.docs.plone.org/manage/installing/installation_minimal_buildout.html), and adapt it to your needs for Plone 6.
 ```
 
 Create a new directory to hold your project, and make it your current directory.