[WFLY-14947] Micrometer AD updates

observability/WFLY-14947-Implement_observability_policy_metrics.adoc

@@ -46,26 +46,26 @@ While WildFly/EAP already supports basic metrics in the base WildFly/EAP system,
 * RBAC support for server/jvm metrics
 * Remove base/vendor prefixes (in accordance with Prometheus standards)
 * Mechanism for arbitrary subsystems to register meters (e.g., Micrometer's `MeterBinder`)
-
-=== Open Questions
-* Deprecate/remove/replace existing WildFly Metrics?
-* How to handle this subsystem under MicroProfile config?
+* This subsystem will replace the existing WildFly Metrics subsystem. Documentation will be provided describing the change.
+* If MicroProfile Metrics is enabled, this subsystem will disable itself, as is the current behavior of WildFly Metrics.
 
 === Nice-to-Have Requirements
-*
+_None at this time_
 
 === Non-Requirements
 * Support for multiple metric backends
-* Removal of MicroProfile Metrics (Future MP specs will address this)
+* Removal of MicroProfile Metrics (Future MicroProfile specs should address the relationship with Micrometer)
 * Removal of application metrics when a user application is undeployed
 * Transforming of Prometheus-compliant meter names to existing format
 
 == Test Plan
 * Add tests to testsuite/integration
 
 == Community Documentation
-The feature will be documented in WildFly Admin Guide (possibly in a new observability section).
+The feature will be documented in WildFly Admin Guide. A description of the differences in the output format will be
+listed.
 
 == Release Note Content
-Support for Micrometer was added, allowing applications to register and record metrics which will be aggregated and
-reported
+The WildFly Metrics subsystem has been replaced by the Micrometer subsystem. This will continue to provide application
+server JVM metrics via the existing /metrics endpoint, though now in a Prometheus-compliant format, and will also now
+allow user applications to register their own meters for export via the same endpoint.