diff --git a/docs/getting-started/configure-integration-policy.asciidoc b/docs/getting-started/configure-integration-policy.asciidoc
index 0e4fdff68b..2d6ab7fbbc 100644
--- a/docs/getting-started/configure-integration-policy.asciidoc
+++ b/docs/getting-started/configure-integration-policy.asciidoc
@@ -5,7 +5,7 @@ After the {agent} is installed with the {endpoint-sec} integration, several prot
 preventions against malware, ransomware, memory threats, and malicious behavior — are automatically enabled
 on protected hosts (some features require a Platinum or Enterprise license). If needed, you can update the
 integration policy to configure protection settings, event collection, antivirus settings, trusted applications,
-event filters, and host isolation exceptions to meet your organization's security needs.
+event filters, host isolation exceptions, and blocked applications to meet your organization's security needs.
 
 NOTE: You must have the {kib} `superuser` role to configure an integration policy in the {security-app}.
 
diff --git a/docs/management/admin/blocklist.asciidoc b/docs/management/admin/blocklist.asciidoc
index e1859414ea..360352e9b8 100644
--- a/docs/management/admin/blocklist.asciidoc
+++ b/docs/management/admin/blocklist.asciidoc
@@ -2,8 +2,6 @@
 [chapter]
 = Blocklist
 
-coming[8.2.0]
-
 The blocklist allows you to prevent specified applications from running on hosts, extending the list of processes that {endpoint-sec} considers malicious. This is especially useful for ensuring that known malicious processes aren't accidentally executed by end users. 
 
 [NOTE]