Apply suggestions from code review

elastic · Nov 12, 2024 · 8e0d67a · 8e0d67a
1 parent b4eede5
commit 8e0d67a
Showing 1 changed file with 6 additions and 6 deletions.
diff --git a/docs/static/releasenotes.asciidoc b/docs/static/releasenotes.asciidoc
@@ -79,7 +79,7 @@ This section summarizes the changes in the following releases:
 **{ls} may 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`.
+Workaround: Add `-Dlogstash.pipelinebus.implementation=v1` to `config/jvm.options`.
 This change reverts the `PipelineBus` to `v1`, a version that does not exhibit this issue, but may impact performance in pipeline-to-pipeline scenarios.
 
 [[health-api-8-16-0]]
@@ -174,7 +174,7 @@ the event or by sending it to the pipeline's DLQ if enabled. https://github.com/
 **{ls} may 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`.
+Workaround: Add `-Dlogstash.pipelinebus.implementation=v1` to `config/jvm.options`.
 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]]
@@ -216,7 +216,7 @@ This change reverts the `PipelineBus` to `v1`, a version that does not exhibit t
 **{ls} may 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`.
+Workaround: Add `-Dlogstash.pipelinebus.implementation=v1` to `config/jvm.options`.
 This change reverts the `PipelineBus` to `v1`, a version that does not exhibit this issue, but may impact performance in pipeline-to-pipeline scenarios.
 
 
@@ -253,7 +253,7 @@ This change reverts the `PipelineBus` to `v1`, a version that does not exhibit t
 **{ls} may 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`.
+Workaround: Add `-Dlogstash.pipelinebus.implementation=v1` to `config/jvm.options`.
 This change reverts the `PipelineBus` to `v1`, a version that does not exhibit this issue, but may impact performance in pipeline-to-pipeline scenarios.
 
 
@@ -301,7 +301,7 @@ Workaround: Downgrade to {ls} 8.15.0, or temporarily avoid using environment and
 * **{ls} may 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`.
+Workaround: Add `-Dlogstash.pipelinebus.implementation=v1` to `config/jvm.options`.
 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.1]]
@@ -343,7 +343,7 @@ This change reverts the `PipelineBus` to `v1`, a version that does not exhibit t
 **{ls} may 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`.
+Workaround: Add `-Dlogstash.pipelinebus.implementation=v1` to `config/jvm.options`.
 This change reverts the `PipelineBus` to `v1`, a version that does not exhibit this issue, but may impact performance in pipeline-to-pipeline scenarios.
 
 [[snmp-ga-8.15.0]]