Update "Blocklist"

Author: joepeeples

docs/management/admin/blocklist.asciidoc

@@ -16,7 +16,7 @@ The blocklist is not intended to broadly block benign applications for non-secur
 
 By default, a blocklist entry is recognized globally across all hosts running {elastic-defend}. If you have a https://www.elastic.co/pricing[Platinum or Enterprise subscription], you can also assign a blocklist entry to specific {elastic-defend} integration policies, which blocks the process only on hosts assigned to that policy.
 
-. Go to **Manage** -> **Blocklist**.
+. Find **Blocklist** in the main menu or use the {kibana-ref}/introduction.html#kibana-navigation-search[global search field].
 
 . Click **Add blocklist entry**. The **Add blocklist** flyout appears.
 
@@ -49,7 +49,7 @@ NOTE: You can also select the `Per Policy` option without immediately assigning
 . Click **Add blocklist**. The new entry is added to the **Blocklist** page.
 
 . When you're done adding entries to the blocklist, ensure that the blocklist is enabled for the {elastic-defend} integration policies that you just assigned:
-.. Go to **Manage** -> **Policies**, then click on an integration policy.
+.. Go to the **Policies** page, then click on an integration policy.
 .. On the **Policy settings** tab, ensure that the **Malware protections** and **Blocklist** toggles are switched on. Both settings are enabled by default.
 
 [discrete]

docs/serverless/edr-manage/blocklist.asciidoc

@@ -5,7 +5,7 @@
 
 preview:[]
 
-The blocklist (**Assets** → **Blocklist**) allows you to prevent specified applications from running on hosts, extending the list of processes that {elastic-defend} considers malicious. This helps ensure that known malicious processes aren't accidentally executed by end users.
+The blocklist allows you to prevent specified applications from running on hosts, extending the list of processes that {elastic-defend} considers malicious. This helps ensure that known malicious processes aren't accidentally executed by end users.
 
 The blocklist is not intended to broadly block benign applications for non-security reasons; only use it to block potentially harmful applications. To compare the blocklist with other endpoint artifacts, refer to <<security-optimize-edr>>.
 
@@ -22,7 +22,7 @@ The blocklist is not intended to broadly block benign applications for non-secur
 
 By default, a blocklist entry is recognized globally across all hosts running {elastic-defend}. You can also assign a blocklist entry to specific {elastic-defend} integration policies, which blocks the process only on hosts assigned to that policy.
 
-. Go to **Assets** → **Blocklist**.
+. Find **Blocklist** in the main menu or use the global search field.
 . Click **Add blocklist entry**. The **Add blocklist** flyout appears.
 . Fill in these fields in the **Details** section:
 +
@@ -60,14 +60,14 @@ You can also select the `Per Policy` option without immediately assigning a poli
 . Click **Add blocklist**. The new entry is added to the **Blocklist** page.
 . When you're done adding entries to the blocklist, ensure that the blocklist is enabled for the {elastic-defend} integration policies that you just assigned:
 +
-.. Go to **Assets** → **Policies**, then click on an integration policy.
+.. Go to the **Policies** page, then click on an integration policy.
 .. On the **Policy settings** tab, ensure that the **Malware protections** and **Blocklist** toggles are switched on. Both settings are enabled by default.
 
 [discrete]
 [[manage-blocklist]]
 == View and manage the blocklist
 
-The **Blocklist** page (**Assets** → **Blocklist**) displays all the blocklist entries that have been added to the {security-app}. To refine the list, use the search bar to search by name, description, or field value.
+The **Blocklist** page displays all the blocklist entries that have been added to the {security-app}. To refine the list, use the search bar to search by name, description, or field value.
 
 [role="screenshot"]
 image::images/blocklist/-management-admin-blocklist.png[]