Propagate suggestions to other entries

docs/static/releasenotes.asciidoc

@@ -73,13 +73,13 @@ This section summarizes the changes in the following releases:
 === Logstash 8.15.4 Release Notes
 
 [[known-issues-8-15-4]]
-==== Known issues
+==== Known issue
 
-* **{ls} can fail to shut down under some circumstances when using pipeline-to-pipeline.**
+**{ls} can fail to shut down under some circumstances when you are using <<pipeline-to-pipeline>>.**
 Check out issue https://github.com/elastic/logstash/issues/16657[#16657] for details.
 +
-Workaround: Add `-Dlogstash.pipelinebus.implementation=v1` to `config/jvm.properties`, which reverts to using v1 of the `PipelineBus` that does not have this issue but may have performance impact in pipeline>pipeline scenarios.
-
+Workaround: Add `-Dlogstash.pipelinebus.implementation=v1` to `config/jvm.properties`.
+This change reverts the `PipelineBus` to `v1`, a version that does not exhibit this issue, but may impact performance in pipeline-to-pipeline scenarios.
 [[notable-8.15.4]]
 ==== Notable issues fixed
 
@@ -121,13 +121,13 @@ Workaround: Add `-Dlogstash.pipelinebus.implementation=v1` to `config/jvm.proper
 * Fixed Logstash core compatibility issues with `logstash-input-azure_event_hubs` versions `1.4.8` and earlier https://github.com/elastic/logstash/pull/16485[#16485]
 
 [[known-issues-8-15-3]]
-==== Known issues
+==== Known issue
 
-* **{ls} can fail to shut down under some circumstances when using pipeline-to-pipeline.**
+**{ls} can fail to shut down under some circumstances when you are using <<pipeline-to-pipeline>>.**
 Check out issue https://github.com/elastic/logstash/issues/16657[#16657] for details.
 +
-Workaround: Add `-Dlogstash.pipelinebus.implementation=v1` to `config/jvm.properties`, which reverts to using v1 of the `PipelineBus` that does not have this issue but may have performance impact in pipeline>pipeline scenarios.
-
+Workaround: Add `-Dlogstash.pipelinebus.implementation=v1` to `config/jvm.properties`.
+This change reverts the `PipelineBus` to `v1`, a version that does not exhibit this issue, but may impact performance in pipeline-to-pipeline scenarios.
 ==== Plugins
 
 *Elastic_integration Filter - 0.1.14*
@@ -154,13 +154,13 @@ Workaround: Add `-Dlogstash.pipelinebus.implementation=v1` to `config/jvm.proper
 * Fixed a https://github.com/elastic/logstash/issues/16437[regression] from {ls} 8.15.1 in which {ls} removes all quotes from docker env variables, possibly causing {ls} not to start https://github.com/elastic/logstash/pull/16456[#16456]
 
 [[known-issues-8-15-2]]
-==== Known issues
+==== Known issue
 
-* **{ls} can fail to shut down under some circumstances when using pipeline-to-pipeline.**
+**{ls} can fail to shut down under some circumstances when you are using <<pipeline-to-pipeline>>.**
 Check out issue https://github.com/elastic/logstash/issues/16657[#16657] for details.
 +
-Workaround: Add `-Dlogstash.pipelinebus.implementation=v1` to `config/jvm.properties`, which reverts to using v1 of the `PipelineBus` that does not have this issue but may have performance impact in pipeline>pipeline scenarios.
-
+Workaround: Add `-Dlogstash.pipelinebus.implementation=v1` to `config/jvm.properties`.
+This change reverts the `PipelineBus` to `v1`, a version that does not exhibit this issue, but may impact performance in pipeline-to-pipeline scenarios.
 ==== Plugins
 
 *Beats Input - 6.8.4*
@@ -196,10 +196,12 @@ If this situation occurs, {ls} may fail to start or some plugins may use a malfo
 Check out issue https://github.com/elastic/logstash/issues/16437[#16437] for details.
 +
 Workaround: Downgrade to {ls} 8.15.0, or temporarily avoid using environment and keystore variable references.
-* **{ls} can fail to shut down under some circumstances when using pipeline-to-pipeline.**
+* **{ls} can fail to shut down under some circumstances when you are using <<pipeline-to-pipeline>>.**
 Check out issue https://github.com/elastic/logstash/issues/16657[#16657] for details.
 +
-Workaround: Add `-Dlogstash.pipelinebus.implementation=v1` to `config/jvm.properties`, which reverts to using v1 of the `PipelineBus` that does not have this issue but may have performance impact in pipeline>pipeline scenarios.
+Workaround: Add `-Dlogstash.pipelinebus.implementation=v1` to `config/jvm.properties`.
+This change reverts the `PipelineBus` to `v1`, a version that does not exhibit this issue, but may impact performance in pipeline-to-pipeline scenarios.
+
 
 
 
@@ -241,7 +243,6 @@ Workaround: Add `-Dlogstash.pipelinebus.implementation=v1` to `config/jvm.proper
 
 **{ls} can fail to shut down under some circumstances when you are using <<pipeline-to-pipeline>>.**
 Check out issue https://github.com/elastic/logstash/issues/16657[#16657] for details.
-Check out issue https://github.com/elastic/logstash/issues/16657[#16657] for details.
 +
 Workaround: Add `-Dlogstash.pipelinebus.implementation=v1` to `config/jvm.properties`.
 This change reverts the `PipelineBus` to `v1`, a version that does not exhibit this issue, but may impact performance in pipeline-to-pipeline scenarios.