diff --git a/openapi-specs/code/Policies.json b/openapi-specs/code/Policies.json
index 94e72f8cd..0b6a20ea8 100644
--- a/openapi-specs/code/Policies.json
+++ b/openapi-specs/code/Policies.json
@@ -3570,7 +3570,7 @@
   "paths": {
     "/code/api/v1/policies/definition/{queryId}": {
       "post": {
-        "description": "Prisma Cloud Application Security supports policy-as-code capabilities using YAML-based policy definition files to enable attribute and connection checks (composite checks).\nFor information on defining YAML-based policies, see the Prisma Cloud documentation about the [Code Editor](https://docs.paloaltonetworks.com/prisma/prisma-cloud/prisma-cloud-admin-code-security/scan-monitor/custom-build-policies/code-editor) and [Custom Build Policy Examples](https://docs.paloaltonetworks.com/prisma/prisma-cloud/prisma-cloud-admin-code-security/scan-monitor/custom-build-policies/custom-build-policy-examples).\nTo use the API request, add your token to the header. API supports both YAML and JSON configuration of Prisma Cloud Application Security custom policy schema.\nThis API is used to validate a user defined Prisma Cloud Application Security YAML-based custom policy schema. It returns an array of errors for not supported keys, values, and more. This call is used to verify that a custom policy which is about to be saved is properly configured.\nPolicy definitions include the following types:\noption 1 - \"attribute\" block (defined by cond_type=attribute) - checks the specific attributes of a given resource type\noption 2 - \"connection\" block (defined by cond_type=connection) - checks the existence of connection between given two resource group types\noption 3 - \"filter\" block (defined by cond_type=filter) - return given resource group types\noption 4 - \"and\"/\"or\"  - structure that supports nested \"and\"/\"or\" logic and blocks for options 1, 2 and 3\nUse the given examples as a reference for configuring the API request body.",
+        "description": "Prisma Cloud Application Security supports policy-as-code capabilities using YAML-based policy definition files to enable attribute and connection checks (composite checks).\nFor information on defining YAML-based policies, see the Prisma Cloud documentation about the [Code Editor](https://docs.prismacloud.io/en/classic/appsec-admin-guide/get-started/code-repositories-policy-management/code-editor) and [Custom Build Policy Examples](https://docs.prismacloud.io/en/classic/appsec-admin-guide/get-started/code-repositories-policy-management/custom-build-policy-examples).\nTo use the API request, add your token to the header. API supports both YAML and JSON configuration of Prisma Cloud Application Security custom policy schema.\nThis API is used to validate a user defined Prisma Cloud Application Security YAML-based custom policy schema. It returns an array of errors for not supported keys, values, and more. This call is used to verify that a custom policy which is about to be saved is properly configured.\nPolicy definitions include the following types:\noption 1 - \"attribute\" block (defined by cond_type=attribute) - checks the specific attributes of a given resource type\noption 2 - \"connection\" block (defined by cond_type=connection) - checks the existence of connection between given two resource group types\noption 3 - \"filter\" block (defined by cond_type=filter) - return given resource group types\noption 4 - \"and\"/\"or\"  - structure that supports nested \"and\"/\"or\" logic and blocks for options 1, 2 and 3\nUse the given examples as a reference for configuring the API request body.",
         "operationId": "validateCustomPolicy",
         "parameters": [
           {
@@ -3646,7 +3646,7 @@
     "/code/api/v1/policies": {
       "post": {
         "deprecated": true,
-        "description": "Prisma Cloud Application Security supports policy-as-code capabilities using YAML-based policy definition files to enable attribute and connection checks (composite checks).\nFor information on defining YAML-based policies, see the Prisma Cloud documentation about the [Code Editor](https://docs.paloaltonetworks.com/prisma/prisma-cloud/prisma-cloud-admin-code-security/scan-monitor/custom-build-policies/code-editor) and [Custom Build Policy Examples](https://docs.paloaltonetworks.com/prisma/prisma-cloud/prisma-cloud-admin-code-security/scan-monitor/custom-build-policies/custom-build-policy-examples).\nTo use the API request, add your token to the header. API supports both YAML and JSON configuration of Prisma Cloud Application Security custom policy schema.\nThis API creates a new Prisma Cloud Application Security custom policy.\nThe input will be a code-based policy definition file. The output will be a new policy id. In case of invalid code - output will include definition errors.\nUse the given examples as a reference for configuring the API request body for saving new policies.\n:::info\nUse the CSPM endpoint [Add Policy](/prisma-cloud/api/cspm/add-policy/) in place of this endpoint.\n:::",
+        "description": "Prisma Cloud Application Security supports policy-as-code capabilities using YAML-based policy definition files to enable attribute and connection checks (composite checks).\nFor information on defining YAML-based policies, see the Prisma Cloud documentation about the [Code Editor](https://docs.prismacloud.io/en/classic/appsec-admin-guide/get-started/code-repositories-policy-management/code-editor) and [Custom Build Policy Examples](https://docs.prismacloud.io/en/classic/appsec-admin-guide/get-started/code-repositories-policy-management/custom-build-policy-examples).\nTo use the API request, add your token to the header. API supports both YAML and JSON configuration of Prisma Cloud Application Security custom policy schema.\nThis API creates a new Prisma Cloud Application Security custom policy.\nThe input will be a code-based policy definition file. The output will be a new policy id. In case of invalid code - output will include definition errors.\nUse the given examples as a reference for configuring the API request body for saving new policies.\n:::info\nUse the CSPM endpoint [Add Policy](/prisma-cloud/api/cspm/add-policy/) in place of this endpoint.\n:::",
         "operationId": "savePolicy",
         "parameters": [],
         "requestBody": {
@@ -3723,7 +3723,7 @@
     "/code/api/v1/policies/table/data": {
       "get": {
         "deprecated": true,
-        "description": "Prisma Cloud Application Security supports policy-as-code capabilities using YAML-based policy definition files to enable attribute and connection checks (composite checks).\nFor information on defining YAML-based policies, see the Prisma Cloud documentation about the [Code Editor](https://docs.paloaltonetworks.com/prisma/prisma-cloud/prisma-cloud-admin-code-security/scan-monitor/custom-build-policies/code-editor) and [Custom Build Policy Examples](https://docs.paloaltonetworks.com/prisma/prisma-cloud/prisma-cloud-admin-code-security/scan-monitor/custom-build-policies/custom-build-policy-examples).\nTo use the API request, add your token to the header. API supports both YAML and JSON configuration of Prisma Cloud Application Security custom policy schema.\nThis API gets all Prisma Cloud Application Security custom policies with count of passed, failed, suppressed resources, scan status (compliant/non-compliant), and attached benchmarks of specific policies.\nUse the given examples as a reference for the expected output of this API request.\n:::info\nUse the CSPM endpoint [List Policies V2](/prisma-cloud/api/cspm/get-policies-v-2/) in place of this endpoint.\n:::",
+        "description": "Prisma Cloud Application Security supports policy-as-code capabilities using YAML-based policy definition files to enable attribute and connection checks (composite checks).\nFor information on defining YAML-based policies, see the Prisma Cloud documentation about the [Code Editor](https://docs.prismacloud.io/en/classic/appsec-admin-guide/get-started/code-repositories-policy-management/code-editor) and [Custom Build Policy Examples](https://docs.prismacloud.io/en/classic/appsec-admin-guide/get-started/code-repositories-policy-management/custom-build-policy-examples).\nTo use the API request, add your token to the header. API supports both YAML and JSON configuration of Prisma Cloud Application Security custom policy schema.\nThis API gets all Prisma Cloud Application Security custom policies with count of passed, failed, suppressed resources, scan status (compliant/non-compliant), and attached benchmarks of specific policies.\nUse the given examples as a reference for the expected output of this API request.\n:::info\nUse the CSPM endpoint [List Policies V2](/prisma-cloud/api/cspm/get-policies-v-2/) in place of this endpoint.\n:::",
         "operationId": "getCustomPoliciesTable",
         "parameters": [],
         "responses": {
@@ -3907,7 +3907,7 @@
     "/code/api/v1/policies/{policyId}": {
       "put": {
         "deprecated": true,
-        "description": "Prisma Cloud Application Security supports policy-as-code capabilities using YAML-based policy definition files to enable attribute and connection checks (composite checks).\nFor information on defining YAML-based policies, see the Prisma Cloud documentation about the [Code Editor](https://docs.paloaltonetworks.com/prisma/prisma-cloud/prisma-cloud-admin-code-security/scan-monitor/custom-build-policies/code-editor) and [Custom Build Policy Examples](https://docs.paloaltonetworks.com/prisma/prisma-cloud/prisma-cloud-admin-code-security/scan-monitor/custom-build-policies/custom-build-policy-examples).\nTo use the API request, add your token to the header. API supports both YAML and JSON configuration of Prisma Cloud Application Security custom policy schema.\nThis API request updates an existing Prisma Cloud Application Security custom policy. The API contains the fields to be edited. Any field not included in the request will remain unchanged.\nYou can use this API request to add fields that were previously not configured. The output will be the id of updated policy.\nUse the given examples as a reference for configuring the API request body.\n:::info\nUse the CSPM endpoint [Update Policy](/prisma-cloud/api/cspm/update-policy/) in place of this endpoint.\n:::",
+        "description": "Prisma Cloud Application Security supports policy-as-code capabilities using YAML-based policy definition files to enable attribute and connection checks (composite checks).\nFor information on defining YAML-based policies, see the Prisma Cloud documentation about the [Code Editor](https://docs.prismacloud.io/en/classic/appsec-admin-guide/get-started/code-repositories-policy-management/code-editor) and [Custom Build Policy Examples](https://docs.prismacloud.io/en/classic/appsec-admin-guide/get-started/code-repositories-policy-management/custom-build-policy-examples).\nTo use the API request, add your token to the header. API supports both YAML and JSON configuration of Prisma Cloud Application Security custom policy schema.\nThis API request updates an existing Prisma Cloud Application Security custom policy. The API contains the fields to be edited. Any field not included in the request will remain unchanged.\nYou can use this API request to add fields that were previously not configured. The output will be the id of updated policy.\nUse the given examples as a reference for configuring the API request body.\n:::info\nUse the CSPM endpoint [Update Policy](/prisma-cloud/api/cspm/update-policy/) in place of this endpoint.\n:::",
         "operationId": "updatePolicy",
         "parameters": [
           {
@@ -3989,7 +3989,7 @@
       },
       "delete": {
         "deprecated": true,
-        "description": "Prisma Cloud Application Security supports policy-as-code capabilities using YAML-based policy definition files to enable attribute and connection checks (composite checks).\nFor information on defining YAML-based policies, see the Prisma Cloud documentation about the [Code Editor](https://docs.paloaltonetworks.com/prisma/prisma-cloud/prisma-cloud-admin-code-security/scan-monitor/custom-build-policies/code-editor) and [Custom Build Policy Examples](https://docs.paloaltonetworks.com/prisma/prisma-cloud/prisma-cloud-admin-code-security/scan-monitor/custom-build-policies/custom-build-policy-examples).\nTo use the API request, add your token to the header. API supports both YAML and JSON configuration of Prisma Cloud Application Security custom policy schema.\nThis API deletes an existing Prisma Cloud Application Security custom policy. The output will be the id of deleted policy.\n:::info\nUse the CSPM endpoint [Delete Policy](/prisma-cloud/api/cspm/delete-policy/) in place of this endpoint.\n:::",
+        "description": "Prisma Cloud Application Security supports policy-as-code capabilities using YAML-based policy definition files to enable attribute and connection checks (composite checks).\nFor information on defining YAML-based policies, see the Prisma Cloud documentation about the [Code Editor](https://docs.prismacloud.io/en/classic/appsec-admin-guide/get-started/code-repositories-policy-management/code-editor) and [Custom Build Policy Examples](https://docs.prismacloud.io/en/classic/appsec-admin-guide/get-started/code-repositories-policy-management/custom-build-policy-examples).\nTo use the API request, add your token to the header. API supports both YAML and JSON configuration of Prisma Cloud Application Security custom policy schema.\nThis API deletes an existing Prisma Cloud Application Security custom policy. The output will be the id of deleted policy.\n:::info\nUse the CSPM endpoint [Delete Policy](/prisma-cloud/api/cspm/delete-policy/) in place of this endpoint.\n:::",
         "operationId": "removePolicy",
         "parameters": [
           {
@@ -4061,7 +4061,7 @@
     },
     "/code/api/v1/policies/preview": {
       "post": {
-        "description": "Prisma Cloud Application Security supports policy-as-code capabilities using YAML-based policy definition files to enable attribute and connection checks (composite checks).\nFor information on defining YAML-based policies, see the Prisma Cloud documentation about the [Code Editor](https://docs.paloaltonetworks.com/prisma/prisma-cloud/prisma-cloud-admin-code-security/scan-monitor/custom-build-policies/code-editor) and [Custom Build Policy Examples](https://docs.paloaltonetworks.com/prisma/prisma-cloud/prisma-cloud-admin-code-security/scan-monitor/custom-build-policies/custom-build-policy-examples).\nTo use the API request, add your token to the header. API supports both YAML and JSON configuration of Prisma Cloud Application Security custom policy schema.\nThis API gets up to 30 results (by default) of non-compliant resources for a specific policy. The input is the policy to test and the output is an array of resources results.\nUse the first example to configure the API to test a policy, and use the second example as a reference of the expected output.",
+        "description": "Prisma Cloud Application Security supports policy-as-code capabilities using YAML-based policy definition files to enable attribute and connection checks (composite checks).\nFor information on defining YAML-based policies, see the Prisma Cloud documentation about the [Code Editor](https://docs.prismacloud.io/en/classic/appsec-admin-guide/get-started/code-repositories-policy-management/code-editor) and [Custom Build Policy Examples](https://docs.prismacloud.io/en/classic/appsec-admin-guide/get-started/code-repositories-policy-management/custom-build-policy-examples).\nTo use the API request, add your token to the header. API supports both YAML and JSON configuration of Prisma Cloud Application Security custom policy schema.\nThis API gets up to 30 results (by default) of non-compliant resources for a specific policy. The input is the policy to test and the output is an array of resources results.\nUse the first example to configure the API to test a policy, and use the second example as a reference of the expected output.",
         "operationId": "policyPreview",
         "parameters": [],
         "requestBody": {
@@ -4189,7 +4189,7 @@
     "/code/api/v1/policies/clone/{policyId}": {
       "post": {
         "deprecated": true,
-        "description": "Prisma Cloud Application Security supports policy-as-code capabilities using YAML-based policy definition files to enable attribute and connection checks (composite checks).\nFor information on defining YAML-based policies, see the Prisma Cloud documentation about the [Code Editor](https://docs.paloaltonetworks.com/prisma/prisma-cloud/prisma-cloud-admin-code-security/scan-monitor/custom-build-policies/code-editor) and [Custom Build Policy Examples](https://docs.paloaltonetworks.com/prisma/prisma-cloud/prisma-cloud-admin-code-security/scan-monitor/custom-build-policies/custom-build-policy-examples).\nTo use the API request, add your token to the header. API supports both YAML and JSON configuration of Prisma Cloud Application Security custom policy schema.\n\nThis API clones an existing Policy.\nGiven a valid Policy Id, this API will create a new Policy based on the different fields from the original Policy, and will override any field given to it as input.\n:::info\nUse the CSPM endpoint [Update Policy](/prisma-cloud/api/cspm/update-policy/) in place of this endpoint.\n:::\n        ",
+        "description": "Prisma Cloud Application Security supports policy-as-code capabilities using YAML-based policy definition files to enable attribute and connection checks (composite checks).\nFor information on defining YAML-based policies, see the Prisma Cloud documentation about the [Code Editor](https://docs.prismacloud.io/en/classic/appsec-admin-guide/get-started/code-repositories-policy-management/code-editor) and [Custom Build Policy Examples](https://docs.prismacloud.io/en/classic/appsec-admin-guide/get-started/code-repositories-policy-management/custom-build-policy-examples).\nTo use the API request, add your token to the header. API supports both YAML and JSON configuration of Prisma Cloud Application Security custom policy schema.\n\nThis API clones an existing Policy.\nGiven a valid Policy Id, this API will create a new Policy based on the different fields from the original Policy, and will override any field given to it as input.\n:::info\nUse the CSPM endpoint [Update Policy](/prisma-cloud/api/cspm/update-policy/) in place of this endpoint.\n:::\n        ",
         "operationId": "clonePolicy",
         "parameters": [
           {
diff --git a/products/compute/api/22-12/stable-endpoints.md b/products/compute/api/22-12/stable-endpoints.md
index df4a686dc..dc7062141 100644
--- a/products/compute/api/22-12/stable-endpoints.md
+++ b/products/compute/api/22-12/stable-endpoints.md
@@ -38,7 +38,7 @@ Where:
 As a best practice, update your scripts to use the version-specific API endpoints to ensure that your implementation is fully supported.
 For the version-specific APIs, you will have access to the API Reference and Release Notes documentation for changes or updates that may impact you.
 
-When using the version-specific endpoints, you will need to update your automation scripts approximately once-a- year to stay in sync with the product [support lifecycle](https://docs.paloaltonetworks.com/prisma/prisma-cloud/prisma-cloud-admin-compute/upgrade/support_lifecycle.html).
+When using the version-specific endpoints, you will need to update your automation scripts approximately once a year to stay in sync with the product [Support lifecycle for connected components](https://docs.prismacloud.io/en/classic/compute-admin-guide/upgrade/support-lifecycle). If you are upgraded to Darwin, see [Support Lifecycle for Connected Components](https://docs.prismacloud.io/en/enterprise-edition/content-collections/runtime-security/upgrade/support-lifecycle).
 
 **Note**: If you have a mixed environment of different version Defenders, then use the version of the API that matches the earliest version.
 
diff --git a/products/compute/api/30-00/stable-endpoints.md b/products/compute/api/30-00/stable-endpoints.md
index 984f37c47..e27eb2ec1 100644
--- a/products/compute/api/30-00/stable-endpoints.md
+++ b/products/compute/api/30-00/stable-endpoints.md
@@ -41,7 +41,7 @@ Where:
 As a best practice, update your scripts to use the version-specific API endpoints to ensure that your implementation is fully supported.
 For the version-specific APIs, you will have access to the API Reference and Release Notes documentation for changes or updates that may impact you.
 
-When using the version-specific endpoints, you will need to update your automation scripts approximately once-a- year to stay in sync with the product [support lifecycle](https://docs.paloaltonetworks.com/prisma/prisma-cloud/prisma-cloud-admin-compute/upgrade/support_lifecycle.html).
+When using the version-specific endpoints, you will need to update your automation scripts approximately once a year to stay in sync with the product [Support lifecycle for connected components](https://docs.prismacloud.io/en/classic/compute-admin-guide/upgrade/support-lifecycle). If you are upgraded to Darwin, see [Support Lifecycle for Connected Components](https://docs.prismacloud.io/en/enterprise-edition/content-collections/runtime-security/upgrade/support-lifecycle).
 
 Starting with version 30.xx, each maintenance release (like 30.01, 30.02, and so on) may contain new features and improvements. As a result, the URLs for the APIs will be updated to reflect the version. 
 
diff --git a/products/compute/api/30-01/stable-endpoints.md b/products/compute/api/30-01/stable-endpoints.md
index f508b4d63..e3b7d0ac4 100644
--- a/products/compute/api/30-01/stable-endpoints.md
+++ b/products/compute/api/30-01/stable-endpoints.md
@@ -41,7 +41,7 @@ Where:
 As a best practice, update your scripts to use the version-specific API endpoints to ensure that your implementation is fully supported.
 For the version-specific APIs, you will have access to the API Reference and Release Notes documentation for changes or updates that may impact you.
 
-When using the version-specific endpoints, you will need to update your automation scripts approximately once-a- year to stay in sync with the product [support lifecycle](https://docs.paloaltonetworks.com/prisma/prisma-cloud/prisma-cloud-admin-compute/upgrade/support_lifecycle.html).
+When using the version-specific endpoints, you will need to update your automation scripts approximately once a year to stay in sync with the product [Support lifecycle for connected components](https://docs.prismacloud.io/en/classic/compute-admin-guide/upgrade/support-lifecycle). If you are upgraded to Darwin, see [Support Lifecycle for Connected Components](https://docs.prismacloud.io/en/enterprise-edition/content-collections/runtime-security/upgrade/support-lifecycle).
 
 Starting with version 30.xx, each maintenance release (like 30.01, 30.02, and so on) may contain new features and improvements. As a result, the URLs for the APIs will be updated to reflect the version. 
 
diff --git a/products/compute/api/30-02/stable-endpoints.md b/products/compute/api/30-02/stable-endpoints.md
index c400e9501..7c3a25352 100644
--- a/products/compute/api/30-02/stable-endpoints.md
+++ b/products/compute/api/30-02/stable-endpoints.md
@@ -41,7 +41,7 @@ Where:
 As a best practice, update your scripts to use the version-specific API endpoints to ensure that your implementation is fully supported.
 For the version-specific APIs, you will have access to the API Reference and Release Notes documentation for changes or updates that may impact you.
 
-When using the version-specific endpoints, you will need to update your automation scripts approximately once-a- year to stay in sync with the product [support lifecycle](https://docs.paloaltonetworks.com/prisma/prisma-cloud/prisma-cloud-admin-compute/upgrade/support_lifecycle.html).
+When using the version-specific endpoints, you will need to update your automation scripts approximately once a year to stay in sync with the product [Support lifecycle for connected components](https://docs.prismacloud.io/en/classic/compute-admin-guide/upgrade/support-lifecycle). If you are upgraded to Darwin, see [Support Lifecycle for Connected Components](https://docs.prismacloud.io/en/enterprise-edition/content-collections/runtime-security/upgrade/support-lifecycle).
 
 Starting with version 30.xx, each maintenance release (like 30.01, 30.02, and so on) may contain new features and improvements. As a result, the URLs for the APIs will be updated to reflect the version. 
 
diff --git a/products/compute/api/30-03/stable-endpoints.md b/products/compute/api/30-03/stable-endpoints.md
index a334520e6..8c492cc36 100644
--- a/products/compute/api/30-03/stable-endpoints.md
+++ b/products/compute/api/30-03/stable-endpoints.md
@@ -39,7 +39,7 @@ Where:
 As a best practice, update your scripts to use the version-specific API endpoints to ensure that your implementation is fully supported.
 For the version-specific APIs, you will have access to the API Reference and Release Notes documentation for changes or updates that may impact you.
 
-When using the version-specific endpoints, you will need to update your automation scripts approximately once-a- year to stay in sync with the product [support lifecycle](https://docs.paloaltonetworks.com/prisma/prisma-cloud/prisma-cloud-admin-compute/upgrade/support_lifecycle.html).
+When using the version-specific endpoints, you will need to update your automation scripts approximately once a year to stay in sync with the product [Support lifecycle for connected components](https://docs.prismacloud.io/en/classic/compute-admin-guide/upgrade/support-lifecycle). If you are upgraded to Darwin, see [Support Lifecycle for Connected Components](https://docs.prismacloud.io/en/enterprise-edition/content-collections/runtime-security/upgrade/support-lifecycle).
 
 Starting with version 30.xx, each maintenance release (like 30.01, 30.02, and so on) may contain new features and improvements. As a result, the URLs for the APIs will be updated to reflect the version. 
 
diff --git a/products/compute/api/31-00/stable-endpoints.md b/products/compute/api/31-00/stable-endpoints.md
index 0f8eabb07..3098882ba 100644
--- a/products/compute/api/31-00/stable-endpoints.md
+++ b/products/compute/api/31-00/stable-endpoints.md
@@ -37,7 +37,7 @@ Where:
 As a best practice, update your scripts to use the version-specific API endpoints to ensure that your implementation is fully supported.
 For the version-specific APIs, you will have access to the API Reference and Release Notes documentation for changes or updates that may impact you.
 
-When using the version-specific endpoints, you will need to update your automation scripts approximately once-a- year to stay in sync with the product [support lifecycle](https://docs.paloaltonetworks.com/prisma/prisma-cloud/prisma-cloud-admin-compute/upgrade/support_lifecycle.html).
+When using the version-specific endpoints, you will need to update your automation scripts approximately once a year to stay in sync with the product [Support lifecycle for connected components](https://docs.prismacloud.io/en/classic/compute-admin-guide/upgrade/support-lifecycle). If you are upgraded to Darwin, see [Support Lifecycle for Connected Components](https://docs.prismacloud.io/en/enterprise-edition/content-collections/runtime-security/upgrade/support-lifecycle).
 
 Starting with version 30.xx, each maintenance release (like 30.01, 30.02, and so on) may contain new features and improvements. As a result, the URLs for the APIs will be updated to reflect the version. 
 
diff --git a/products/compute/api/stable-endpoints.md b/products/compute/api/stable-endpoints.md
index f48c4e00a..86cc719cf 100644
--- a/products/compute/api/stable-endpoints.md
+++ b/products/compute/api/stable-endpoints.md
@@ -40,7 +40,7 @@ Where:
 As a best practice, update your scripts to use the version-specific API endpoints to ensure that your implementation is fully supported.
 For the version-specific APIs, you will have access to the API Reference and Release Notes documentation for changes or updates that may impact you.
 
-When using the version-specific endpoints, you will need to update your automation scripts approximately once-a- year to stay in sync with the product [support lifecycle](https://docs.paloaltonetworks.com/prisma/prisma-cloud/prisma-cloud-admin-compute/upgrade/support_lifecycle.html).
+When using the version-specific endpoints, you will need to update your automation scripts approximately once a year to stay in sync with the product [Support lifecycle for connected components](https://docs.prismacloud.io/en/classic/compute-admin-guide/upgrade/support-lifecycle). If you are upgraded to Darwin, see [Support Lifecycle for Connected Components](https://docs.prismacloud.io/en/enterprise-edition/content-collections/runtime-security/upgrade/support-lifecycle).
 
 Starting with version 30.xx, each maintenance release (like 30.01, 30.02, and so on) may contain new features and improvements. As a result, the URLs for the APIs will be updated to reflect the version. 
 
diff --git a/products/prisma-cloud/api/code/basic-request.md b/products/prisma-cloud/api/code/basic-request.md
index 085ae3680..e01c9050c 100644
--- a/products/prisma-cloud/api/code/basic-request.md
+++ b/products/prisma-cloud/api/code/basic-request.md
@@ -12,7 +12,8 @@ keywords:
 
 Use the following guidelines to ensure that your Application Security API requests to Prisma Cloud are successful.
 
-See [Prisma Cloud Application Security](https://docs.paloaltonetworks.com/prisma/prisma-cloud/prisma-cloud-admin-code-security.html) for more information and for directions to enable Application Security on Prisma Cloud.
+ For more information and for directions to enable Application Security on Prisma Cloud, see [Prisma Cloud Administrator’s Guide—Application Security](https://docs.prismacloud.io/en/classic/appsec-admin-guide). If you are upgraded to Darwin, see [Prisma Cloud Application Security](https://docs.prismacloud.io/en/enterprise-edition/content-collections/application-security/application-security).
+ 
 
 ## Prerequisites for a Application Security Request
 
@@ -20,16 +21,13 @@ To make a Application Security API request, you must have the right privileges a
 
 ### Application Security Access
 
-To have the right privileges to make a Application Security API request, you must set up:
-
-- [Administrator access](https://docs.paloaltonetworks.com/prisma/prisma-cloud/prisma-cloud-admin-code-security/get-started/setup-administrator-access.html)
-- [Developer access](https://docs.paloaltonetworks.com/prisma/prisma-cloud/prisma-cloud-admin-code-security/get-started/setup-developer-access.html)
+To have the right privileges to make a Application Security API request, you must set up Administrator and Developer access. For more information, see - [Manage Roles and Permissions](https://docs.prismacloud.io/en/classic/cspm-admin-guide/manage-prisma-cloud-administrators/prisma-cloud-administrator-roles). If you are upgraded to Darwin, see [Administrator access](https://docs.prismacloud.io/en/classic/appsec-admin-guide/get-started/manage-roles-permissions).
 
 ### Application Security API Authorization
 
 To have the right authorization for a Application Security API request, follow the high-level steps below:
 
-1. [Obtain an access key](https://docs.paloaltonetworks.com/prisma/prisma-cloud/prisma-cloud-admin/manage-prisma-cloud-administrators/create-access-keys.html) from your Prisma Cloud system administrator.
+1. [Create and Manage Access Keys](https://docs.prismacloud.io/en/classic/cspm-admin-guide/manage-prisma-cloud-administrators/create-access-keys). If you are upgraded to Darwin, see [Create and Manage Access Keys](https://docs.prismacloud.io/en/enterprise-edition/content-collections/administration/create-access-keys).
 2. Make a CSPM API request to [log in](/prisma-cloud/api/cspm/app-login) . A successful request returns a JSON Web Token (JWT).
 
 All the Application Security API requests use this JWT in the API request [header](/prisma-cloud/api/code/api-headers) for authorization. Note that for security, a JWT is valid for only ten minutes. If your session must be active beyond that limit, you can [extend a session](/prisma-cloud/api/cspm/extend-session/).
diff --git a/products/prisma-cloud/api/code/code.md b/products/prisma-cloud/api/code/code.md
index a0cccc27e..2127e540b 100644
--- a/products/prisma-cloud/api/code/code.md
+++ b/products/prisma-cloud/api/code/code.md
@@ -17,6 +17,6 @@ enables you to:
 
 Use the [CSPM Policy API](/prisma-cloud/api/cspm/policy) to create and manage Application Security build policies.
 
-See [Prisma Cloud Application Security](https://docs.paloaltonetworks.com/prisma/prisma-cloud/prisma-cloud-admin-code-security.html) for more information.
+For more information, see [Prisma Cloud Administrator’s Guide—Application Security](https://docs.prismacloud.io/en/classic/appsec-admin-guide). If you are upgraded to Darwin, see [Prisma Cloud Application Security](https://docs.prismacloud.io/en/enterprise-edition/content-collections/application-security/application-security).
 
 Check the status notifications at <https://status.paloaltonetworks.com/> for the Prisma Cloud release schedule to know when new functionality is available.
diff --git a/products/prisma-cloud/api/cwpp/stable-endpoints.md b/products/prisma-cloud/api/cwpp/stable-endpoints.md
index 4e6dc08dd..65a6a6950 100644
--- a/products/prisma-cloud/api/cwpp/stable-endpoints.md
+++ b/products/prisma-cloud/api/cwpp/stable-endpoints.md
@@ -32,7 +32,7 @@ Where:
 As a best practice, update your scripts to use the version-specific API endpoints to ensure that your implementation is fully supported.
 For the version-specific APIs, you will have access to the API Reference and Release Notes documentation for changes or updates that may impact you.
 
-When using the version-specific endpoints, you will need to update your automation scripts approximately once-a- year to stay in sync with the product [support lifecycle](https://docs.paloaltonetworks.com/prisma/prisma-cloud/prisma-cloud-admin-compute/upgrade/support_lifecycle.html).
+When using the version-specific endpoints, you will need to update your automation scripts approximately once a year to stay in sync with the product [Support lifecycle for connected components](https://docs.prismacloud.io/en/classic/compute-admin-guide/upgrade/support-lifecycle). If you are upgraded to Darwin, see [Support Lifecycle for Connected Components](https://docs.prismacloud.io/en/enterprise-edition/content-collections/runtime-security/upgrade/support-lifecycle).
 
 **Note**: If you have a mixed environment of different version Defenders, then use the version of the API that matches the earliest version.
 
diff --git a/products/prisma-cloud/docs/cwpp/view_registry_scan.md b/products/prisma-cloud/docs/cwpp/view_registry_scan.md
index 0ebd5a4ef..181e1b5de 100644
--- a/products/prisma-cloud/docs/cwpp/view_registry_scan.md
+++ b/products/prisma-cloud/docs/cwpp/view_registry_scan.md
@@ -31,7 +31,7 @@ After you configure, Prisma Cloud automatically scans images for vulnerabilities
 3. Discovers the images using tags within each configured repository.
 4. Scans the discovered images.
 
-This guide shows how to get vulnerability report for container images stored in different registries. For more information about registry scan, see [Configure Registry Scan](https://docs.paloaltonetworks.com/prisma/prisma-cloud/prisma-cloud-admin-compute/vulnerability_management/registry_scanning/configure_registry_scanning).
+This guide shows how to get vulnerability report for container images stored in different registries. For more information about registry scan, see [Configure Registry Scan](https://docs.prismacloud.io/en/classic/compute-admin-guide/vulnerability-management/registry-scanning/configure-registry-scanning). If you are upgraded to Darwin, see [Configure Registry Scan](https://docs.prismacloud.io/en/enterprise-edition/content-collections/runtime-security/vulnerability-management/registry-scanning/configure-registry-scanning).
 
 
 ***Prerequisite***:
diff --git a/products/prisma-cloud/docs/home.md b/products/prisma-cloud/docs/home.md
index d20a09cff..824702078 100644
--- a/products/prisma-cloud/docs/home.md
+++ b/products/prisma-cloud/docs/home.md
@@ -10,7 +10,7 @@ keywords:
   - Cloud Workload Protection
 ---
 
-Prisma™ Cloud is a cloud-native security platform that provides comprehensive visibility, threat detection/prevention, compliance assurance, and data protection across an organization’s hybrid, multi-cloud infrastructure. It is available as either an [Enterprise or Compute Edition](https://docs.paloaltonetworks.com/prisma/prisma-cloud/prisma-cloud-admin-compute/welcome/pcee_vs_pcce.html), offering a convenient REST API for all three capabilities.
+Prisma™ Cloud is a cloud-native security platform that provides comprehensive visibility, threat detection/prevention, compliance assurance, and data protection across an organization’s hybrid, multi-cloud infrastructure. It is available as either an Enterprise or Compute Edition, offering a convenient REST API for all three capabilities. For more information, see [Prisma Cloud Enterprise Edition vs Compute Edition](https://docs.prismacloud.io/en/classic/compute-admin-guide/welcome/pcee-vs-pcce). If you are upgraded to Darwin, see [Prisma Cloud Enterprise Edition vs Compute Edition](https://docs.prismacloud.io/en/enterprise-edition/content-collections/runtime-security/pcee-vs-pcce). 
 
 - [Cloud Security Posture Management](/prisma-cloud/api/cspm) enables you to configure custom integrations for your cloud security needs. For example, you can use it to automate sending alert notifications to your in-house tool or to extend the DevOps security capabilities for a tool that does not have an extension or plugin for Prisma Cloud. Most actions supported on the Prisma Cloud web interface are available with the REST API.
 
@@ -19,7 +19,7 @@ Prisma™ Cloud is a cloud-native security platform that provides comprehensive
 - [Cloud Application Security](/prisma-cloud/api/code/) enables you to programmatically check your Infrastructure-as-Code resources against Prisma Cloud out-of-the-box and custom security policies, ensuring security throughout the build lifecycle.
 
 For information about Prisma Cloud beyond its APIs, such as administration and policy management,
-see the [Prisma Cloud administration documentation](https://docs.paloaltonetworks.com/prisma/prisma-cloud.html).
+see the [Prisma Cloud documentation](https://docs.prismacloud.io/en).
 
 :::info
 
diff --git a/products/prisma-cloud/docs/twistcli_gs.md b/products/prisma-cloud/docs/twistcli_gs.md
index d4ed3381d..e4d28f238 100644
--- a/products/prisma-cloud/docs/twistcli_gs.md
+++ b/products/prisma-cloud/docs/twistcli_gs.md
@@ -183,7 +183,7 @@ Each package has the following name-value pairs:
 
 ## Running scans from inside the container
 
-By default, `twistcli` is run from outside the container image. In some cases, you might need to copy `twistcli` to the container’s file system, and then run the scanner from inside the container. One reason you might want to run the scanner this way is when your build platform doesn’t give you access to the Docker socket. OpenShift Container Platform and CodeFresh are examples of such platforms. For step-by-step guidance on configuring the OpenShift build process, <a href="https://docs.paloaltonetworks.com/prisma/prisma-cloud/prisma-cloud-admin-compute/howto/openshift_build_twistcli_scanning.html" target="_blank">see here.</a>
+By default, `twistcli` is run from outside the container image. In some cases, you might need to copy `twistcli` to the container’s file system, and then run the scanner from inside the container. One reason you might want to run the scanner this way is when your build platform doesn’t give you access to the Docker socket. OpenShift Container Platform and CodeFresh are examples of such platforms. For step-by-step guidance on configuring the OpenShift build process, see [Scan Images Built with Jenkins in an OpenShift Environment](https://docs.prismacloud.io/en/compute-edition/31/admin-guide/tools/twistcli-scan-images). If you are upgraded to Darwin, see [Scan Images Built with Jenkins in an OpenShift Environment](https://docs.prismacloud.io/en/enterprise-edition/content-collections/runtime-security/tools/twistcli-scan-images).
 
 There are some shortcomings with this scanning from inside a container, so you should only use this approach when no other approach is viable. The shortcomings are:
 
@@ -440,7 +440,7 @@ $ twistcli hosts scan \
 
 Where the `--skip-docker` option skips all Docker compliance checks such as the Docker daemon configuration and the `--include-3rd-party` option scans application-specific files such as Java JARs.
 
-> A detailed procedure for setting up twistcli scanning during the OpenShift build process can be found <a href="https://docs.paloaltonetworks.com/prisma/prisma-cloud/prisma-cloud-admin-compute/howto/openshift_build_twistcli_scanning.html" target="_blank">here</a>.
+> For the detailed procedure for setting up twistcli scanning during the OpenShift build process, see [Scan Images Built with Jenkins in an OpenShift Environment](https://docs.prismacloud.io/en/compute-edition/31/admin-guide/tools/twistcli-scan-images). If you are upgraded to Darwin, see [Scan Images Built with Jenkins in an OpenShift Environment](https://docs.prismacloud.io/en/enterprise-edition/content-collections/runtime-security/tools/twistcli-scan-images).
 
 ## Scan images when the Docker socket isn’t in the default location
 
diff --git a/products/prisma-cloud/sidebars.js b/products/prisma-cloud/sidebars.js
index d00ed5415..bab486104 100644
--- a/products/prisma-cloud/sidebars.js
+++ b/products/prisma-cloud/sidebars.js
@@ -67,18 +67,24 @@ module.exports = {
       items: [
         {
           type: "link",
-          label: "Administrator's Guide",
-          href: "https://docs.paloaltonetworks.com/prisma/prisma-cloud/prisma-cloud-admin.html",
+          label: "Administrator's Guide (Enterprise Edition - Classic)",
+          href: "https://docs.prismacloud.io/en/classic/cspm-admin-guide",
         },
+        {
+          type: "link",
+          label: "Content Collections (Enterprise Edition)",
+          href: "https://docs.prismacloud.io/en/enterprise-edition/content-collections",
+        },
+
         {
           type: "link",
           label: "Release Information",
-          href: "https://docs.paloaltonetworks.com/content/techdocs/en_US/prisma/prisma-cloud/prisma-cloud-release-notes/prisma-cloud-release-information.html",
+          href: "https://docs.prismacloud.io/en/enterprise-edition/rn",
         },
         {
           type: "link",
           label: "Resource Query Language (RQL)",
-          href: "https://docs.paloaltonetworks.com/prisma/prisma-cloud/prisma-cloud-rql-reference/rql-reference.html",
+          href: "https://docs.prismacloud.io/en/classic/rql-reference",
         },
         "prisma-cloud/docs/twistcli_gs",
         {
@@ -108,12 +114,12 @@ module.exports = {
             {
               type: "link",
               label: "Administrator's Guide",
-              href: "https://docs.paloaltonetworks.com/content/techdocs/en_US/prisma/prisma-cloud/31/prisma-cloud-compute-edition-admin.html",
+              href: "https://docs.prismacloud.io/en/compute-edition/31/admin-guide",
             },
             {
               type: "link",
               label: "Release Notes",
-              href: "https://docs.paloaltonetworks.com/prisma/prisma-cloud/31/prisma-cloud-compute-edition-release-notes/release-information",
+              href: "https://docs.prismacloud.io/en/compute-edition/31/rn/release-information/release-notes-31-02-update2",
             },
           ],
         },
@@ -124,12 +130,12 @@ module.exports = {
             {
               type: "link",
               label: "Administrator's Guide",
-              href: "https://docs.paloaltonetworks.com/content/techdocs/en_US/prisma/prisma-cloud/30/prisma-cloud-compute-edition-admin.html",
+              href: "https://docs.prismacloud.io/en/compute-edition/30/admin-guide",
             },
             {
               type: "link",
               label: "Release Notes",
-              href: "https://docs.paloaltonetworks.com/prisma/prisma-cloud/30/prisma-cloud-compute-edition-release-notes/release-information",
+              href: "https://docs.prismacloud.io/en/compute-edition/30/rn/release-information/release-notes-30-03-update3",
             },
           ],
         },
@@ -140,28 +146,12 @@ module.exports = {
             {
               type: "link",
               label: "Administrator's Guide",
-              href: "https://docs.paloaltonetworks.com/content/techdocs/en_US/prisma/prisma-cloud/22-12/prisma-cloud-compute-edition-admin.html",
-            },
-            {
-              type: "link",
-              label: "Release Notes",
-              href: "https://docs.paloaltonetworks.com/prisma/prisma-cloud/22-12/prisma-cloud-compute-edition-release-notes/release-information",
-            },
-          ],
-        },
-        {
-          type: "category",
-          label: "Compute 22.06",
-          items: [
-            {
-              type: "link",
-              label: "Administrator's Guide",
-              href: "https://docs.paloaltonetworks.com/content/techdocs/en_US/prisma/prisma-cloud/22-06/prisma-cloud-compute-edition-admin.html",
+              href: "https://docs.prismacloud.io/en/compute-edition/22-12/admin-guide",
             },
             {
               type: "link",
               label: "Release Notes",
-              href: "https://docs.paloaltonetworks.com/prisma/prisma-cloud/22-06/prisma-cloud-compute-edition-release-notes/release-information",
+              href: "https://docs.prismacloud.io/en/compute-edition/22-12/rn/release-information/release-notes-22-12-update4",
             },
           ],
         },
@@ -172,7 +162,7 @@ module.exports = {
             {
               type: "link",
               label: "Administrator's Guide",
-              href: "https://docs.paloaltonetworks.com/prisma/prisma-cloud/prisma-cloud-admin-compute.html",
+              href: "https://docs.prismacloud.io/en/enterprise-edition/content-collections",
             },
           ],
         },