Identify and move abstract-type info to abstract

Author: aneta-petrova

guides/common/modules/con_compliance-email-notifications.adoc

@@ -4,6 +4,8 @@
 = Compliance email notifications
 
 [role="_abstract"]
+You can configure email notifications on your {ProjectServer} to stay informed about compliance policy changes.
+
 {ProjectServer} sends an OpenSCAP Summary email to all users who subscribe to the *Compliance policy summary* email notifications.
 For more information on subscribing to email notifications, see {AdministeringDocURL}Configuring_Email_Notification_Preferences_admin[Configuring Email Notification Preferences] in _{AdministeringDocTitle}_.
 

guides/common/modules/con_scap-content-in-project.adoc

@@ -4,12 +4,12 @@
 = SCAP content in {Project}
 
 [role="_abstract"]
+In {Project}, you use an XCCDF profile from SCAP content and, eventually, a tailoring file, to define a _compliance policy_.
+{Project} includes default SCAP contents from SCAP Security Guide provided by the https://www.open-scap.org/[OpenSCAP project].
+
 SCAP content is a SCAP data-stream file that contains implementation of compliance, configuration, or security baselines.
 A single data stream usually includes multiple XCCDF profiles.
 An XCCDF profile defines an industry standard or custom security standard against which you can evaluate compliance of host configuration in {Project}, such as Protection Profile for General Purpose Operating Systems (OSPP), Health Insurance Portability and Accountability Act (HIPAA), and PCI-DSS v3.2.1 Control Baseline for {EL}{nbsp}9.
 You can adapt existing XCCDF profiles according to your requirements by using _tailoring files_.
 
-In {Project}, you use an XCCDF profile from SCAP content and, eventually, a tailoring file, to define a _compliance policy_.
-{Project} includes default SCAP contents from SCAP Security Guide provided by the https://www.open-scap.org/[OpenSCAP project].
-
 {Project} supports content of SCAP versions 1.2 and 1.3.

guides/common/modules/con_security-compliance-management-in-project.adoc

@@ -5,7 +5,4 @@
 
 [role="_abstract"]
 Security compliance management is the ongoing process of defining security policies, auditing systems for compliance with those policies, and resolving instances of non-compliance.
-Any non-compliance is managed according to the organization's configuration management policies.
-Security policies range in scope from host-specific to industry-wide, therefore, flexibility in their definition is required.
-
 With {Project}, you can schedule compliance auditing and reporting on all registered hosts.

guides/common/modules/ref_compliance-policy-deployment-options.adoc

@@ -4,6 +4,8 @@
 = Compliance policy deployment options
 
 [role="_abstract"]
+With {Project}, multiple methods are available for compliance policy deployment.
+
 You can use one of the following methods to deploy compliance policies:
 
 Ansible deployment::

guides/common/modules/ref_inclusion-of-remote-scap-resources.adoc

@@ -5,6 +5,8 @@
 
 [role="_abstract"]
 SCAP data streams can reference remote resources, such as OVAL files, that the SCAP client fetches over the internet when it runs on hosts.
+You can enable the download of these remote resources for hosts with internet access.
+
 If a data stream requires a remote resource, you can see a warning from the OpenSCAP Scanner tool on your {ProjectServer}, such as:
 
 [options="nowrap", subs="+quotes,verbatim,attributes"]