docs: update MetaMask version and remove admonitions

README.md

@@ -35,18 +35,21 @@ or
 
 ## Keyring Snaps
 
-Starting with MetaMask 11.5, Snaps can implement the Keyring API. This allows
+> **:pencil: Note:** To test your Snap, you will need MetaMask 11.4 or later.
+> You can also build MetaMask from [source][extension-repo] from the `develop`
+> branch.
+
+Starting with MetaMask 11.4, Snaps can implement the Keyring API. This allows
 users to manage their accounts in a more flexible way, and enables developers
 to build new types of accounts.
 
-> [!IMPORTANT]
-> Before implementing your Snap, please make sure to read the [security
-> recommendations](./docs/security.md) and the [architecture
+> **:point_up: Important**: Before implementing your Snap, please make sure to read the
+> [security recommendations](./docs/security.md) and the [architecture
 > document](./docs/architecture.md).
 
 Follow these steps to implement the Keyring API in your Snap. Please note that
 these instruction assume that you are already familiar with the process of
-[developing a Snap](https://docs.metamask.io/).
+[developing a Snap](https://docs.metamask.io/snaps/).
 
 1. **Implement the Keyring API:**
 
@@ -58,10 +61,9 @@ these instruction assume that you are already familiar with the process of
    }
    ```
 
-   > [!WARNING]
-   > Ensure that your keyring implements the [methods called by
-   > MetaMask](./docs/security.md#limit-the-methods-exposed-to-dapps),
-   > otherwise some features may not work.
+   > **:point_up: Important**: Ensure that your keyring implements the [methods
+   > called by MetaMask][exposed-methods], otherwise some features may not
+   > work.
 
 2. **Handle requests submitted by MetaMask:**
 
@@ -175,8 +177,7 @@ these instruction assume that you are already familiar with the process of
 
       MetaMask will return an error if the request does not exist.
 
-      > [!NOTE]
-      > This only applies to Snaps that implement the [async
+      > **:pencil: Note:** This only applies to Snaps that implement the [async
       > flow](./docs/architecture.md#transaction-flow).
 
    5. When a request is rejected:
@@ -194,8 +195,7 @@ these instruction assume that you are already familiar with the process of
 
       MetaMask will return an error if the request does not exist.
 
-      > [!NOTE]
-      > This only applies to Snaps that implement the [async
+      > **:pencil: Note:** This only applies to Snaps that implement the [async
       > flow](./docs/architecture.md#transaction-flow).
 
 4. **Expose the Keyring API:**
@@ -282,9 +282,9 @@ implementation:
   emitSnapKeyringEvent(snap, KeyringEvent.RequestRejected, { id: request.id });
   ```
 
-  > [!IMPORTANT]
-  > For all events above, MetaMask may return an error indicating that the
-  > event was not handled, possibly because it contains invalid arguments.
+  > **:point_up: Important**: For all events above, MetaMask may return an error
+  > indicating that the event was not handled, possibly because it contains
+  > invalid arguments.
 
 - Keyrings that implement the [async transaction
   flow](./docs/architecture.md#transaction-flow) can now return an optional
@@ -395,3 +395,6 @@ The project follows the same release process as the other libraries in the MetaM
    - Wait for the `publish-release` GitHub Action workflow to finish. This should trigger a second job (`publish-npm`), which will wait for a run approval by the [`npm publishers`](https://github.com/orgs/MetaMask/teams/npm-publishers) team.
    - Approve the `publish-npm` job (or ask somebody on the npm publishers team to approve it for you).
    - Once the `publish-npm` job has finished, check npm to verify that it has been published.
+
+[extension-repo]: https://github.com/MetaMask/metamask-extension
+[exposed-methods]: ./docs/security.md#limit-the-methods-exposed-to-dapps