chore: fix integration docs

Author: shane-t

integration-docs/accounts.md

@@ -2,4 +2,4 @@ Custodians are responsible for maintaining the list of accounts a user can acces
 
 These can correspond to private keys held in a HSM, EOAs that are controlled by shared secrets, or any other mechanism that allows the custodian to sign transactions on behalf of the user. Contract wallets are also supported, although they generally cannot sign messages.
 
-The custodial snap, once authenticated, will ask the custodian for a list of accounts for this user using the custodian_listAccounts method of the Ethereum Custodian API.
+The institutional snap, once authenticated, will ask the custodian for a list of accounts for this user using the custodian_listAccounts method of the Ethereum Custodian API.

integration-docs/architecture.md

@@ -1,5 +1,5 @@
 # Overview
 
-The custodial snap is a preinstalled component of MetaMask that allows users to interact with decentralised applications across EVMs and propose transactions to custodians as if the keys were stored in the extension. It is a thin client that runs in the browser and communicates directly with a custodian service to initiate transactions and message signing.
+The institutional snap is a preinstalled component of MetaMask that allows users to interact with decentralised applications across EVMs and propose transactions to custodians as if the keys were stored in the extension. It is a thin client that runs in the browser and communicates directly with a custodian service to initiate transactions and message signing.
 
 Custodians are responsible for account management abd transaction/message signing, including being ultimately accountable for nonce and gas parameters. They are also responsible for providing the user with a way to authenticate with the extension.

integration-docs/authentication.md

@@ -2,9 +2,9 @@
 
 When users import their custodial accounts, they enter a refresh token, or multiple tokens for access to multiple accounts. This token is used to fetch access tokens use to make requests to the custodian API. See below for the specification of the token refresh endpoint.
 
-All requests made by the custodial snap to the Ethereum Custodian API (JSON-RPC API) will use this access token.
+All requests made by the institutional snap to the Ethereum Custodian API (JSON-RPC API) will use this access token.
 
-!!! important Custodians must keep separate any tokens issued to users (for example, in the custodian UI) that are capable of signing transactions. In other words, credentials used in the custodial snap should never have the capability to actually cause transfer of funds.
+!!! important Custodians must keep separate any tokens issued to users (for example, in the custodian UI) that are capable of signing transactions. In other words, credentials used in the institutional snap should never have the capability to actually cause transfer of funds.
 
 If the custodian has a web UI, they should implement a button or link that takes advantage of RPC Onboarding.
 
@@ -16,7 +16,7 @@ Your refresh token endpoint must support application/json request bodies.
 
 ## Example requests
 
-Here are some example requests. that would be made by the custodial snap to your refresh token endpoint.
+Here are some example requests. that would be made by the institutional snap to your refresh token endpoint.
 
 ```json
 application/json
@@ -48,18 +48,18 @@ It is intended that refresh tokens should last a long time, if not forever. Howe
 
 ### Non-interactive token replacement
 
-Any time the custodial snap encounters a refresh token in the `refresh_token` field of the response from the token refresh endpoint which is different from the stored refresh token, it will be saved as the new refresh token for any accounts that were onboarded using the old token.
+Any time the institutional snap encounters a refresh token in the `refresh_token` field of the response from the token refresh endpoint which is different from the stored refresh token, it will be saved as the new refresh token for any accounts that were onboarded using the old token.
 
 
 ## FAQ
 
 ### Are refresh tokens securely stored?
-The custodial snap stores the custodian refresh token in a vault (keyring) which is encrypted while the extension is locked. After injection, this token never leaves the vault. The security is the same as MetaMask's storage of private keys and seed phrases.
+The institutional snap stores the custodian refresh token in a vault (keyring) which is encrypted while the extension is locked. After injection, this token never leaves the vault. The security is the same as MetaMask's storage of private keys and seed phrases.
 
-### Does the custodial snap support Oauth 2.0?
-The custodial snap does not use a standard Oauth 2.0 flow. However, it does contain elements of the client credentials grant and the refresh token grant. This is to facilitate custodian web applications, mobile apps, and desktop applications.
+### Does the institutional snap support Oauth 2.0?
+The institutional snap does not use a standard Oauth 2.0 flow. However, it does contain elements of the client credentials grant and the refresh token grant. This is to facilitate custodian web applications, mobile apps, and desktop applications.
 
-The user provides, from the custodian, a refresh token. The custodial snap uses this token to obtain the actual token for accompanying requests.
+The user provides, from the custodian, a refresh token. The institutional snap uses this token to obtain the actual token for accompanying requests.
 
-Ideally, this token is issued in a non-interactive way; i.e. the credential exchange happens at the custodian and this is effectively a Machine-to-Machine token. Since the custodial snap is an extension and not an ordinary web application, it cannot accept redirects.x
+Ideally, this token is issued in a non-interactive way; i.e. the credential exchange happens at the custodian and this is effectively a Machine-to-Machine token. Since the institutional snap is an extension and not an ordinary web application, it cannot accept redirects.x
 ```

integration-docs/index.md

@@ -1,6 +1,6 @@
-This document is for crypto custodians looking to integrate with the custodial snap.
+This document is for crypto custodians looking to integrate with the institutional MetaMask snap.
 
-The custodial snap provides a customized client library that supports custodian APIs. This document is a guide to the API a custodian must have in order for it to be usable with the custodial snap.
+The institutional snap provides a customized client library that supports custodian APIs. This document is a guide to the API a custodian must have in order for it to be usable with the institutional snap.
 
 ## How it works
 
@@ -20,4 +20,4 @@ The custodial snap provides a customized client library that supports custodian
 
 ## How to get allowlisted
 
-Please create a pull request on this repository adding your API to the list of allowlisted custodians in [this file](/packages/snap/src/lib/custodian-types/custodianMetadata.ts.
+Please create a pull request on this repository adding your API to the list of allowlisted custodians in [this file](/packages/snap/src/lib/custodian-types/custodianMetadata.ts.)

integration-docs/rpc-api.md

@@ -1,4 +1,4 @@
-# MMI's JSON-RPC provider
+# JSON-RPC provider
 
 !!! info "Terminology information"
 This document refers to the `injected RPC provider` also known as `window.ethereum`. This is the provider that is injected into the browser by Metamask. It does not refer to the JSON-RPC endpoint served by the custodian, or the JSON-RPC provider endpoint served by Ethereum nodes.
@@ -7,18 +7,18 @@ The browser ethereum provider is used by dapps to communicate with the extension
 
 ### Initial connection
 
-In order to first check if the custodial snap is installed and to use later method, it's first necessary to establish a connection.
+In order to first check if the institutional snap is installed and to use later method, it's first necessary to establish a connection.
 
 ```
 await window.ethereum.request({
   method: "wallet_requestSnaps",
   params: {
-    "npm:@metamask/custodial-wallet-snap": {},
+    "npm:@metamask/institutional-wallet-snap": {},
   },
 })
 ```
 
-Once the custodial is fully integrated, the custodian UI can be added as an initial connection and this step can be skipped.
+Once the custodian is fully integrated, the custodian UI can be added as an initial connection and this step can be skipped.
 
 ## authentication.onboard : Inject the token
 
@@ -34,7 +34,7 @@ Several values here will depend on the your integration process.
 await window.ethereum.request({
   method: 'wallet_invokeSnap',
   params: {
-    snapId: 'npm:@metamask/custodial-wallet-snap',
+    snapId: 'npm:@metamask/institutional-wallet-snap',
     request: {
       method: 'authentication.onboard',
       params: {

integration-docs/transactions.md

@@ -5,7 +5,7 @@ Relevant JSON-RPC method: `custodian_createTransaction`
 
 ![Areas of responsibility - transactions](../../assets/images/transaction-responsibility.png)
 
-MetaMask via the custodial snap creates/proposes transactions to the custodian API, including a proposed gas price. However, custodians may (at their users' request, or automatically) use a different gas price. Custodians are responsible for the ordering of transactions.
+MetaMask via the institutional snap creates/proposes transactions to the custodian API, including a proposed gas price. However, custodians may (at their users' request, or automatically) use a different gas price. Custodians are responsible for the ordering of transactions.
 
 ## Supporting multiple chains
 
@@ -21,7 +21,7 @@ This is the network that the user intended to create the transaction on.
 This parameter is needed to sign an ethereum transaction, and custodians can also use it to decide where to broadcast the transaction.
 
 `custodian_listAccountChainIds`
-A custodian_listAccountChainIds method exists on the Custodian JSON-RPC API which is executed when the extension is unlocked, for each custodian account stored in MMI.
+A custodian_listAccountChainIds method exists on the Custodian JSON-RPC API which is executed when the extension is unlocked, for each custodian account stored in the institutional snap.
 
 This method takes a single parameter, the ethereum account address in question. Custodians may ignore this parameter if users use their addresses with all their configured chains.