From dc74b49e3526cce952160f8e0937d2cd49307958 Mon Sep 17 00:00:00 2001 From: "mintlify[bot]" <109931778+mintlify[bot]@users.noreply.github.com> Date: Mon, 8 Jun 2026 00:14:14 +0000 Subject: [PATCH] docs: normalize curly quotes to straight quotes in prose --- .../integrating-initia-apps/minitswap.mdx | 2 +- .../vip/whitelist-rollup-for-vip.mdx | 2 +- .../initia-js/transactions/handling-errors.mdx | 2 +- .../vm-specific-tutorials/evm/connect-oracles.mdx | 2 +- .../creating-erc20s/creating-standard-erc20s.mdx | 2 +- .../enshrined-liquidity/introduction.mdx | 2 +- .../opinit-framework/components/challenger.mdx | 2 +- home/core-concepts/minitswap/architecture.mdx | 14 +++++++------- nodes-and-rollups/indexing/rollytics/faq.mdx | 2 +- .../indexing/rollytics/setup-and-migration.mdx | 2 +- user-guides/wallet/auto-signing/introduction.mdx | 2 +- user-guides/wallet/autosign/introduction.mdx | 2 +- .../autosign/using-autosign/enabling-autosign.mdx | 2 +- 13 files changed, 19 insertions(+), 19 deletions(-) diff --git a/developers/developer-guides/integrating-initia-apps/minitswap.mdx b/developers/developer-guides/integrating-initia-apps/minitswap.mdx index 2480dd39..65aca926 100644 --- a/developers/developer-guides/integrating-initia-apps/minitswap.mdx +++ b/developers/developer-guides/integrating-initia-apps/minitswap.mdx @@ -176,7 +176,7 @@ After the 7-day unbonding period, you can withdraw your LP tokens using the `withdraw_unbond` function. This allows you to freely exit your position whenever you'd like and reclaim -your provided liquidity plus any fees you’ve earned along the way. +your provided liquidity plus any fees you've earned along the way. **Move Function Interface:** diff --git a/developers/developer-guides/integrating-initia-apps/vip/whitelist-rollup-for-vip.mdx b/developers/developer-guides/integrating-initia-apps/vip/whitelist-rollup-for-vip.mdx index 93481072..7f568740 100644 --- a/developers/developer-guides/integrating-initia-apps/vip/whitelist-rollup-for-vip.mdx +++ b/developers/developer-guides/integrating-initia-apps/vip/whitelist-rollup-for-vip.mdx @@ -16,7 +16,7 @@ Program (VIP). - Deploy the appropriate VIP scoring contract for your rollup’s VM. + Deploy the appropriate VIP scoring contract for your rollup's VM. - EVM: https://github.com/initia-labs/vip-score-evm - Wasm: https://github.com/initia-labs/vip-score-wasm - Move: https://github.com/initia-labs/vip-score-move diff --git a/developers/developer-guides/tools/sdks/initia-js/transactions/handling-errors.mdx b/developers/developer-guides/tools/sdks/initia-js/transactions/handling-errors.mdx index fc259593..7edc929c 100644 --- a/developers/developer-guides/tools/sdks/initia-js/transactions/handling-errors.mdx +++ b/developers/developer-guides/tools/sdks/initia-js/transactions/handling-errors.mdx @@ -9,4 +9,4 @@ handle them. | -------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------ | | account 'init1...' not found | The account does not exist on the network. | Ensure the account exists on the network. | | failed to execute message; message index: 0: VM aborted: location=0000000000000000000000000000000000000000000000000000000000000001::fungible_asset, code=65540 | The transaction failed to execute due to insufficient funds. | Ensure the account has enough funds to execute the transaction. | -| message": "VM error: status LINKER_ERROR of type Verification with message Cannot find | This may be because the function has not been published on chain or by trying to call an invalid function as the result of either an incorrect account address, module name, or function name. This might not happen locally if the sources are available locally but have yet to be published on-chain. | There are many reasons, but you should check your account addresses, module names, and function names to determine that they’re correct and published. | +| message": "VM error: status LINKER_ERROR of type Verification with message Cannot find | This may be because the function has not been published on chain or by trying to call an invalid function as the result of either an incorrect account address, module name, or function name. This might not happen locally if the sources are available locally but have yet to be published on-chain. | There are many reasons, but you should check your account addresses, module names, and function names to determine that they're correct and published. | diff --git a/developers/developer-guides/vm-specific-tutorials/evm/connect-oracles.mdx b/developers/developer-guides/vm-specific-tutorials/evm/connect-oracles.mdx index 59f9e997..70174925 100644 --- a/developers/developer-guides/vm-specific-tutorials/evm/connect-oracles.mdx +++ b/developers/developer-guides/vm-specific-tutorials/evm/connect-oracles.mdx @@ -262,7 +262,7 @@ Gas Used: 290728 ✅ Sequence #1 on 4303131403034904 | Total Paid: 0. ETH (290728 gas * avg 0 gwei) ``` -To query the `oracle_get_price()` function, use Foundry’s cast call command. +To query the `oracle_get_price()` function, use Foundry's cast call command. ```sh cast call 0x505500221090Cd06400125B4f41A266B89Ffd62e "oracle_get_price()" --rpc-url $JSON_RPC_URL diff --git a/developers/developer-guides/vm-specific-tutorials/evm/creating-erc20s/creating-standard-erc20s.mdx b/developers/developer-guides/vm-specific-tutorials/evm/creating-erc20s/creating-standard-erc20s.mdx index 4ef6cfbd..309349e9 100644 --- a/developers/developer-guides/vm-specific-tutorials/evm/creating-erc20s/creating-standard-erc20s.mdx +++ b/developers/developer-guides/vm-specific-tutorials/evm/creating-erc20s/creating-standard-erc20s.mdx @@ -60,7 +60,7 @@ private key and the deployed ERC20Factory contract address. These values are required for signing transactions and interacting with the MiniEVM. The `ERC20Factory` contract is automatically deployed on all MiniEVM rollups as -part of the chain’s bootstrapping process. +part of the chain's bootstrapping process. To retrieve the deployed factory address, query `{ROLLUP_REST_URL}/minievm/evm/v1/contracts/erc20_factory`. diff --git a/home/core-concepts/enshrined-liquidity/introduction.mdx b/home/core-concepts/enshrined-liquidity/introduction.mdx index 4e34b8ef..3781b4b4 100644 --- a/home/core-concepts/enshrined-liquidity/introduction.mdx +++ b/home/core-concepts/enshrined-liquidity/introduction.mdx @@ -2,7 +2,7 @@ title: Introduction --- -Enshrined Liquidity is Initia’s solution to address some inherent challenges of +Enshrined Liquidity is Initia's solution to address some inherent challenges of the Proof of Stake (PoS) and rollup models. These challenges include: 1. Trade-offs between chain security and liquidity diff --git a/home/core-concepts/interwoven-stack/opinit-framework/components/challenger.mdx b/home/core-concepts/interwoven-stack/opinit-framework/components/challenger.mdx index f3b45b87..c1450146 100644 --- a/home/core-concepts/interwoven-stack/opinit-framework/components/challenger.mdx +++ b/home/core-concepts/interwoven-stack/opinit-framework/components/challenger.mdx @@ -69,7 +69,7 @@ type Deposit struct { submitted to maintain the synchronization between L1 and L2. The Challenger ensures that the OutputRoot of the submitted `MsgProposeOutput` -matches the system’s expectations and that future proposals are made within the +matches the system's expectations and that future proposals are made within the designated timeframe. This process prevents any incorrect or malicious outputs from being finalized, diff --git a/home/core-concepts/minitswap/architecture.mdx b/home/core-concepts/minitswap/architecture.mdx index 318a8991..2e588e17 100644 --- a/home/core-concepts/minitswap/architecture.mdx +++ b/home/core-concepts/minitswap/architecture.mdx @@ -59,7 +59,7 @@ part of the bridging process as shown below. 1. **Initiate Swap on Minitswap DEX**: The user sends a transaction to the Minitswap DEX to swap their $INIT$ tokens into $IbcOpINIT_m$ tokens. -2. **Simulate Swap**: The DEX simulates swapping the user’s $INIT$ tokens into +2. **Simulate Swap**: The DEX simulates swapping the user's $INIT$ tokens into $IbcOpINIT_m$ tokens. 3. **Compare Swap and Direct Bridging**: The DEX compares the simulated amount of $IbcOpINIT_m$ tokens with the amount the user would receive if they @@ -77,12 +77,12 @@ part of the bridging process as shown below. state, updating the state in the process. - **Fee Deduction**: Minitswap deducts a fee based on a predefined value and an additional fee from any extra $IbcOpINIT_m$ that the user receives. - - **Peg Keeper Swap Check**: Once the user’s swap action and fee calculation + - **Peg Keeper Swap Check**: Once the user's swap action and fee calculation are complete, Minitswap checks if a [Peg Keeper Swap](#peg-keeper-swaps) should be performed based on the latest Virtual Pool state. - **Internal Rebalancing Check**: After completing the Peg Keeper Swap, Minitswap checks if [Internal Rebalancing](#internal-rebalancing) is - possible based on the Peg Keeper’s $IbcOpINIT$ balance. If balancing is + possible based on the Peg Keeper's $IbcOpINIT$ balance. If balancing is possible, it is initiated. 6. **Final Outcome**: In both cases, once the OP Bridge or IBC transfer is complete, the user receives the most amount of $OpINIT_m$ tokens in their @@ -117,10 +117,10 @@ expire. the updated state of the Virtual Pool. - **Fee Deduction**: Minitswap deducts a predefined fee amount from the transaction. - - **Internal Rebalancing Check**: After completing the user’s swap + - **Internal Rebalancing Check**: After completing the user's swap transaction, Minitswap checks if [Internal Rebalancing](#internal-rebalancing) is possible based on the Peg - Keeper’s $IbcOpINIT$ balance. If balancing is possible, it is executed to + Keeper's $IbcOpINIT$ balance. If balancing is possible, it is executed to maintain market stability. 4. **Final Outcome**: If the swap is successful, the user receives $INIT$ tokens in their wallet on Initia L1. @@ -136,11 +136,11 @@ serves as an additional method of replenishing the Peg Keeper's $INIT$ balance alongside the [Internal Rebalancing](#internal-rebalancing). The Direct Swap allows any user to directly exchange their $INIT$ tokens for the -Peg Keeper’s $IbcOpINIT$ tokens. This exchange occurs at the average price at +Peg Keeper's $IbcOpINIT$ tokens. This exchange occurs at the average price at which the Peg Keeper purchased $INIT$ tokens. This price could sometimes be lower than what you would get through the traditional swap process. Initially, the Direct Swap might not seem attractive due to the Target Ratio being close to -0.5. However, as the Peg Keeper’s balance of OP-bridged tokens increases, the +0.5. However, as the Peg Keeper's balance of OP-bridged tokens increases, the Direct Swap option becomes more appealing to users. ## Swap Logic diff --git a/nodes-and-rollups/indexing/rollytics/faq.mdx b/nodes-and-rollups/indexing/rollytics/faq.mdx index 580117d5..568ffd67 100644 --- a/nodes-and-rollups/indexing/rollytics/faq.mdx +++ b/nodes-and-rollups/indexing/rollytics/faq.mdx @@ -32,7 +32,7 @@ KV Indexer: Rollytics is the long-term supported indexing solution for Initia rollups. -## Will Services Break If We Don’t Migrate? +## Will Services Break If We Don't Migrate? No immediate breakage is expected, but migration is recommended before production scale. diff --git a/nodes-and-rollups/indexing/rollytics/setup-and-migration.mdx b/nodes-and-rollups/indexing/rollytics/setup-and-migration.mdx index f5ac9576..62f5f0e0 100644 --- a/nodes-and-rollups/indexing/rollytics/setup-and-migration.mdx +++ b/nodes-and-rollups/indexing/rollytics/setup-and-migration.mdx @@ -161,7 +161,7 @@ Validate: ## Step 4: Update Initia Registry -Update your rollup’s registry entry so Initia products use Rollytics: +Update your rollup's registry entry so Initia products use Rollytics: - Modify `apis.indexer` in your `chain.json` - Point it to the Rollytics API endpoint diff --git a/user-guides/wallet/auto-signing/introduction.mdx b/user-guides/wallet/auto-signing/introduction.mdx index 6f38712d..c3502c2d 100644 --- a/user-guides/wallet/auto-signing/introduction.mdx +++ b/user-guides/wallet/auto-signing/introduction.mdx @@ -2,7 +2,7 @@ title: 'Introduction' --- -Auto-signing and Ghost Wallets are Initia’s next evolution in blockchain user +Auto-signing and Ghost Wallets are Initia's next evolution in blockchain user experience, designed to make on-chain actions feel as smooth as browsing the internet. Ghost Wallets function as temporary delegated wallets that allow for auto-signing, where approved on-chain transactions run on behalf of your main diff --git a/user-guides/wallet/autosign/introduction.mdx b/user-guides/wallet/autosign/introduction.mdx index 4d3e44d5..29100163 100644 --- a/user-guides/wallet/autosign/introduction.mdx +++ b/user-guides/wallet/autosign/introduction.mdx @@ -6,7 +6,7 @@ Autosign and Ghost Wallets make onchain actions feel as smooth as browsing the internet. They function as temporary delegated wallets that auto-sign approved onchain transactions on behalf of your primary wallet. -Ghost Wallets use Privy’s embedded wallet infrastructure to eliminate repetitive +Ghost Wallets use Privy's embedded wallet infrastructure to eliminate repetitive signature pop-ups. You maintain full custody of your primary wallet, private keys, and assets while enjoying faster, smoother on-chain interactions across all Initia appchains and supported dApps. diff --git a/user-guides/wallet/autosign/using-autosign/enabling-autosign.mdx b/user-guides/wallet/autosign/using-autosign/enabling-autosign.mdx index d68aa585..e2858ff1 100644 --- a/user-guides/wallet/autosign/using-autosign/enabling-autosign.mdx +++ b/user-guides/wallet/autosign/using-autosign/enabling-autosign.mdx @@ -4,7 +4,7 @@ title: 'Enabling Autosign' On an Autosign-enabled application -1. Click “Connect Wallet” and select your wallet of choice or use the supported +1. Click "Connect Wallet" and select your wallet of choice or use the supported social login options. 2. When prompted, click "Enable auto-signing" 3. This will open a permission window with the following information and