Snap dialogs do not support metamask:: urls (#1970)

Author: alexandratran

snaps/features/custom-ui/dialogs.md

@@ -13,10 +13,11 @@ There are four types of dialogs: [alerts](#display-an-alert-dialog),
 [confirmations](#display-a-confirmation-dialog), [prompts](#display-a-prompt-dialog), and
 [custom dialogs](#display-a-custom-dialog).
 
-:::caution
-Dialogs do not work when MetaMask is locked.
-To check if MetaMask is locked, use
-[`snap_getClientStatus`](../../reference/snaps-api.md#snap_getclientstatus).
+:::warning
+- Dialogs do not work when MetaMask is locked.
+  To check if MetaMask is locked, use
+  [`snap_getClientStatus`](../../reference/snaps-api.md#snap_getclientstatus).
+- [`metamask:` URLs](index.md#about-metamask-urls) are not supported in dialogs.
 :::
 
 ## Request permission to display dialogs

snaps/features/custom-ui/index.md

@@ -999,8 +999,9 @@ A Snap can link to the following screens using the `metamask:` scheme:
   Snap IDs for local testing and production.
 
 :::warning
-MetaMask will throw an error if the URL is not valid or if the URL leads to a Snap that is not 
-installed. 
+- MetaMask will throw an error if the URL is not valid or if the URL leads to a Snap that is not 
+installed.
+- `metamask:` URLs are not supported in [dialogs](dialogs.md).
 :::
 
 #### Example

snaps/features/notifications.md

@@ -66,7 +66,7 @@ Each Snap can trigger up to:
 ## Expanded view
 
 In-app notifications can include an optional expanded view that displays when selected.
-The expanded view includes a title, content, and an optional footer link. 
+The expanded view includes a title, [custom UI](custom-ui/index.md) content, and an optional footer link. 
 
 The following example displays a notification in MetaMask, with the message "Hello, world!"
 When the user selects the notification, the expanded view displays a page with a title, a paragraph, and a link to the MetaMask Snaps directory:

snaps/features/signature-insights.md

@@ -107,8 +107,8 @@ Your Snap should use `signatureMethod` as the source of truth to identify the si
 providing insights for.
 
 Once you've identified the signature object, your Snap can run any logic, including calling APIs.
-Then, your Snap must either return `null` if it has no insights to provide, or an object with a
-`content` property and an optional `severity` property as specified in the
+Then, your Snap must either return `null` if it has no insights to provide, or an object with
+[custom UI](custom-ui/index.md) content and an optional `severity` property as specified in the
 [`onSignature`](../reference/entry-points.md#onsignature) entry point.
 
 The following is an example implementation of `onSignature`:

snaps/features/transaction-insights.md

@@ -40,7 +40,8 @@ permission object, and set it to `true`:
 ### 2. Implement the `onTransaction` entry point
 
 Expose an [`onTransaction`](../reference/entry-points.md#ontransaction) entry point, which receives
-a raw unsigned transaction payload, the chain ID, and the optional transaction origin.
+a raw unsigned transaction payload, the chain ID, and the optional transaction origin,
+and returns [custom UI](custom-ui/index.md) content.
 When a user submits a transaction using the MetaMask extension, MetaMask calls the `onTransaction`
 handler method.