Updates (#635)

Update manage_compliance.adoc
* Address customer feedback

Update scan_ibm_cloud_container_registry.adoc
* Add the correct path and followed up with the PM on some other 404s and syntax updates required for the registry and namespace

Update runtime_defense_containers.adoc
* Fix typos

Author: Pubs-MV

admin_guide/compliance/manage_compliance.adoc

@@ -1,4 +1,4 @@
-== Manage compliance
+== Enforce compliance checks
 
 Prisma Cloud can monitor and enforce compliance settings across your environment.
 Out of the box, Prisma Cloud supports hundreds of discrete checks that cover images, containers, hosts, clusters, and clouds.

admin_guide/runtime_defense/runtime_defense_containers.adoc

@@ -1,28 +1,25 @@
 == Runtime defense for containers
 
-Runtime defense is the set of features that provide both predictive and threat based active protection for running containers.
+Runtime defense is the set of features that provide both predictive and threat-based active protection for running containers.
 For example, predictive protection includes capabilities like determining when a container runs a process not included in the origin image or creates an unexpected network socket.
-Threat based protection includes capabilities like detecting when malware is added to a container or when a container connects to a botnet.
+Threat-based protection includes capabilities like detecting when malware is added to a container or when a container connects to a botnet.
 
-Prisma Cloud introduced runtime defense all the way back in our 1.1 release.
-In releases since then, we’ve continuously added to the feature set.
-This article describes the current architecture.
 
-Prisma Cloud has distinct sensors for file system, network, and process activity.
+Prisma Cloud Compute has distinct sensors for file system, network, and process activity.
 Each sensor is implemented individually, with its own set of rules and alerting.
-The runtime defense architecture is unified to both simplify the admin experience and to show more detail about what Prisma Cloud automatically learns from each image.
+The runtime defense architecture is unified to both simplify the administrator experience and to show more detail about what Prisma Cloud automatically learns from each image.
 Runtime defense has two principle object types: models and rules.
 
 
 === Container Models
 
 Models are the results of the autonomous learning that Prisma Cloud performs every time we see a new image in an environment.
-A model is the ‘allow list’ for what a given image should be doing, across all runtime sensors.
+A model is the ‘allow list’ for what a given container image should be doing, across all runtime sensors.
 Models are automatically created and maintained by Prisma Cloud and provide an easy way for administrators to view and understand what Prisma Cloud has learned about their images.
 For example, a model for an Apache image would detail the specific processes that should run within containers derived from the image and what network sockets should be exposed.
 
 Navigate to *Monitor > Runtime > Container Models*.
-Click on the image to view it’s model.
+Click on the image to view the model.
 
 There is a 1:1 relationship between models and images; every image has a model and every model applies to a single unique image.
 For each image, a unique model is created and mapped to the image digest.
@@ -96,9 +93,9 @@ This automatic switching only happens during the first 24 hours of model initiat
 
 === Archived mode
 
-Archived mode is a phase that models are transitioned into after no containers are actively running them.
-Models persist in archived mode for 24 hours after being archived, after which point they’re automatically removed by an internally managed garbage collection process.
-Archived mode essentially acts a 'recycle bin' for models, ensuring that a given image does not need go through learning mode again if it frequently starts and stops while also ensuring that the list of models does not continuously grow over time.
+Archived mode is a phase that models are transitioned into when a container is no longer actively running them.
+Models persist in archived mode for 24 hours after being archived, after which point they’re automatically removed.
+Archived mode serves as a 'recycle bin' for models, ensuring that a given image does not need go through learning mode again if it frequently starts and stops while also ensuring that the list of models does not continuously grow over time.
 
 Models display all the learned data across each of the runtime sensors to make it easy to understand exactly what Prisma Cloud has learned about an image and how it will protect it.
 However, what if you need to customize the protection for a given image, set of images, or containers?
@@ -131,8 +128,8 @@ By default, Prisma Cloud has a single rule that says 'use the models'.
 As with every other subsystem in Prisma Cloud, you can customize how it works by creating rules, scoping the rules to the desired objects with filtering and pattern matching, and then xref:../configure/rule_ordering_pattern_matching.adoc[properly ordering the rules] in the policy.
 Rules are evaluated sequentially from top to bottom.
 Once a match is found for the scope, the actions in the rule are executed and enforced.
-Only a single rule is ever enforced for a given event
-While rules are combined with models as described above, rules themselves are never combined.
+Only a single rule is ever enforced for a given event.
+While rules work in conjunction with models as described above, rules themselves are never combined.
 
 Prisma Cloud ships with a rule named *Default - alert on suspicious runtime behavior* that enables runtime protection for containers by default.
 You can further refine your policy by creating additional custom rules that target specific resources, enable or disable protection features, and define exceptions to the automatically generated allow-list models.

admin_guide/vulnerability_management/registry_scanning/scan_ibm_cloud_container_registry.adoc

@@ -31,7 +31,7 @@ See the IBM Cloud Docs to learn how to create a service ID for Prisma Cloud, and
 
 .. Click *Save*. 
 
-. Go to *Defend > Vulnerabilities > Registry*.
+. Go to *Defend > Vulnerabilities > Images > Registry settings*.
 
 . Click *Add registry*.