Make Consumer usage scenario examples more clear in section 3.1.2

[david-waltermire]

In section 3.1.2 the following text represents examples with little to no distinction:

"Whether it is a configuration verification system; a checklist verification system; or a system for detecting posture deviations, compliance or vulnerabilities"

The functional distinctions between these examples are not clear and can be construed as very similar concepts. The following text may help make this text more clear:

Old:

As described in Section 2.2 of the SACM Use Cases
[I-D.ietf-sacm-use-cases], several usage scenarios are posed with
different application types requesting posture assessment
information. Whether it is a configuration verification system; a
checklist verification system; or a system for detecting posture
deviations, compliance or vulnerabilities, they all need to acquire
information about Posture Assessment. The architectural component
performing such requests is a Consumer.

New:

As described in Section 2.2 of the SACM Use Cases
[I-D.ietf-sacm-use-cases], several usage scenarios are focused
around requesting posture assessment information to measure
compliance and to detect posture deviations supporting the
management of configurations, vulnerabilities, and other
Posture Assessment uses. Support for these usage scenarios requires
the acquisition of information pertaining to endpoint posture. The
architectural component performing such requests is a Consumer.