After reviewing the following:

https://github.com/openshift/openshift-docs/pull/94394 

These are the changes that are needed:

CHANGE 1:

It needs to be very clear for the user that there are 2 compliance options side by side as well as what are the instructions to navigate to each of them. I feel right now that is not clear.
The user goes to the page 'Compliance feature Overview' on the side panel and gets two titles 'Dashboard' and 'OpenShift Schedules' and 'OpenShift Coverage' which is not necessarily explaining clearly our messy UI. 

One idea is to change the following:  Before getting into the two titles, let's describe a bit that there are 2 compliance functionalities side by side. The 1.0 (under Dashboard), currently deprecated applicable to kubernetes clusters. And OpenShift Infrastructure Compliance (under OpenShift Schedules and OpenShift Coverage) applicable to only OpenShift clusters. 

CHANGE 2:
After doing that, we can break down the two sections based on the way they are in the UI. 

First section can be called : OpenShift Schedules and OpenShift Coverage , and the second one 'Dashboard (deprecated)'.

Dashboard should be last because it is deprecated and we want our customers to look first at the newer one. 

CHANGE 3:
The subsequent sections which talk about Compliance Assessment and reporting need to be clear to which of these 2 compliance functionality are related to. 
For example:
 We need to think that our customers will be using one or the other compliance feature and and they just want all the relevant instructions about that one. 

Some examples: 
'Scheduling compliance scans and assessing profile compliance' only has content for OpenShift Infrastructure Compliance. 
at the same time 'Monitoring workload and cluster compliance' only has content for Compliance 1.0. 
Maybe we should call those sections something more descriptive:

From "Monitoring workload and cluster compliance" -> "Using the compliance dashboard (deprecated)".  [took the idea from deprecated vuln. management docs]

From "Scheduling compliance scans and assessing profile compliance" -> "Using OpenShift Compliance" 

CHANGE 4:
We don't need to call specifically that OpenShift Infrastructure Compliance is not available in EKS. It is not available neither in GKE, EKS, AKS... I think the statement that it is only available in OpenShift and w/ CO above than 1.6 version should be enough