From bf6e5ca63256326ea26ee44e701abcaf31a58ece Mon Sep 17 00:00:00 2001 From: Andrew Cholakian Date: Wed, 9 May 2018 18:48:05 -0500 Subject: [PATCH] Fix formatting of breaking changes to not split across pages The current formatting results in multiple pages, which is confusing, as seen on https://www.elastic.co/guide/en/logstash/current/breaking-changes.html Fixes #9550 --- docs/static/breaking-changes.asciidoc | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/static/breaking-changes.asciidoc b/docs/static/breaking-changes.asciidoc index 259eb28ca..16d4ec4c4 100644 --- a/docs/static/breaking-changes.asciidoc +++ b/docs/static/breaking-changes.asciidoc @@ -1,6 +1,6 @@ [[breaking-changes]] -== Breaking Changes Across PQ Versions Prior to Logstash 6.3.0 +===== Breaking Changes Across PQ Versions Prior to Logstash 6.3.0 The following applies only to users upgrading from Logstash installations that used the persistent queue prior to 6.3.0. @@ -10,12 +10,12 @@ If you are upgrading Logstash from a pre 6.3.0 version and use the persistent qu To drain the queue, enable the `queue.drain` setting, and then shutdown Logstash. Wait for it to shutdown completely. This may take a while if you have a large queue backlog. -== Breaking Changes in 6.0.0 +=== Breaking Changes in 6.0.0 This section discusses the changes that you need to be aware of when migrating to Logstash 6.0.0 from the previous major releases. [float] -=== Changes in Logstash Core +==== Changes in Logstash Core These changes can impact any instance of Logstash and are plugin agnostic, but only if you are using the features that are impacted.