OBSDOCS-639: Fix version number and other minor edits

Author: abrennan89

modules/logging-release-notes-5-8-0.adoc

@@ -45,7 +45,7 @@ In order to support multi-cluster log forwarding in additional namespaces other
 === Log Console
 * With this update, you can enable the Logging Console Plugin when Elasticsearch is the default Log Store. (link:https://issues.redhat.com/browse/LOG-3856[LOG-3856])
 
-* With this update, OpenShift Application owners can receive notifications for application-logs-based alerts on the OpenShift Developer Console view for {product-title} version 4.14 and greater. (link:https://issues.redhat.com/browse/LOG-3548[LOG-3548])
+* With this update, {product-title} application owners can receive notifications for application log-based alerts on the {product-title} web console *Developer* perspective for {product-title} version 4.14 and later. (link:https://issues.redhat.com/browse/LOG-3548[LOG-3548])
 
 [id="logging-release-notes-5-8-0-known-issues"]
 == Known Issues
@@ -57,9 +57,9 @@ In order to support multi-cluster log forwarding in additional namespaces other
 
 * Currently, `must-gather` cannot gather any logs on a FIPS-enabled cluster, because the required OpenSSL library is not available in the `cluster-logging-rhel9-operator`. There is currently no workaround for this issue. (link:https://issues.redhat.com/browse/LOG-4403[LOG-4403])
 
-* Currently, when deploying Logging 5.6.5 on a FIPS-enabled cluster, the collector pods cannot start and are stuck in `CrashLoopBackOff` status, while using FluentD as a collector. There is currently no workaround for this issue. (link:https://issues.redhat.com/browse/LOG-3933[LOG-3933])
+* Currently, when deploying the {logging} version 5.8 on a FIPS-enabled cluster, the collector pods cannot start and are stuck in `CrashLoopBackOff` status, while using FluentD as a collector. There is currently no workaround for this issue. (link:https://issues.redhat.com/browse/LOG-3933[LOG-3933])
 
 
 [id="logging-release-notes-5-8-0-CVEs"]
 == CVEs
-* link:https://access.redhat.com/security/cve/CVE-2023-40217[CVE-2023-40217]
+* link:https://access.redhat.com/security/cve/CVE-2023-40217[CVE-2023-40217]