[Cloud Sec] 24.10.1 updates (#923)

* [Cloud Sec] 24.10.1 updates

* dev feedback update

* add links to co-pilot

* fixed link

docs/en/enterprise-edition/content-collections/alerts/risk-prioritization-remediation.adoc

@@ -6,6 +6,8 @@ With Prisma Cloud risk prioritization you can find out what is going wrong in yo
 
 Prisma Cloud reports issues, such as misconfigurations, network exposures, anomalies, and threats as *Findings*. On the Home page, begin with the view into the urgent risks and incidents detected in the last 24 hours and prioritize accordingly.
 
+You can use xref:../prisma-cloud-copilot/prisma-cloud-copilot-benefits.adoc[Prisma Cloud Copilot] to easily find risks and manage vulnerabilities in your cloud environment.
+
 image::alerts/home-urgent-risks-1.png[]
 
 [#remediate]

docs/en/enterprise-edition/content-collections/book.yml

@@ -532,8 +532,7 @@ topics:
         topics:
           - name: Container Network Exposure
             file: container-network-exposure.adoc
-          - name: Overview of Container Network Exposure
-          - name: Overview of Container Network Exposure	          
+          - name: Overview of Container Network Exposure         
             file: container-network-exposure-overview.adoc
           - name: Pre-requisites and Supported Objects and Platforms for Satellite Deployment
             file: satellite-prerequisites.adoc            

docs/en/enterprise-edition/content-collections/governance/create-a-policy.adoc

@@ -81,7 +81,7 @@ config from cloud.resource where resource.status = Active AND api.name = 'aws-ac
 ----
 +
 *NOTE:*
-When creating a custom policy, as a best practice *do not* include `cloud.account`, `cloud.accountgroup`, `cloud.region`, `resource.status`, or `tag` attributes in the RQL query. If you have a saved search that includes these attributes, make sure to edit the RQL before you create a custom policy. While these attributes are useful to filter the results you see on the *Investigate* tab, they are ignored when used in a custom policy.
+When creating a custom policy, as a best practice *do not* include `cloud.account`, `cloud.accountgroup`, `cloud.region`, `resource.status`, or `tag` attributes in the RQL query. If you have a saved search that includes these attributes, make sure to edit the RQL before you create a custom policy. While these attributes are useful to filter the results you see on *Investigate*, they are ignored by the policy engine (scanner) when used in a custom policy.
 
 .. [[idbdc1e8bb-8c17-4b05-b428-0bb4fd6f5a2a]]Add a rule for the *Build* phase.
 +

docs/en/enterprise-edition/content-collections/search-and-investigate/c2c-tracing-vulnerabilities/investigate-vulnerabilities-tracing.adoc

@@ -2,6 +2,8 @@
 
 You can benefit from the C2C vulnerability tracing automatically since everytime you select a runtime workload where tracing is available, the Investigate graph will automatically identify the root cause of a vulnerability and it's content. 
 
+Use xref:../../prisma-cloud-copilot/prisma-cloud-copilot-benefits.adoc[Prisma Cloud Copilot] to easily find, understand, and manage vulnerabilities in your cloud environment.
+
 image::search-and-investigate/c2c-tracing-4.png[]
 
 The assets can be in one of the following three available states: