From fd45de32d77c592c0ebaed55b275250afe74fbb2 Mon Sep 17 00:00:00 2001
From: Peter Wilcsinszky <peter.wilcsinszky@axoflow.com>
Date: Tue, 10 Oct 2023 12:30:55 +0200
Subject: [PATCH] reword whatsnew for timeout based configcheck

Signed-off-by: Peter Wilcsinszky <peter.wilcsinszky@axoflow.com>
---
 content/docs/whats-new/_index.md | 24 ++++--------------------
 1 file changed, 4 insertions(+), 20 deletions(-)

diff --git a/content/docs/whats-new/_index.md b/content/docs/whats-new/_index.md
index 96bdc49a1..ff5c41bdb 100644
--- a/content/docs/whats-new/_index.md
+++ b/content/docs/whats-new/_index.md
@@ -40,32 +40,16 @@ In a future Logging operator version the logs of the aggregators will also be av
 
 ### Timeout-based configuration checks
 
-You can now use timeout-based configuration strategies for both syslog-ng and Fluentd. For example:
+Timeout based configuration checks are different from the normal method in that it starts a fluentd or syslog-ng instance
+without the dry-run or syntax-check flags, so that output plugins or destination drivers will actually try to establish
+connections and will fail if there are any issues with the credentials for example.
 
+Add the following to you `Logging` resource spec:
 ```yaml
-apiVersion: logging.banzaicloud.io/v1beta1
-kind: Logging
-metadata:
-  name: all-to-file
 spec:
   configCheck:
     strategy: StartWithTimeout
     timeoutSeconds: 5
-  syslogNG: {}
-  controlNamespace: default
-```
-
-```yaml
-apiVersion: logging.banzaicloud.io/v1beta1
-kind: Logging
-metadata:
-  name: all-to-file
-spec:
-  configCheck:
-    strategy: StartWithTimeout
-    timeoutSeconds: 5
-  fluentd: {}
-  controlNamespace: default
 ```
 
 ### Istio support