[format] Format all files

Author: gregnazario

package.json

@@ -159,8 +159,6 @@
       "eslint --fix",
       "prettier --write"
     ],
-    "src/content/**/*.mdx": [
-      "remark --output"
-    ]
+    "src/content/**/*.mdx": []
   }
 }

src/content/docs/build/ai/aptos-mcp.mdx

@@ -22,7 +22,7 @@ and others that support the Model Context Protocol.
 
 To be able to make Geomi actions like managing API keys, etc., follow these instructions to generate a new Bot API Key to use with the MCP.
 
-- Go to https://geomi.dev/
+- Go to [https://geomi.dev/](https://geomi.dev/)
 - Click on your name in the bottom left corner
 - Click on "Bot Keys"
 - Click on the "Create Bot Key" button

src/content/docs/build/apis/data-providers.mdx

@@ -56,12 +56,12 @@ We also have sample analytics queries [using the above resources](https://github
 
 ### Dune
 
-We have a dashboard here: https://dune.com/aptos/aptos-chain-metrics-overview
+We have a dashboard here: [https://dune.com/aptos/aptos-chain-metrics-overview](https://dune.com/aptos/aptos-chain-metrics-overview)
 
 ### Allium
 
-Data source for many downstream vendors such as defillama and rwa.xyz. Raw data is available: https://docs.allium.so/historical-data/supported-blockchains/move-ecosystem/aptos
-They also have transfers for stablecoins https://docs.allium.so/historical-data/stablecoins#stablecoin-metrics
+Data source for many downstream vendors such as defillama and rwa.xyz. Raw data is available: [https://docs.allium.so/historical-data/supported-blockchains/move-ecosystem/aptos](https://docs.allium.so/historical-data/supported-blockchains/move-ecosystem/aptos)
+They also have transfers for stablecoins [https://docs.allium.so/historical-data/stablecoins#stablecoin-metrics](https://docs.allium.so/historical-data/stablecoins#stablecoin-metrics)
 
 ### Artemis
 

src/content/docs/build/apis/faucet-api.mdx

@@ -9,7 +9,7 @@ The faucet allows users to get `APT` on devnet. On testnet you can only mint at
 
 The endpoints for each faucet are:
 
-- Devnet: https://faucet.devnet.aptoslabs.com
+- Devnet: [https://faucet.devnet.aptoslabs.com](https://faucet.devnet.aptoslabs.com)
 
 ## Using the faucet
 

src/content/docs/build/cli/install-cli/install-cli-mac.mdx

@@ -12,7 +12,7 @@ For Mac, the easiest way to install the Aptos CLI is with the package manager `b
 # Installation
 
 <Steps>
-  1. Ensure you have brew installed https://brew.sh/.
+  1. Ensure you have brew installed [https://brew.sh/](https://brew.sh/).
 
   2. Open a new terminal and enter the following commands.
 

src/content/docs/build/get-started/ethereum-cheatsheet.mdx

@@ -21,7 +21,7 @@ To learn more about the differences and similarities see [Aptos Learn](https://l
 | **Example Code**           | [ERC-20](https://github.com/OpenZeppelin/openzeppelin-contracts/tree/master/contracts/token/ERC20)                             | [Fungible Asset](https://github.com/aptos-labs/aptos-core/blob/main/aptos-move/framework/aptos-framework/sources/fungible_asset.move) |
 | **Caller ID**              | `msg.sender`                                                                                                                   | `&signer` reference                                                                                                                   |
 | **Upgradeability**         | Proxy patterns                                                                                                                 | Direct module upgrades                                                                                                                |
-| **Safety & Security**  | Vulnerable to attacks like reentrancy                                                                                          | Mitigates common vulnerabilities                                                                                                      |
+| **Safety & Security**      | Vulnerable to attacks like reentrancy                                                                                          | Mitigates common vulnerabilities                                                                                                      |
 | **Dispatch Type**          | Dynamic dispatch                                                                                                               | Static dispatch                                                                                                                       |
 | **FT Standard**            | [ERC-20](https://docs.openzeppelin.com/contracts/4.x/erc20)                                                                    | [Coin](/build/smart-contracts/aptos-coin) (legacy) and [Fungible Asset](/build/smart-contracts/fungible-asset)                        |
 | **NFT Standards**          | [ERC-721](https://docs.openzeppelin.com/contracts/4.x/erc721), [ERC-1155](https://docs.openzeppelin.com/contracts/4.x/erc1155) | [Digital Asset](/build/smart-contracts/digital-asset)                                                                                 |
@@ -31,11 +31,11 @@ To learn more about the differences and similarities see [Aptos Learn](https://l
 
 ### Comparing Token Standards in Detail
 
-|                        | Solidity                                                               | Move (Aptos)                                                                                                                                                         |
-| ---------------------- | ---------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| **Token Structure**    | Each token is its own contract.                                        | Every token is a typed `Coin` or `FungibleAsset` using a single, reusable contract.                                                                                  |
-| **Token Standard**     | Must conform to standards like ERC20; implementations can vary.        | Uniform interface and implementation for all tokens.                                                                                                                 |
-| **Balance Storage**    | Balances stored in contract using a mapping structure.                 | **Resource-Oriented Balance**: Balances stored as a resource in the user's account. Resources cannot be arbitrarily created, ensuring integrity of token value. |
+|                        | Solidity                                                          | Move (Aptos)                                                                                                                                                    |
+| ---------------------- | ----------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| **Token Structure**    | Each token is its own contract.                                   | Every token is a typed `Coin` or `FungibleAsset` using a single, reusable contract.                                                                             |
+| **Token Standard**     | Must conform to standards like ERC20; implementations can vary.   | Uniform interface and implementation for all tokens.                                                                                                            |
+| **Balance Storage**    | Balances stored in contract using a mapping structure.            | **Resource-Oriented Balance**: Balances stored as a resource in the user's account. Resources cannot be arbitrarily created, ensuring integrity of token value. |
 | **Transfer Mechanism** | Tokens can be transferred without receiver's explicit permission. | Except for specific cases (like AptosCoin), Tokens generally require receiver's `signer` authority for transfer.                                                |
 
 <br />
@@ -49,7 +49,7 @@ To learn more about the differences and similarities see [Aptos Learn](https://l
 
 |                                 | EVM (Ethereum Virtual Machine)                                         | Move VM (Move Virtual Machine)                                                                                     |
 | ------------------------------- | ---------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------ |
-| **Data Storage**                | Data is stored in the smart contract's storage space.             | Data is stored across smart contracts, user accounts, and objects.                                                 |
+| **Data Storage**                | Data is stored in the smart contract's storage space.                  | Data is stored across smart contracts, user accounts, and objects.                                                 |
 | **Parallelization**             | Parallel execution is limited due to shared storage space.             | More parallel execution enabled due to flexible split storage design.                                              |
 | **VM and Language Integration** | Separate layers for EVM and smart contract languages (e.g., Solidity). | Seamless integration between VM layer and Move language, with native functions written in Rust executable in Move. |
 | **Critical Network Operations** | Implementation of network operations can be complex and less direct.   | Critical operations like validator set management natively implemented in Move, allowing for direct execution.     |

src/content/docs/build/guides/aptos-keyless/integration-guide.mdx

@@ -12,7 +12,7 @@ import { Aside, Steps } from '@astrojs/starlight/components';
 
   Use of the \*\*_Aptos Keyless Integration Guide_\*\* will allow for the integration of keyless accounts directly into your application. This means that blockchain accounts are scoped to your application's domain (logging in with your Google account on dApp A and logging in with your Google account on dApp B will create separate accounts). Stay tuned for more to come on Aptos’ plan to allow Keyless accounts to be used portably across applications.
 
-  To provide feedback, get support, or be a design partner as we enhance Aptos Keyless, join us here: https://t.me/+h5CN-W35yUFiYzkx
+  To provide feedback, get support, or be a design partner as we enhance Aptos Keyless, join us here: [https://t.me/+h5CN-W35yUFiYzkx](https://t.me/+h5CN-W35yUFiYzkx)
 </Aside>
 
 At a high level, there are three steps to follow in order to integrate Keyless Accounts.

src/content/docs/build/guides/aptos-keyless/oidc-support.mdx

@@ -54,7 +54,7 @@ To integrate Aptos Keyless into your dApp, you must register your dApp with at l
 
      3. Choose the application type (e.g., Web application, Desktop app, or Mobile app).
 
-     4. Enter the necessary details such as the name of your application and the authorized redirect URIs. For OIDC, the redirect URIs should follow the format https://your-app-domain.com/auth/google/callback.
+     4. Enter the necessary details such as the name of your application and the authorized redirect URIs. For OIDC, the redirect URIs should follow the format [https://your-app-domain.com/auth/google/callback](https://your-app-domain.com/auth/google/callback).
 
      5. Click "Create."
 
@@ -67,7 +67,7 @@ To integrate Aptos Keyless into your dApp, you must register your dApp with at l
 
      1. Integrate OIDC authentication into your application using a suitable OIDC library or framework (e.g., Passport.js for Node.js, Spring Security for Java, or Auth0 for various platforms).
      2. Use the client ID and client secret obtained from Google to configure OIDC authentication in your application settings.
-     3. Set up the appropriate callback URL (https://your-app-domain.com/auth/google/callback) for handling authentication responses from Google.
+     3. Set up the appropriate callback URL ([https://your-app-domain.com/auth/google/callback](https://your-app-domain.com/auth/google/callback)) for handling authentication responses from Google.
 </Steps>
 
 ## Registering your dApp with Apple
@@ -99,12 +99,12 @@ To integrate Aptos Keyless into your dApp, you must register your dApp with at l
 
      1. Under the "App ID" section, locate your newly created App ID and click on it.
      2. Scroll down to the "Sign in with Apple" section and click on "Edit."
-     3. Add the redirect URIs that your application will use for callback after authentication. The format should be https://your-app-domain.com/auth/apple/callback.
+     3. Add the redirect URIs that your application will use for callback after authentication. The format should be [https://your-app-domain.com/auth/apple/callback](https://your-app-domain.com/auth/apple/callback).
      4. Click "Save" to update the settings.
 
   5. Step 5: Set Up Your OIDC Integration
 
      1. Use an OIDC library or framework compatible with Apple's OIDC service (e.g., Passport.js for Node.js, Spring Security for Java).
      2. Configure your application to use the client ID and private key obtained from Apple during the registration process.
-     3. Set up the appropriate callback URL (https://your-app-domain.com/auth/apple/callback) for handling authentication responses from Apple.
+     3. Set up the appropriate callback URL ([https://your-app-domain.com/auth/apple/callback](https://your-app-domain.com/auth/apple/callback)) for handling authentication responses from Apple.
 </Steps>

src/content/docs/build/guides/aptos-keyless/other.mdx

@@ -10,7 +10,7 @@ sidebar:
 - **OpenID Connect (OIDC)**: is the identity authentication protocol used to enable federated identity verification. This protocol is what is used when a user goes through the "Sign in with Google" flow for example.
 - **Identity Provider (IdP)**: is the trusted authority who authenticates your identity via OIDC. Supported example includes: Google.
 - **JSON Web Token (JWT):** is an open standard used to share security information between two parties — a client and a server. Each JWT contains encoded JSON objects, including a set of claims. JWTs are signed using a cryptographic algorithm to ensure that the claims cannot be altered after the token is issued.
-  - `iss`, an identifier for the OIDC provider (e.g., https://accounts.google.com)
+  - `iss`, an identifier for the OIDC provider (e.g., [https://accounts.google.com](https://accounts.google.com))
   - `aud`, the OAuth `client_id` of the application that the user is signing in to (e.g., [Notion.so](https://notion.so))
   - `sub`, an identifier that the OIDC provider uses to identify the user
     - This could be an identifier specific to this `client_id`

src/content/docs/build/guides/exchanges.mdx

@@ -708,7 +708,7 @@ For fungible assets, the balance changes are tracked in the `primary_fungible_st
 The primary fungible store address is deterministic, and will always be tracked by
 the owner of the store.
 
-An example: https://api.mainnet.aptoslabs.com/v1/transactions/by\_version/1750174030
+An example: [https://api.mainnet.aptoslabs.com/v1/transactions/by\\\_version/1750174030](https://api.mainnet.aptoslabs.com/v1/transactions/by\\_version/1750174030)
 
 There are a few steps when tracking fungible assets:
 
@@ -842,7 +842,7 @@ The Fungible asset metadata address is the hash of the coin type and 0xA
 address = sha3_256(0xA | coin_type | 0xFE)
 ```
 
-Here is an example of a migrated coin with APT: https://api.mainnet.aptoslabs.com/v1/transactions/by\_version/1642580695
+Here is an example of a migrated coin with APT: [https://api.mainnet.aptoslabs.com/v1/transactions/by\\\_version/1642580695](https://api.mainnet.aptoslabs.com/v1/transactions/by\\_version/1642580695)
 
 <details>
   <summary>Full response</summary>
@@ -1244,7 +1244,7 @@ the balance is 0.001 APT smaller and minus the gas cost associated.
 
 #### Check Fungible Asset Transfer
 
-To test a transfer, you can fund an account with the fungible asset here https://test-token-faucet.vercel.app/
+To test a transfer, you can fund an account with the fungible asset here [https://test-token-faucet.vercel.app/](https://test-token-faucet.vercel.app/)
 and then transfer the fungible asset to another account.  The balance should be updated
 according to the change, and you should be able to track the mint on the website.