Convert using and integrating-metamask to .mdx

onflow · Nov 25, 2024 · a167f23 · a167f23
1 parent 6139ffc
commit a167f23
Show file tree

Hide file tree

Showing 5 changed files with 5 additions and 5 deletions.
diff --git a/docs/build/core-contracts/13-evm.md b/docs/build/core-contracts/13-evm.md
@@ -7,7 +7,7 @@ sidebar_label: EVM
 # Contract
 
 The `EVM` contract is the entrypoint from Cadence to EVM on Flow. While many developers may choose to interact with EVM
-via [EVM-equivalent tooling paths](../../evm/using.md), all access to Flow EVM ultimately interfaces via Cadence at
+via [EVM-equivalent tooling paths](../../evm/using.mdx), all access to Flow EVM ultimately interfaces via Cadence at
 some level.
 
 If you would like to interact with EVM directly from Cadence, you can use the `EVM` contract and it's constructs. Read

diff --git a/docs/evm/accounts.md b/docs/evm/accounts.md
@@ -18,7 +18,7 @@ There are three types of accounts used for EVM on Flow.
 2. **Contract Accounts**: These accounts hold smart contract code and are governed by this code's logic. Unlike EOAs, Contract Accounts do not initiate transactions on their own but can execute transactions in response to calls they receive from EOAs or other contracts.
 3. **Cadence Owned Accounts (COA)**: This is an account type unique to Flow EVM. These accounts are managed by [Cadence resources](https://cadence-lang.org/docs/language/resources) and can be used to interact with the Flow EVM from within the Cadence environment.
 
-EOAs and Contract accounts function the same as on other EVM networks. Users may interact with these accounts using the standard EVM JSON-RPC API ([see endpoints here](./using.md)). You can read more about EOAs and Contract accounts on the [Ethereum docs](https://ethereum.org/developers/docs/accounts).
+EOAs and Contract accounts function the same as on other EVM networks. Users may interact with these accounts using the standard EVM JSON-RPC API ([see endpoints here](./using.mdx)). You can read more about EOAs and Contract accounts on the [Ethereum docs](https://ethereum.org/developers/docs/accounts).
 
 However, in order to leverage all the features of Cadence, developers will need to utilize Cadence Owned Accounts.
 

diff --git a/docs/evm/guides/integrating-metamask.md → docs/evm/guides/integrating-metamask.mdx b/docs/evm/guides/integrating-metamask.md → docs/evm/guides/integrating-metamask.mdx
@@ -78,6 +78,6 @@ After they approve, your app will be connected to the Flow network.
 
 By using this approach to add the Flow network to Metamask, you can avoid manual user data entry and ensure that users are ready to interact with your dApp!
 
-<!-- Reference-style links, does not render on page -->
+{/* Reference-style links, does not render on page */}
 
-[manual process]: ../using.md
+[manual process]: ../using.mdx
diff --git a/docs/evm/guides/remix.md b/docs/evm/guides/remix.md
@@ -13,7 +13,7 @@ Remix is an open-source, web-based development environment tailored for EVM smar
 
 ![Add Flow Network](./Remix-adding-metamask-network.gif)
 
-Navigate to the [Using EVM](../using.md) page to find the button to add the Flow network information to your metamask.
+Navigate to the [Using EVM](../using.mdx) page to find the button to add the Flow network information to your metamask.
 
 ## Fund Your Flow Account
 

diff --git a/docs/evm/using.md → docs/evm/using.mdx b/docs/evm/using.md → docs/evm/using.mdx