CWP-52985 - Custom Compliance checks (#363)

docs/en/classic/compute-admin-guide/compliance/custom-compliance-checks.adoc

@@ -1,28 +1,24 @@
 == Custom compliance checks
 
-Custom image checks give you a way to write and run your own compliance checks to assess, measure, and enforce security baselines in your environment.
-
-Prisma Cloud lets you implement your custom image checks with simple scripts.
+With custom image checks you can write and run your own compliance checks to assess, measure, and enforce security baselines in your environment. Prisma Cloud allows you to implement your custom image checks with simple scripts.
 
 Custom compliance checks are supported for:
 
-- Linux and Windows hosts (Host configured for docker, containerd, or CRI-O)
 - Docker images on Linux hosts
+- Linux and Windows hosts (Host configured for docker, containerd, or CRI-O)
 - OCI images
 
 Custom compliance checks are not supported for:
 
-- Linux and Windows containers
+- Agentless scanning on Windows hosts
 - Docker images on Windows hosts
-- Tanzu Application Service (TAS) defender
 - GKE Autopilot
+- Linux and Windows containers
+- Tanzu Application Service (TAS) defender
 
-A custom image check consists of a single script.
-The script's exit code determines the result of the check, where "0" stands for pass and "1" stands for fail.
+A custom image check consists of a single script. The script's exit code determines the result of the check, where "0" stands for pass and "1" stands for fail.
 
-Scripts are executed in the default shell.
-The most common default shell for Linux is bash, but that's not always the case.
-For Windows container images, the default shell is cmd.exe.
+Scripts are executed in the default shell. The common default shell for Linux is bash, in most cases. For Windows container images, the default shell is cmd.exe.
 
 [NOTE]
 ====