archive and redirect deploys overview as its now part of the deployment overview

Author: rosieyohannan

docs/guides/modules/deploy/pages/deploys-overview.adoc renamed to archive/deploys-overview.adoc

@@ -25,4 +25,4 @@ For more information about Docker Layer Caching, refer to the xref:guides:optimi
 
 Visualise and control your deployments with CircleCI deploys. Deployments to Kubernetes and SageMaker are supported.
 
-Start with the xref:guides:deploy:deploys-overview.adoc[Deploys overview] for more information.
+Start with the xref:guides:deploy:deployment-overview.adoc[Deploys overview] for more information.

docs/guides/modules/ROOT/partials/shared-sections/features-of-circleci.adoc

@@ -66,7 +66,7 @@ From your organization home page you have access to org-level options. You can c
 
 **Projects**: Allows you to see all projects associated with your organization. Choose to follow or unfollow projects, as well as xref:getting-started:create-project.adoc[create/set up new projects].
 
-**Deploys**: Set up environment integrations to manage deployments for your projects. For full details of the deployments feature, see the xref:deploy:deploys-overview.adoc[Deploys overview] page.
+**Deploys**: Set up environment integrations to manage deployments for your projects. For full details of the deployments feature, see the xref:deploy:deployment-overview.adoc[Deployment overview] page.
 
 **Insights**: Provides you with time-series data overviews of credit usage, success rates, pipeline duration, and more. For full details of the Insights feature, see the xref:insights:insights.adoc[Using Insights] page.
 
@@ -160,7 +160,7 @@ The following settings are available in the project settings page. If you do not
 * A list of configured xref:orchestrate:pipelines.adoc#pipelines-and-triggers[pipeline triggers]
 * Set up UI for scheduled pipelines if available for your integration. To set up a xref:orchestrate:scheduled-pipelines.adoc[scheduled pipeline] you will define a timetable, parameter, and attribution to automatically run a pipeline when the criteria is met.
 
-**Deploys**: A UI for managing and viewing deployments. Setup and manage environment integrations, setup components. For full information on the deploys feature, start with the xref:deploy:deploys-overview.adoc[Deploys overview] page.
+**Deploys**: A UI for managing and viewing deployments. Setup and manage environment integrations, setup components. For full information on the deploys feature, start with the xref:deploy:deployment-overview.adoc[Deployment overview] page.
 
 **Advanced**: Toggle options on and off for:
 

docs/guides/modules/about-circleci/pages/introduction-to-the-circleci-web-app.adoc

@@ -10,7 +10,7 @@ This page provides the details of 3rd-party open source components used in Circl
 Release agent::
 +
 --
-The following 3rd-party open source components are used in the CircleCI release agent. The release agent is used to integrate CircleCI with Kubernetes clusters for release management. For more information, see the xref:deploy:deploys-overview.adoc[Deploys docs].
+The following 3rd-party open source components are used in the CircleCI release agent. The release agent is used to integrate CircleCI with Kubernetes clusters for release management. For more information, see the xref:deploy:deployment-overview.adoc[Deploys docs].
 
 [cols=2*, options="header", format=csv]
 |===

docs/guides/modules/about-circleci/pages/open-source.adoc

@@ -9,7 +9,7 @@ This how-to guide walks you through the steps to set up and use the Amazon SageM
 
 For further information about the orb and the CircleCI deploys feature see the following:
 
-* xref:deploys-overview.adoc[Deploys overview]
+* xref:deployment-overview.adoc[Deployment overview]
 * link:https://circleci.com/developer/orbs/orb/circleci/aws-sagemaker[Amazon SageMaker orb]
 * link:https://circleci.com/blog/amazon-sagemaker-deployment-orchestration/[**Blog post**: Using Amazon SageMaker orb to orchestrate model deployment across environments]
 
@@ -180,7 +180,7 @@ image::guides:ROOT:deploy/role-arn.png[Screenshot showing location of Role ARN]
 
 The CircleCI Amazon SageMaker orb requires some environment variables to function. You can store these environment variables at the project level, or you can store them using a xref:security:contexts.adoc[context]. The following steps show how to add the environment variables at the project level. You need to add two environment variables, as follows:
 
-* `CCI_RELEASE_INTEGRATION_TOKEN`: The orb connects your deployment to SageMaker with xref:deploys-overview.adoc[CircleCI deploys]. This gives you visibility into the Endpoint Configuration Updates, and what is currently active.
+* `CCI_RELEASE_INTEGRATION_TOKEN`: The orb connects your deployment to SageMaker with xref:deployment-overview.adoc[CircleCI deploys]. This gives you visibility into the Endpoint Configuration Updates, and what is currently active.
 * `SAGEMAKER_EXECUTION_ROLE_ARN`: This is the AWS IAM Role you configured with the necessary SageMaker permissions, and the OIDC Trust relationship.
 
 {empty} +

docs/guides/modules/deploy/pages/deploy-to-amazon-sagemaker.adoc

@@ -1,5 +1,5 @@
 = Deployment and deploy management overview
-:page-alias: deploys-overview
+:page-aliases: deploys-overview.adoc
 :page-platform: Cloud, Server v4+
 :page-description: Learn the basics of deployment and deploys management with CircleCI.
 :experimental:

docs/guides/modules/deploy/pages/deployment-overview.adoc

@@ -38,11 +38,11 @@ a| * Simple systems
 * A CircleCI account connected to your code. You can link:https://circleci.com/signup/[sign up for free].
 * A CircleCI project with a workflow configured to deploy your code.
 * Deploy markers *must* be configured in your project. Follow the xref:configure-deploy-markers.adoc[Configure Deploy Markers] guide to set this up.
-* Familiarity with CircleCI deploys concepts. Find full details in the xref:deploys-overview.adoc[CircleCI deploys overview] guide.
+* Familiarity with CircleCI deploys concepts. Find full details in the xref:deployment-overview.adoc[CircleCI deploys overview] guide.
 
 == Set up rollbacks
 
-The following steps guide you through setting up a custom rollback pipeline. This is the recommended rollback method.
+The following steps guide you through setting up a custom rollback pipeline. Using a custom rollback pipeline is the recommended rollback method.
 
 === 1. Navigate to project overview
 
@@ -54,7 +54,7 @@ You will see a red Rollback button with a dropdown option on the project overvie
 .Rollback options on project overview page
 image::guides:ROOT:deploy/project-overview-rollback.png[Rollback button on project overview page]
 
-The followng steps guide you through setting up a custom rollback pipeline. If you want details on how to *Rollback by workflow re-run*, see the <<rollback-by-workflow-re-run, Rollback by workflow re-run>> section at the end of this guide.
+The following steps guide you through setting up a custom rollback pipeline. If you want details on how to *Rollback by workflow re-run*, see the <<rollback-by-workflow-re-run, Rollback by workflow re-run>> section at the end of this guide.
 
 === 2. Start the rollback setup
 
@@ -145,7 +145,7 @@ The modal displays several configuration options with parameters auto-filled bas
 *Environment Name*:: The environment in which you wish to perform the rollback.
 *Current Version*:: Once you choose the component name and environment name, this will display all possible current versions. More often than not there should be just one current version available. You could have two in case a new progressive release is ongoing. Choose the version you believe is the current version of your component. To help you out, the relevant commit information is also displayed alongside the version.
 *Target Version*:: Choose the version you wish to rollback to. To help you out, the relevant commit information is also displayed alongside the version.
-*Namespace*:: This is optional. In case you use Kubernetes and do your deployments to a specific namespace, mention your namespace here, otherwise leave it empty.
+*Namespace*:: Optional. In case you use Kubernetes and do your deployments to a specific namespace, mention your namespace here, otherwise leave it empty.
 +
 The Parameters section shows the auto-filled parameters from your configuration file, which you can modify as needed for the specific rollback operation.
 
@@ -511,7 +511,7 @@ workflows:
 
 == Rollback by workflow re-run
 
-Workflow rerun rollbacks do not need any additional configuration beyond setting up deploy markers. There are advantages and disadvantages to using this method, as follows:
+Workflow rerun rollbacks do not need any additional configuration beyond setting up deploy markers. Advantages and disadvantages of using this method are as follows:
 
 * *Advantage*: No setup required. This rollback method works immediately after configuring deploy markers.
 * *Disadvantage*: The entire workflow will be re-run, which may not always be desirable depending on your workflow complexity and duration.

docs/guides/modules/deploy/pages/set-up-rollbacks.adoc

@@ -416,7 +416,7 @@ jobs:
       ... // other config
 ----
 
-Jobs with the `release` type are used to xref:guides:deploy:configure-your-kubernetes-components.adoc#link-release[connect your pipeline configuration] to a deployment in the CircleCI deploys UI. For full details, see the xref:guides:deploy:deploys-overview.adoc#[Deploys overview] page.
+Jobs with the `release` type are used to xref:guides:deploy:configure-your-kubernetes-components.adoc#link-release[connect your pipeline configuration] to a deployment in the CircleCI deploys UI. For full details, see the xref:guides:deploy:deployment-overview.adoc#[Deploys overview] page.
 
 **Example** of a job with a `release` type: