Update memory leak known issue to indicate all Beats are affected, up…

…dated workaround (#750)

* Update memory leak issue to indicate all Beats are affected

* Update based on Luca's feedback

* higher -> later

(cherry picked from commit fd30eec)

docs/en/ingest-management/release-notes/release-notes-8.11.asciidoc

@@ -55,7 +55,7 @@ The 8.11.3 patch release contains a fix for a potential security vulnerability.
 
 Review important information about {fleet-server} and {agent} for the 8.11.2 release.
 
-IMPORTANT: The memory leak <<known-issue-115-8.11.1,known issue>> that affects Windows users running {agent} is resolved in this release. If you're currently on {agent} version 8.11.0 or 8.11.1, we recommend upgrading to 8.11.2 to avoid the issue. If you're on an earlier version, avoid upgrading to version 8.11.0 or 8.11.1 and update directly to version 8.11.2.
+IMPORTANT: The memory leak <<known-issue-115-8.11.1,known issue>> that affects Windows users running {agent} is resolved in this release. If you're currently on {agent} version 8.11.0 or 8.11.1, we strongly recommend upgrading to 8.11.2 or a later release to avoid the issue. If you're on an earlier version, avoid upgrading to version 8.11.0 or 8.11.1 and update directly to version 8.11.2 or later.
 
 [discrete]
 [[enhancements-8.11.2]]
@@ -109,16 +109,24 @@ IMPORTANT: Due to a memory leak issue, Windows users running {agent} are recomme
 
 *Details*
 
-A memory leak has been identified in {metricbeat} on Windows. The leak also affects the {agent} System integration which is implemented with {metricbeat}. The leak will eventually exhaust all memory on the host system, typically after several days.
+A memory leak has been identified in {beats} on Windows. All {beats} running Elastic Stack version 8.11.0 or 8.11.1 are affected. The leak also affects the {agent} System integration which is implemented with {beats}. The leak will eventually exhaust all memory on the host system, typically after several days.
 
 *Impact* +
 
-This issue has been fixed in upcoming version 8.11.2. For a Windows environment, we recommend waiting for the official release of 8.11.2 before upgrading from 8.10.x or earlier.
+This issue has been fixed in version 8.11.2. For a Windows environment, we strongly recommend upgrading directly to 8.11.2 or any later release.
 
-If you're already running {agent} version 8.11.0 or 8.11.1 on Windows, we recommend disabling the `process` and `process_summary` metrics in your System integration and restarting {agent}. Note that disablling these datasets will prevent the collection of process-related metrics.
+If you're already running {agent} version 8.11.0 or 8.11.1 on Windows and do not want to upgrade, we recommend that you:
+
+. Disable the `process` and `process_summary` metrics in your System integration.
+. Disable logs and metrics collection.
+. Restart {agent}.
+ 
+Note that disabling these datasets will prevent the collection of process-related metrics.
 
 Another workaround is to downgrade {agent} to a version below 8.11.0. Note that this could result in missing or reindexed logs or metrics as the "state" will not be persisted after {agent} is uninstalled and reinstalled.
 
+For {beats} we currently do not have a workaround apart from upgrading to 8.12.2 or a later release.
+
 ====
 
 [[known-issue-169825-8.11.1]]
@@ -271,16 +279,24 @@ For more information, refer to {agent-pull}3593[#3593].
 
 *Details*
 
-A memory leak has been identified in {metricbeat} on Windows. The leak also affects the {agent} system integration which is implemented with {metricbeat}. The leak will eventually exhaust all memory on the host system, typically after several days.
+A memory leak has been identified in {beats} on Windows. All {beats} running Elastic Stack version 8.11.0 or 8.11.1 are affected. The leak also affects the {agent} System integration which is implemented with {beats}. The leak will eventually exhaust all memory on the host system, typically after several days.
 
 *Impact* +
 
-This issue has been fixed in upcoming version 8.11.2. For a Windows environment, we recommend waiting for the official release of 8.11.2 before upgrading from 8.10.x or earlier.
+This issue has been fixed in version 8.11.2. For a Windows environment, we strongly recommend upgrading directly to 8.11.2 or any higher release.
 
-If you're already running {agent} version 8.11.0 or 8.11.1 on Windows, we recommend disabling the `process` and `process_summary` metrics in your System integration and restarting {agent}. Note that disablling these datasets will prevent the collection of process-related metrics.
+If you're already running {agent} version 8.11.0 or 8.11.1 on Windows and do not want to upgrade, we recommend that you:
+
+. Disable the `process` and `process_summary` metrics in your System integration.
+. Disable logs and metrics collection.
+. Restart {agent}.
+ 
+Note that disabling these datasets will prevent the collection of process-related metrics.
 
 Another workaround is to downgrade {agent} to a version below 8.11.0. Note that this could result in missing or reindexed logs or metrics as the "state" will not be persisted after {agent} is uninstalled and reinstalled.
 
+For {beats} we currently do not have a workaround apart from upgrading to 8.12.2 or a later release.
+
 ====
 
 [[known-issue-169825-8.11.0]]