First draft

Author: nastasha-solomon

docs/release-notes/8.18.asciidoc

@@ -51,23 +51,14 @@ After you complete this step, risk scores should automatically begin to successf
 ====
 // end::known-issue[]
 
-// tag::known-issue[]
-[discrete]
-.The technical preview badge incorrectly displays on the alert suppression fields for event correlation rules 
-[%collapsible]
-====
-*Details* +
-On April 8, 2025, it was discovered that alert suppression for event correlation rules is incorrectly shown as being in technical preview when you create a new rule. For more information, check https://github.com/elastic/docs-content/issues/1021[#1021].
-
-====
-// end::known-issue[]
 
 [discrete]
 [[bug-fixes-8.18.2]]
 ==== Fixes
 * Improves error telemetry for the AI assistant ({kibana-pull}220938[#220938]).
 * Simplifies and improves the rule import error message ({kibana-pull}218701[#218701]).
 * Fixes a bug that caused the Dashboard overview page to crash when a Lens widget aggregation error occurred ({kibana-pull}214888[#214888]).
+* Removes the technical preview badge from the alert suppression fields for event correlation rules.
 * Fixes a bug in {elastic-defend} 8.16.0 where {elastic-endpoint} would incorrectly report some files as being `.NET`.
 
 [discrete]
@@ -128,6 +119,9 @@ After you complete this step, risk scores should automatically begin to successf
 *Details* +
 On April 8, 2025, it was discovered that alert suppression for event correlation rules is incorrectly shown as being in technical preview when you create a new rule. For more information, check https://github.com/elastic/docs-content/issues/1021[#1021].
 
+*Resolved* +
+This issue is fixed in {stack} versions 8.18.2.
+
 ====
 // end::known-issue[]
 
@@ -221,6 +215,9 @@ Duplicate your rules and enable them.
 *Details* +
 On April 8, 2025, it was discovered that alert suppression for event correlation rules is incorrectly shown as being in technical preview when you create a new rule. For more information, check https://github.com/elastic/docs-content/issues/1021[#1021].
 
+*Resolved* +
+This issue is fixed in {stack} versions 8.18.2.
+
 ====
 // end::known-issue[]