From 180ca0f8b827d175333ab02ed4173edfa8f36b32 Mon Sep 17 00:00:00 2001
From: charanya <charanya.jayaraman@harness.io>
Date: Tue, 25 Apr 2023 15:05:26 +0530
Subject: [PATCH 1/2] added a note in AS rules creation topics and fixed some
 minor cosmetic issues

---
 .../ccm-roles-and-permissions.md              |  3 +-
 ...anage-access-control-for-ccm-dashboards.md |  4 ++-
 ...nage-access-control-perspective-folders.md |  4 ++-
 .../create-auto-stopping-rules-for-azure.md   |  5 +++-
 .../create-auto-stopping-rules-for-ecs.md     |  1 -
 .../create-auto-stopping-rules-for-gcp.md     | 12 ++++----
 .../create-autostopping-rules-aws.md          | 10 ++++++-
 ...reate-autostopping-rules-for-kubernetes.md | 30 ++++++++++++-------
 .../cost-optimization-governance.md           |  4 +--
 docs/cloud-cost-management/6-ccm-auditing.md  |  3 +-
 .../_category_.json                           |  2 +-
 src/components/Docs/CloudCostManagement.tsx   |  4 +--
 12 files changed, 54 insertions(+), 28 deletions(-)

diff --git a/docs/cloud-cost-management/2-getting-started-ccm/5-access-control/ccm-roles-and-permissions.md b/docs/cloud-cost-management/2-getting-started-ccm/5-access-control/ccm-roles-and-permissions.md
index 1dcc8961df0..700739f876a 100644
--- a/docs/cloud-cost-management/2-getting-started-ccm/5-access-control/ccm-roles-and-permissions.md
+++ b/docs/cloud-cost-management/2-getting-started-ccm/5-access-control/ccm-roles-and-permissions.md
@@ -1,5 +1,5 @@
 ---
-title: CCM RBAC
+title: RBAC
 description: Harness RBAC includes Roles and Permissions that enable you to control access to the CCM resources in your Harness account. CCM Roles and Permissions are Account Level Only. Most Roles and Permission…
 # sidebar_position: 2
 helpdocs_topic_id: di9dut7jki
@@ -8,6 +8,7 @@ helpdocs_is_private: false
 helpdocs_is_published: true
 ---
 
+# CCM Roles and Permissions
 Harness RBAC includes Roles and Permissions that enable you to control access to the CCM resources in your Harness account.
 
 ## CCM Roles and Permissions are Account Level Only
diff --git a/docs/cloud-cost-management/2-getting-started-ccm/5-access-control/manage-access-control-for-ccm-dashboards.md b/docs/cloud-cost-management/2-getting-started-ccm/5-access-control/manage-access-control-for-ccm-dashboards.md
index 76b2ed420d9..dd04ef97768 100644
--- a/docs/cloud-cost-management/2-getting-started-ccm/5-access-control/manage-access-control-for-ccm-dashboards.md
+++ b/docs/cloud-cost-management/2-getting-started-ccm/5-access-control/manage-access-control-for-ccm-dashboards.md
@@ -1,5 +1,5 @@
 ---
-title: Manage access control for CCM dashboards
+title: Dashboards
 description: This topic describes how to add and manage access control for CCM Dashboards.
 # sidebar_position: 2
 helpdocs_topic_id: ng6yaxqi2r
@@ -8,6 +8,8 @@ helpdocs_is_private: false
 helpdocs_is_published: true
 ---
 
+# Manage access control for CCM dashboards
+
 Harness provides Role-Based Access Control (RBAC) that enables you to control user and group access to Harness Resources according to their role assignment.
 
 This topic describes how to add and manage access control for CCM Dashboards.
diff --git a/docs/cloud-cost-management/2-getting-started-ccm/5-access-control/manage-access-control-perspective-folders.md b/docs/cloud-cost-management/2-getting-started-ccm/5-access-control/manage-access-control-perspective-folders.md
index f5cdb11bb38..8cca8dd5857 100644
--- a/docs/cloud-cost-management/2-getting-started-ccm/5-access-control/manage-access-control-perspective-folders.md
+++ b/docs/cloud-cost-management/2-getting-started-ccm/5-access-control/manage-access-control-perspective-folders.md
@@ -1,9 +1,11 @@
 ---
-title: Manage access control for CCM perspective folders
+title: Perspective folders
 description: This topic describes how to add and manage access control for CCM Perspectives folder.
 # sidebar_position: 2
 ---
 
+# Manage access control for CCM perspective folders
+
 You can now manage access to Perspective folders by assigning Resource Groups to users bound by the roles assigned to them.
 
 The following steps illustrate how to restrict access to a Resource Group:
diff --git a/docs/cloud-cost-management/4-use-ccm-cost-optimization/1-optimize-cloud-costs-with-intelligent-cloud-auto-stopping-rules/4-create-auto-stopping-rules/create-auto-stopping-rules-for-azure.md b/docs/cloud-cost-management/4-use-ccm-cost-optimization/1-optimize-cloud-costs-with-intelligent-cloud-auto-stopping-rules/4-create-auto-stopping-rules/create-auto-stopping-rules-for-azure.md
index 01c2d4deecb..0ff490f7c4f 100644
--- a/docs/cloud-cost-management/4-use-ccm-cost-optimization/1-optimize-cloud-costs-with-intelligent-cloud-auto-stopping-rules/4-create-auto-stopping-rules/create-auto-stopping-rules-for-azure.md
+++ b/docs/cloud-cost-management/4-use-ccm-cost-optimization/1-optimize-cloud-costs-with-intelligent-cloud-auto-stopping-rules/4-create-auto-stopping-rules/create-auto-stopping-rules-for-azure.md
@@ -148,6 +148,10 @@ In certain scenarios, you would not want your resources to go down or up. For ex
 The fixed schedule takes precedence over the defined AutoStopping Rule.
 :::
 
+:::note
+Harness executes scheduled rules using [Dkron](https://dkron.io/), an open-source workload automation service.
+:::
+
 To create a fixed schedule for your rule, do the following:
 
 1. In **Fixed Schedules**, click **Add Fixed Schedule**.
@@ -228,7 +232,6 @@ The list populates the application gateway if the application gateway has previo
 
 
 
-
 #### Enter Routing Configuration and Health Check Details
 This is an application gateway routing configuration for the underlying application that is running on the cloud resources managed by this AutoStopping Rule.
 
diff --git a/docs/cloud-cost-management/4-use-ccm-cost-optimization/1-optimize-cloud-costs-with-intelligent-cloud-auto-stopping-rules/4-create-auto-stopping-rules/create-auto-stopping-rules-for-ecs.md b/docs/cloud-cost-management/4-use-ccm-cost-optimization/1-optimize-cloud-costs-with-intelligent-cloud-auto-stopping-rules/4-create-auto-stopping-rules/create-auto-stopping-rules-for-ecs.md
index 48613dd534d..0231e9d571a 100644
--- a/docs/cloud-cost-management/4-use-ccm-cost-optimization/1-optimize-cloud-costs-with-intelligent-cloud-auto-stopping-rules/4-create-auto-stopping-rules/create-auto-stopping-rules-for-ecs.md
+++ b/docs/cloud-cost-management/4-use-ccm-cost-optimization/1-optimize-cloud-costs-with-intelligent-cloud-auto-stopping-rules/4-create-auto-stopping-rules/create-auto-stopping-rules-for-ecs.md
@@ -104,7 +104,6 @@ If you chose **ECS Service Tags**, select the region, cluster, and the tag assoc
 :::
 
 
-
 ![](./static/aws-ecs-use-tags.png)
 
    
diff --git a/docs/cloud-cost-management/4-use-ccm-cost-optimization/1-optimize-cloud-costs-with-intelligent-cloud-auto-stopping-rules/4-create-auto-stopping-rules/create-auto-stopping-rules-for-gcp.md b/docs/cloud-cost-management/4-use-ccm-cost-optimization/1-optimize-cloud-costs-with-intelligent-cloud-auto-stopping-rules/4-create-auto-stopping-rules/create-auto-stopping-rules-for-gcp.md
index a09ed180c1b..1a2f52365e7 100644
--- a/docs/cloud-cost-management/4-use-ccm-cost-optimization/1-optimize-cloud-costs-with-intelligent-cloud-auto-stopping-rules/4-create-auto-stopping-rules/create-auto-stopping-rules-for-gcp.md
+++ b/docs/cloud-cost-management/4-use-ccm-cost-optimization/1-optimize-cloud-costs-with-intelligent-cloud-auto-stopping-rules/4-create-auto-stopping-rules/create-auto-stopping-rules-for-gcp.md
@@ -66,7 +66,6 @@ You can add multiple instances to a single Rule. However, all the VMs should be
 3. Select the instances that you want to manage using the AutoStopping rules. You can use the search option to search the instances.
    
 
-   
 ![](./static/create-auto-stopping-rules-for-gcp-19.png)
 
 4. Click **Add Selected** to select the instances.
@@ -110,6 +109,9 @@ In certain scenarios, you would not want your resources to go down or up. For ex
 The fixed schedule takes precedence over the defined AutoStopping Rule.
 :::
 
+:::note
+Harness executes scheduled rules using [Dkron](https://dkron.io/), an open-source workload automation service.
+:::
 
 To create a fixed schedule for your rule, do the following:
 
@@ -126,10 +128,10 @@ To create a fixed schedule for your rule, do the following:
 	  If you don't specify an end time, the schedule continues to run until you manually update the settings or remove the schedule.
 6. Select the checbox **Never ends** if you do not want to set end time for your schedule.
 7. You can also set a recurring schedule for the rule. If you want to set a recurring schedule, in **Uptime/Downtime in the selected period**, in **Repeats**, select the repeat frequency.
-	3. Select which days of the week you'd like your schedule to repeat. You can choose any day between Sunday and Saturday.
-	4. Select **Everyday**, to set the schedule for all seven days of the week.
-	5. Set your repeat schedule's beginning and ending time. In the **Time** field, specify the start and end time for the fixed schedule.
-	6. Select **All Day**, if you wish to set your schedule for the entire day. If you choose All Day for your schedule, you won't be able to choose a start and end time.  
+	1. Select which days of the week you'd like your schedule to repeat. You can choose any day between Sunday and Saturday.
+	2. Select **Everyday**, to set the schedule for all seven days of the week.
+	3. Set your repeat schedule's beginning and ending time. In the **Time** field, specify the start and end time for the fixed schedule.
+	4. Select **All Day**, if you wish to set your schedule for the entire day. If you choose All Day for your schedule, you won't be able to choose a start and end time.  
 	  
 	**Example 1**:  
 	In the following example, resources are up every Mon, Tue, Wed starting from 12:00 a.m. on February 14, 2022 till April 30, at 10:00 p.m.
diff --git a/docs/cloud-cost-management/4-use-ccm-cost-optimization/1-optimize-cloud-costs-with-intelligent-cloud-auto-stopping-rules/4-create-auto-stopping-rules/create-autostopping-rules-aws.md b/docs/cloud-cost-management/4-use-ccm-cost-optimization/1-optimize-cloud-costs-with-intelligent-cloud-auto-stopping-rules/4-create-auto-stopping-rules/create-autostopping-rules-aws.md
index 8d19d066077..baa6d1e2ed3 100644
--- a/docs/cloud-cost-management/4-use-ccm-cost-optimization/1-optimize-cloud-costs-with-intelligent-cloud-auto-stopping-rules/4-create-auto-stopping-rules/create-autostopping-rules-aws.md
+++ b/docs/cloud-cost-management/4-use-ccm-cost-optimization/1-optimize-cloud-costs-with-intelligent-cloud-auto-stopping-rules/4-create-auto-stopping-rules/create-autostopping-rules-aws.md
@@ -210,7 +210,15 @@ Create fixed uptime or downtime schedules for the resources managed by this Auto
 
 In certain scenarios, you would not want your resources to go down or up. For example, every Friday at 5 p.m. you want your `ABC` resource to go down. You can schedule downtime for your `ABC` resource. During this window, the resource is forced to go down regardless of the defined rule. You can choose to specify uptime for your resources in the same way.
 
-The fixed schedule takes precedence over the defined AutoStopping Rule.To create a fixed schedule for your rule, do the following:
+:::note
+The fixed schedule takes precedence over the defined AutoStopping Rule. 
+:::
+
+:::note
+Harness executes scheduled rules using [Dkron](https://dkron.io/), an open-source workload automation service.
+:::
+
+To create a fixed schedule for your rule, do the following:
 
 1. In **Fixed Schedules**, click **Add Fixed Schedule**.
    
diff --git a/docs/cloud-cost-management/4-use-ccm-cost-optimization/1-optimize-cloud-costs-with-intelligent-cloud-auto-stopping-rules/4-create-auto-stopping-rules/create-autostopping-rules-for-kubernetes.md b/docs/cloud-cost-management/4-use-ccm-cost-optimization/1-optimize-cloud-costs-with-intelligent-cloud-auto-stopping-rules/4-create-auto-stopping-rules/create-autostopping-rules-for-kubernetes.md
index 326753269e5..dffc05fff9c 100644
--- a/docs/cloud-cost-management/4-use-ccm-cost-optimization/1-optimize-cloud-costs-with-intelligent-cloud-auto-stopping-rules/4-create-auto-stopping-rules/create-autostopping-rules-for-kubernetes.md
+++ b/docs/cloud-cost-management/4-use-ccm-cost-optimization/1-optimize-cloud-costs-with-intelligent-cloud-auto-stopping-rules/4-create-auto-stopping-rules/create-autostopping-rules-for-kubernetes.md
@@ -10,7 +10,7 @@ helpdocs_is_published: true
 
 AutoStopping Rules make sure that your non-production resources run only when used, and never when idle. 
 
-## Before You Begin
+## Before you begin
 
 * [Create a Kubernetes Connector for AutoStopping Rules](../1-add-connectors/k8s-connector-autostopping.md)
 * [AutoStopping Rules Overview](../1-add-connectors/1-auto-stopping-rules.md)
@@ -32,7 +32,7 @@ The following section lists the support for Kubernetes clusters for AutoStopping
 	+ Ensure that you have access to (Cost Usage Report) CUR. See [Review: Cost and Usage Reports (CUR) and CCM Requirements](../../../2-getting-started-ccm/4-set-up-cloud-cost-management/set-up-cost-visibility-for-aws.md#cost-and-usage-reports-cur-and-ccm-requirements)
 	+ Permissions to create a cross-account role. See [AWS Access Permissions](../../../2-getting-started-ccm/4-set-up-cloud-cost-management/set-up-cost-visibility-for-aws.md#aws-access-permissions)
 
-## Step 1: Add a Cloud Provider
+## Add a cloud provider
 
 Perform the following steps to link your Kubernetes cluster to Harness for creating AutoStopping Rules:
 
@@ -53,11 +53,11 @@ You can select any of the following cloud account types:
   
 For the detailed steps, see the [Create a Kubernetes Connector for AutoStopping Rules](../1-add-connectors/k8s-connector-autostopping.md).
 
-## Step 2: Add a New AutoStopping Rule
+## Add a new AutoStopping rule
 
 Perform the following steps to add a new AWS AutoStopping rule for Kubernetes clusters:
 
-### Step 1: Define an AutoStopping Rule
+### Define an AutoStopping rule
 
 Perform the following steps to get started with AutoStopping Rule.
 
@@ -72,7 +72,7 @@ For the detailed steps, see [Create a Kubernetes Connector for AutoStopping Rule
 4. In **Define your AutoStopping rule**, in **Name your Rule**, enter a name for your rule. This is the name of your AutoStopping rule.
 5. In **Idle time**, enter the idle time in minutes. This is the time that the AutoStopping rule will wait before stopping the idle instances.
 
-### Step 2: Select the Resources to be Managed by the AutoStopping Rule
+### Select the Resources to be Managed by the AutoStopping Rule
 
 Select the Kubernetes workload that you want to manage using this rule. AutoStopping Rule will monitor the selected resources and stop them when they are idle beyond the configured idle time.
 
@@ -80,11 +80,11 @@ Select the Kubernetes workload that you want to manage using this rule. AutoStop
 2. Select the Kubernetes cluster that you want to manage using the AutoStopping rules. If you wish to create a new connector for the Kubernetes cluster, see [Create a Kubernetes Connector for AutoStopping Rules](../1-add-connectors/k8s-connector-autostopping.md).
 3. Once you have finished selecting the Kubernetes cluster, click **Add selected**.
 
-### (Optional) Step 3: Set Up Advanced Configuration
+## (Optional) Set up Advanced Configuration
 
 In this step, you can configure the following settings:
 
-#### Hide Progress Page
+### Hide progress page
 
 Toggle the button to disable the display of progress page during instances' warming up process. This option is especially useful when the service is invoked by an automation system, as it prevents misinterpretation of the progress page as the intended response from a service that is onboarded to AutoStopping. By hiding the progress page, the first response of warming up a rule after a downtime will be delayed until the intended service is up and running.
 
@@ -95,7 +95,7 @@ Toggle the button to disable the display of progress page during instances' warm
 
 Toggle the button if you wish to evaluate this feature without terminating your cloud resources. For more information, go to [Evaluate AutoStopping rules in dry-run mode](../4-create-auto-stopping-rules/autostopping-dry-run-mode.md).
 
-#### Add Dependency
+### Add Dependency
 
 Set dependencies between two or more AutoStopping Rules when you want one Rule to make one or more Rules to be active based on the traffic that it receives. For example for an application server dependant on a database server, create two AutoStopping Rules managing both the servers. Add a dependency on the Rule managing the application server to be dependant on the Rule managing the database server.
 
@@ -104,13 +104,21 @@ Set dependencies between two or more AutoStopping Rules when you want one Rule t
 3. In **DELAY IN SECS**, enter the number of seconds that rule should wait after warming up the dependent rule. For example, you have Rule 1 dependent on Rule 2 and you have set 5 seconds delay. In that case, when the request is received to warm up Rule 1, then Rule 2 (dependent rule) is warmed up first, and then there will be a delay of 5 seconds before warming up Rule 1.
 4. Once you're done with all the configurations, click **Next**.
 
-##### Fixed Schedule
+### Fixed Schedule
 
 Create fixed uptime or downtime schedules for the resources managed by this AutoStopping Rule. When a resource is configured to go up or down on a fixed schedule, it is unaffected by activity or idleness during that time period.
 
 In certain scenarios, you would not want your resources to go down or up. For example, every Friday at 5 p.m. you want your `ABC` resource to go down. You can schedule downtime for your `ABC` resource. During this window, the resource will be forced to go down regardless of the defined rule. You can choose to specify uptime for your resources in the same way.
 
-The fixed schedule takes precedence over the defined AutoStopping Rule.To create a fixed schedule for your rule, do the following:
+:::note
+The fixed schedule takes precedence over the defined AutoStopping Rule.
+:::
+
+:::note
+Harness executes scheduled rules using [Dkron](https://dkron.io/), an open-source workload automation service.
+:::
+
+To create a fixed schedule for your rule, do the following:
 
 1. In **Fixed Schedules**, click **Add Fixed Schedule**.
    
@@ -139,7 +147,7 @@ The fixed schedule takes precedence over the defined AutoStopping Rule.To create
       ![](./static/create-autostopping-rules-for-kubernetes-86.png)
 8. Click **Apply**.
 
-## Step 3: Setup Access
+## Setup Access
 
 In this step, update the resource definition YAML of the Kubernetes AutoStopping Rule that will be applied to the cluster.
 
diff --git a/docs/cloud-cost-management/5-use-ccm-cost-governance/asset-governance/cost-optimization-governance.md b/docs/cloud-cost-management/5-use-ccm-cost-governance/asset-governance/cost-optimization-governance.md
index 81c48a71ee1..45119943b0c 100644
--- a/docs/cloud-cost-management/5-use-ccm-cost-governance/asset-governance/cost-optimization-governance.md
+++ b/docs/cloud-cost-management/5-use-ccm-cost-governance/asset-governance/cost-optimization-governance.md
@@ -1,10 +1,10 @@
 ---
-title: Optimize cloud costs using the asset governance rules
+title: Cost optimization using the asset governance rules
 description: This topic describes how to optimize cloud costs using asset governance.
 # sidebar_position: 2
 ---
 
-
+# Optimize cloud costs using the asset governance rules
 To optimize cloud costs, you need to create a governance rule or combine multiple rules into a ruleset and enforce it to provide a more comprehensive, consistent, and efficient approach to cloud asset governance.
 
 
diff --git a/docs/cloud-cost-management/6-ccm-auditing.md b/docs/cloud-cost-management/6-ccm-auditing.md
index 1e2c2535959..32d92bcf7ca 100644
--- a/docs/cloud-cost-management/6-ccm-auditing.md
+++ b/docs/cloud-cost-management/6-ccm-auditing.md
@@ -1,5 +1,5 @@
 ---
-title: CCM Audit Trail
+title: Audit trail
 description: Currently, this feature is behind the feature flag AUDIT_TRAIL_WEB_INTERFACE. Contact Harness Support to enable the feature. Your Harness account Audit Trail includes events for CCM changes. CCM Even…
 # sidebar_position: 2
 helpdocs_topic_id: rhbnypj2rs
@@ -8,6 +8,7 @@ helpdocs_is_private: false
 helpdocs_is_published: true
 ---
 
+# CCM Audit trail
 Currently, this feature is behind the feature flag `AUDIT_TRAIL_WEB_INTERFACE`. Contact [Harness Support](mailto:support@harness.io) to enable the feature. Your Harness account [Audit Trail](/docs/platform/Governance/Audit-Trail/audit-trail) includes events for CCM changes.
 
 ## CCM Events in Audit Trail
diff --git a/docs/cloud-cost-management/8-monitor-cloud-cost-with-integration/_category_.json b/docs/cloud-cost-management/8-monitor-cloud-cost-with-integration/_category_.json
index 40f17ff12f0..59f1975c989 100644
--- a/docs/cloud-cost-management/8-monitor-cloud-cost-with-integration/_category_.json
+++ b/docs/cloud-cost-management/8-monitor-cloud-cost-with-integration/_category_.json
@@ -1 +1 @@
-{"label": "Third-party integrations", "collapsible": "true", "collapsed": "true", "className": "red", "link": {"type": "generated-index", "title": "Third-party integrations"}, "customProps": {"position": "30", "helpdocs_category_id": "8a7gmuvz7e"}}
\ No newline at end of file
+{"label": "Integrations", "collapsible": "true", "collapsed": "true", "className": "red", "link": {"type": "generated-index", "title": "Third-party integrations"}, "customProps": {"position": "30", "helpdocs_category_id": "8a7gmuvz7e"}}
\ No newline at end of file
diff --git a/src/components/Docs/CloudCostManagement.tsx b/src/components/Docs/CloudCostManagement.tsx
index 2f29668f747..2b51f08a237 100644
--- a/src/components/Docs/CloudCostManagement.tsx
+++ b/src/components/Docs/CloudCostManagement.tsx
@@ -37,8 +37,8 @@ export default function CCM() {
         <div className={styles.spaceBetween}>
           <div className={styles.content}>
           <p>
-          Harness CCM is a cutting-edge cloud cost management solution that empowers FinOps, infrastructure, and engineering teams with intelligent tools to optimize their cloud spending. 
-          With its advanced business intelligence (BI) capabilities, CCM provides complete cost transparency across teams.
+          Harness CCM is a cutting-edge cloud cost management solution that empowers your FinOps, infrastructure, and engineering teams with intelligent tools to optimize your cloud spend. 
+          With its advanced business intelligence (BI) capabilities, CCM provides complete cost transparency across teams in your organization.
           </p>
           </div>
         </div>

From 8928b90318ebd4a676f7d52609ef4744e995f98b Mon Sep 17 00:00:00 2001
From: charanya <charanya.jayaraman@harness.io>
Date: Tue, 25 Apr 2023 15:53:50 +0530
Subject: [PATCH 2/2] minor link fix

---
 .../8-monitor-cloud-cost-with-integration/_category_.json     | 2 +-
 src/components/Docs/data/cloudCostManagementData.ts           | 4 ++--
 2 files changed, 3 insertions(+), 3 deletions(-)

diff --git a/docs/cloud-cost-management/8-monitor-cloud-cost-with-integration/_category_.json b/docs/cloud-cost-management/8-monitor-cloud-cost-with-integration/_category_.json
index 59f1975c989..0c07950641e 100644
--- a/docs/cloud-cost-management/8-monitor-cloud-cost-with-integration/_category_.json
+++ b/docs/cloud-cost-management/8-monitor-cloud-cost-with-integration/_category_.json
@@ -1 +1 @@
-{"label": "Integrations", "collapsible": "true", "collapsed": "true", "className": "red", "link": {"type": "generated-index", "title": "Third-party integrations"}, "customProps": {"position": "30", "helpdocs_category_id": "8a7gmuvz7e"}}
\ No newline at end of file
+{"label": "Integrations", "collapsible": "true", "collapsed": "true", "className": "red", "link": {"type": "generated-index", "title": "Integrations"}, "customProps": {"position": "30", "helpdocs_category_id": "8a7gmuvz7e"}}
\ No newline at end of file
diff --git a/src/components/Docs/data/cloudCostManagementData.ts b/src/components/Docs/data/cloudCostManagementData.ts
index a06cfc11237..c5200f8bad2 100644
--- a/src/components/Docs/data/cloudCostManagementData.ts
+++ b/src/components/Docs/data/cloudCostManagementData.ts
@@ -57,11 +57,11 @@ import {
             link: "/docs/category/cost-governance",
           },
           {
-            title: "Third-party integrations",
+            title: "Integrations",
             module: MODULES.ccm,
             description:
               "Monitor your cloud costs by integrating CCM with third-party tools such as Datadog.",
-            link: "/docs/category/third-party-integrations",
+            link: "/docs/category/integrations-1",
           },
         ],
       },