stellar · JFWooten4 · Jun 20, 2024 · Jun 22, 2024 · Jun 23, 2024 · Jun 23, 2024
diff --git a/.husky/pre-commit b/.husky/pre-commit
@@ -1,5 +1,33 @@
+#!/bin/bash
+
+export NVM_DIR="$HOME/.nvm"
+[ -s "$NVM_DIR/nvm.sh" ] && \. "$NVM_DIR/nvm.sh"
+
+if ! nvm use 22 >/dev/null 2>&1; then
+  echo "⚠️  Node v22 not installed. Skipping formatting check."
+  exit 0
+fi
+
 G='\033[0;32m'
 P='\033[0;35m'
 CLEAN='\033[0;0m'
 
-yarn run check:mdx || (echo -e "${G}Hint:${CLEAN} execute ${P}yarn run format:mdx${CLEAN} to format files" && exit 1)
+if command -v yarn >/dev/null 2>&1; then
+  CHECK_OUTPUT=$(yarn run check:mdx 2>&1)
+  STATUS=$?
+
+  if echo "$CHECK_OUTPUT" | grep -q 'The engine "node" is incompatible with this module'; then
+    echo -e "${G}Warning:${CLEAN} Node version mismatch. Skipping formatting check."
+    exit 0
+  fi
+
+  if [ "$STATUS" -ne 0 ]; then
+    echo "$CHECK_OUTPUT"
+    echo -e "${G}Hint:${CLEAN} Run ${P}yarn run format:mdx${CLEAN} to fix formatting."
+    exit 1
+  fi
+
+else
+  echo -e "${G}Hint:${CLEAN} Yarn not installed. Skipping formatting check."
+  exit 0
+fi
diff --git a/.prettierrc.js b/.prettierrc.js
@@ -1,12 +1,10 @@
 module.exports = {
   ...require("@stellar/prettier-config"),
-  // This is mostly content, and prose wrap has a way of exploding markdown
-  // diffs. Override the default for a better experience.
   overrides: [
     {
       files: "*.mdx",
       options: {
-        proseWrap: "never",
+        proseWrap: "never", // Minimize `mdx` diffs with simpler content lines
       },
     },
   ],

diff --git a/docs/build/apps/moneygram-access-integration-guide.mdx b/docs/build/apps/moneygram-access-integration-guide.mdx
@@ -129,7 +129,7 @@ Many cryptocurrency exchanges support purchasing XLM or USDC on Stellar. The SDF
 
 When you’ve purchased XLM and / or USDC on an exchange, you can make a payment to an external account, specifically to the funds public key you generated in the previous step. Note that you will first need to send XLM to create the account, then add a USDC [trustline], then send the USDC. Creating a trustline to USDC can be done using [Stellar Lab] or any Stellar-enabled wallet application, such as [Lobstr].
 
-Some exchanges support XLM but do not support USDC on Stellar. This is not a problem, because you can always sell XLM for USDC on Stellar’s decentralized exchange (or SDEX).
+Some exchanges support XLM but do not support USDC on Stellar. This is not a problem, because you can always sell XLM for USDC on [Stellar’s decentralized exchange](../../learn/encyclopedia/sdex/README.mdx).
 
 To do this, send your XLM to the funds public key from the exchange, add a USDC trustline, and sell XLM for USDC using a [sell offer].
 

diff --git a/docs/build/apps/wallet/sep24.mdx b/docs/build/apps/wallet/sep24.mdx
@@ -11,7 +11,7 @@ import Header from "./component/header.mdx";
 
 <Header />
 
-The [SEP-24] standard defines the standard way for anchors and wallets to interact on behalf of users. Wallets use this standard to facilitate exchanges between on-chain assets (such as stablecoins) and off-chain assets (such as fiat, or other network assets such as BTC).
+The [SEP-24] standard defines the standard way for anchors and wallets to interact on behalf of users. Wallets use this standard to facilitate exchanges between on-chain assets (such as stablecoins) and off-chain assets (such as fiat or other crypto networks).
 
 During the flow, a wallet makes several requests to the anchor, and finally receives an interactive URL to open in iframe. This URL is used by the user to provide an input (such as KYC) directly to the anchor. Finally, the wallet can fetch transaction information using query endpoints.
 

diff --git a/docs/build/apps/wallet/sep6.mdx b/docs/build/apps/wallet/sep6.mdx
@@ -10,7 +10,7 @@ import Header from "./component/header.mdx";
 
 <Header WIPLangs={["kotlin"]} />
 
-The [SEP-6] standard defines a way for anchors and wallets to interact on behalf of users. Wallets use this standard to facilitate exchanges between on-chain assets (such as stablecoins) and off-chain assets (such as fiat, or other network assets such as BTC).
+The [SEP-6] standard defines a way for anchors and wallets to interact on behalf of users. Wallets use this standard to facilitate exchanges between on-chain assets (such as stablecoins) and off-chain assets (such as fiat or other crypto networks).
 
 Please note, this is for _programmatic_ deposits and withdrawals. For hosted deposits and withdrawals, where the anchor interacts with wallets interactively using a popup, please see [Hosted Deposit and Withdrawal](./sep24.mdx).
 

diff --git a/docs/build/guides/storage/use-temporary.mdx b/docs/build/guides/storage/use-temporary.mdx
@@ -4,21 +4,21 @@ hide_table_of_contents: true
 description: Temporary storage is useful for a contract to store data that can quickly become irrelevant or out-dated
 ---
 
-Temporary storage is useful for a contract to store data that can quickly become irrelevant or out-dated. For example, here's how a contract might be used to store a recent price of BTC against the US Dollar.
+Temporary storage is useful for a contract to store data that can quickly become irrelevant or out-dated. For example, here's how a contract might be used to store a recent price of AstroPesos against AstroDollars.
 
 ```rust
-// This function updates the BTC price
-pub fn update_btc_price(env: Env, price: i128) {
-    env.storage().temporary().set(&!symbol_short("BTC"), &price);
+// This function updates the PEN price
+pub fn update_pen_price(env: Env, price: i128) {
+  env.storage().temporary().set(&!symbol_short("PEN"), &price);
 }
 
-// This function reads and returns the current BTC price (zero if the storage
+// This function reads and returns the current PEN price (zero if the storage
 // entry is archived)
-pub fn get_btc_price(env: Env) -> i128 {
-    if let Some(price) = env.storage().temporary().get(&!symbol_short("BTC")) {
-        price
-    } else {
-        0
-    }
+pub fn get_pen_price(env: Env) -> i128 {
+  if let Some(price) = env.storage().temporary().get(&!symbol_short("PEN")) {
+    price
+  } else {
+    0
+  }
 }
 ```
diff --git a/docs/build/guides/tokens/stellar-asset-contract.mdx b/docs/build/guides/tokens/stellar-asset-contract.mdx
@@ -57,7 +57,7 @@ client.mint(...);
 
 ## Testing
 
-Soroban Rust SDK provides an easy way to instantiate a Stellar Asset Contract tokens using `register_stellar_asset_contract_v2`. This function can be seen as the deployment of a generic token. It also allows you to manipulate flags on the issuer account like `AUTH_REVOCABLE` and `AUTH_REQUIRED`. In the following example, we are following the best practices outlined in the [Issuing and Distribution Accounts section](../../../tokens/control-asset-access.mdx#issuing-and-distribution-accounts):
+Soroban Rust SDK provides an easy way to instantiate a Stellar Asset Contract tokens using `register_stellar_asset_contract_v2`. This function can be seen as the deployment of a generic token. It also allows you to manipulate flags on the issuer account like `AUTH_REVOCABLE` and `AUTH_REQUIRED`. In the following example, we are following the best practices outlined in the [Issuing and Distribution Accounts section](../../../tokens/control-asset-access.mdx#issuer-and-distributor-accounts):
 
 ```rust
 #![cfg(test)]

diff --git a/docs/build/smart-contracts/example-contracts/custom-account.mdx b/docs/build/smart-contracts/example-contracts/custom-account.mdx
@@ -26,7 +26,7 @@ Custom accounts are exclusive to Soroban and can't be used to perform other Stel
 
 :::danger
 
-Implementing a custom account contract requires a very good understanding of authentication and authorization and requires rigorous testing and review. The example here is _not_ a full-fledged account contract - use it as an API reference only.
+Implementing a custom account contract requires a very good understanding of authentication and authorization and requires rigorous testing and review. The example here is _not_ a full-fledged account contract; use it as an API reference only.
 
 :::
 

diff --git a/docs/data/analytics/hubble/analyst-guide/queries-for-horizon-like-data.mdx b/docs/data/analytics/hubble/analyst-guide/queries-for-horizon-like-data.mdx
@@ -563,7 +563,7 @@ where true
 
 Offers are statements about how much of an asset an account wants to buy or sell.
 
-Learn more about [offers](../../../../learn/glossary.mdx#decentralized-exchange).
+Learn more about [offers](../../../../learn/glossary.mdx#offers).
 
 ### List All Offers
 

diff --git a/docs/data/apis/horizon/api-reference/aggregations/order-books/README.mdx b/docs/data/apis/horizon/api-reference/aggregations/order-books/README.mdx
@@ -7,9 +7,9 @@ import { EndpointsTable } from "@site/src/components/EndpointsTable";
 
 An order book is a collection of offers for a specific pair of assets.
 
-The [latest ledger](../../structure/consistency.mdx) known to Horizon is included as an HTTP header in the response.
+The response includes the [latest ledger](../../structure/consistency.mdx) known in an HTTP header.
 
-Learn more about [order books](../../../../../../learn/glossary.mdx#decentralized-exchange).
+_See_ [Liquidity on Stellar Encyclopedia Entry: the Unified Orderbook](../../../../../../learn/encyclopedia/sdex/liquidity-on-stellar-sdex-liquidity-pools.mdx#orderbook).
 
 <EndpointsTable title="Endpoints">
 

diff --git a/docs/data/apis/horizon/api-reference/aggregations/order-books/object.mdx b/docs/data/apis/horizon/api-reference/aggregations/order-books/object.mdx
@@ -76,7 +76,7 @@ When Horizon returns information about an order book, it uses the following form
 
 </AttributeTable>
 
-The [latest ledger](../../structure/consistency.mdx) known to Horizon is included as an HTTP header in the response.
+The response includes the [latest ledger](../../structure/consistency.mdx) known in an HTTP header.
 
 <ExampleResponse>
 

diff --git a/docs/data/apis/horizon/api-reference/aggregations/paths/README.mdx b/docs/data/apis/horizon/api-reference/aggregations/paths/README.mdx
@@ -7,9 +7,9 @@ import { EndpointsTable } from "@site/src/components/EndpointsTable";
 
 Paths provide information about potential path payments. A path can be used to populate the necessary fields for a path payment operation.
 
-The [latest ledger](../../structure/consistency.mdx) known to Horizon is included as an HTTP header in the response.
+The HTTP header in the response includes the [latest ledger](../../structure/consistency.mdx) known to Horizon.
 
-Learn more about the two types of path payment: [`path payment strict send`](../../../../../../learn/fundamentals/transactions/list-of-operations.mdx#path-payment-strict-send) and [`path payment strict receive`](../../../../../../learn/fundamentals/transactions/list-of-operations.mdx#path-payment-strict-receive)
+Learn more about path usage: [Path Payments Encyclopedia Entry](../../../../../../learn/encyclopedia/transactions-specialized/path-payments.mdx)
 
 <EndpointsTable title="Endpoints">
 

diff --git a/docs/data/apis/horizon/api-reference/aggregations/paths/object.mdx b/docs/data/apis/horizon/api-reference/aggregations/paths/object.mdx
@@ -52,7 +52,7 @@ When Horizon returns information about a path, it uses the following format:
 
 </AttributeTable>
 
-The [latest ledger](../../structure/consistency.mdx) known to Horizon is included as an HTTP header in the response.
+The response includes the [latest ledger](../../structure/consistency.mdx) known in an HTTP header.
 
 <ExampleResponse>
 

diff --git a/docs/data/apis/horizon/api-reference/errors/README.mdx b/docs/data/apis/horizon/api-reference/errors/README.mdx
@@ -5,15 +5,15 @@ sidebar_position: 40
 
 import { MethodTable } from "@site/src/components/MethodTable";
 
-After processing a request, Horizon returns a success or error response to the client. A success response will return a Status Code of 200, and an error response will return a Status Code in the range of 4XX - 5XX along with additional information about why the request could not complete successfully.
+After processing a request, Horizon returns a success or error response to the client. A success response will return a Status Code of 200, and an error response will return a Status Code in the range of `4XX` – `5XX` along with additional information about why the request could not complete successfully.
 
-There are two categories of errors: [HTTP Status Codes](./http-status-codes/README.mdx) and [Result Codes](./result-codes/README.mdx). Result Codes only follow a Transaction Failed (400) HTTP Status Code.
+There are two categories of errors: [HTTP Status Codes](./http-status-codes/README.mdx) and [Result Codes](./result-codes/README.mdx). Result Codes only follow an HTTP Status Code `400` (Transaction Failed).
 
 <MethodTable title="Error Categories">
 
 |  |  |
 | --- | --- |
-| [HTTP Status Codes](./http-status-codes/README.mdx) | Errors that occur at the Horizon Server level. |
+| [HTTP Status](./http-status-codes/README.mdx) | Errors that occur at the Horizon Server level. |
 | [Result Codes](./result-codes/README.mdx) | Errors that occur at the Stellar Core level. |
 
 </MethodTable>
diff --git a/docs/data/apis/horizon/api-reference/resources/accounts/README.mdx b/docs/data/apis/horizon/api-reference/resources/accounts/README.mdx
@@ -7,7 +7,7 @@ import { EndpointsTable } from "@site/src/components/EndpointsTable";
 
 Users interact with the Stellar network through accounts. Everything else in the ledger—assets, offers, trustlines, etc.—are owned by accounts, and accounts must authorize all changes to the ledger through signed transactions.
 
-The [latest ledger](../../structure/consistency.mdx) known to Horizon is included as an HTTP header in the response.
+The response includes the [latest ledger](../../structure/consistency.mdx) known in an HTTP header.
 
 Learn more about [accounts](../../../../../../learn/glossary.mdx#account).
 

diff --git a/docs/data/apis/horizon/api-reference/resources/accounts/object.mdx b/docs/data/apis/horizon/api-reference/resources/accounts/object.mdx
@@ -133,7 +133,7 @@ When Horizon returns information about an account, it uses the following format:
 
 </AttributeTable>
 
-The [latest ledger](../../structure/consistency.mdx) known to Horizon is included as an HTTP header in the response.
+The response includes the [latest ledger](../../structure/consistency.mdx) known in an HTTP header.
 
 <ExampleResponse>
 

diff --git a/docs/data/apis/horizon/api-reference/resources/assets/README.mdx b/docs/data/apis/horizon/api-reference/resources/assets/README.mdx
@@ -7,7 +7,7 @@ import { EndpointsTable } from "@site/src/components/EndpointsTable";
 
 Assets are representations of value issued on the Stellar network. An asset consists of a type, code, and issuer.
 
-The [latest ledger](../../structure/consistency.mdx) known to Horizon is included as an HTTP header in the response.
+The response includes the [latest ledger](../../structure/consistency.mdx) known in an HTTP header.
 
 Learn more about [assets](../../../../../../learn/glossary.mdx#asset).
 

diff --git a/docs/data/apis/horizon/api-reference/resources/assets/object.mdx b/docs/data/apis/horizon/api-reference/resources/assets/object.mdx
@@ -64,7 +64,7 @@ When Horizon returns information about an asset, it uses the following format:
 
 </AttributeTable>
 
-The [latest ledger](../../structure/consistency.mdx) known to Horizon is included as an HTTP header in the response.
+The response includes the [latest ledger](../../structure/consistency.mdx) known in an HTTP header.
 
 <ExampleResponse>
 

diff --git a/docs/data/apis/horizon/api-reference/resources/claimablebalances/README.mdx b/docs/data/apis/horizon/api-reference/resources/claimablebalances/README.mdx
@@ -7,7 +7,7 @@ import { EndpointsTable } from "@site/src/components/EndpointsTable";
 
 A Claimable Balance represents the transfer of ownership of some amount of an asset. Claimable balances provide a mechanism for setting up a payment which can be claimed in the future. This allows you to make payments to accounts which are currently not able to accept them.
 
-The [latest ledger](../../structure/consistency.mdx) known to Horizon is included as an HTTP header in the response.
+The response includes the [latest ledger](../../structure/consistency.mdx) known in an HTTP header.
 
 <EndpointsTable title="Endpoints">
 

diff --git a/docs/data/apis/horizon/api-reference/resources/claimablebalances/object.mdx b/docs/data/apis/horizon/api-reference/resources/claimablebalances/object.mdx
@@ -67,7 +67,7 @@ When Horizon returns information about a claimable balance, it uses the followin
 
 </AttributeTable>
 
-The [latest ledger](../../structure/consistency.mdx) known to Horizon is included as an HTTP header in the response.
+The response includes the [latest ledger](../../structure/consistency.mdx) known in an HTTP header.
 
 <ExampleResponse>
 

diff --git a/docs/data/apis/horizon/api-reference/resources/liquiditypools/README.mdx b/docs/data/apis/horizon/api-reference/resources/liquiditypools/README.mdx
@@ -5,9 +5,11 @@ order: 0
 
 import { EndpointsTable } from "@site/src/components/EndpointsTable";
 
-Liquidity Pools provide a simple, non-interactive way to trade large amounts of capital and enable high volumes of trading.
+Liquidity Pools provide a simple, non-interactive way to trade large amounts of capital and enable trading high volumes.
 
-The [latest ledger](../../structure/consistency.mdx) known to Horizon is included as an HTTP header in the response.
+The response includes the [latest ledger](../../structure/consistency.mdx) known in an HTTP header.
+
+Learn more about pool participation: [Liquidity on Stellar: Automated Market Making Encyclopedia Entry](../../../../../../learn/encyclopedia/sdex/liquidity-on-stellar-sdex-liquidity-pools.mdx#amms)
 
 <EndpointsTable title="Endpoints">
 

diff --git a/docs/data/apis/horizon/api-reference/resources/offers/README.mdx b/docs/data/apis/horizon/api-reference/resources/offers/README.mdx
@@ -7,9 +7,7 @@ import { EndpointsTable } from "@site/src/components/EndpointsTable";
 
 Offers are statements about how much of an asset an account wants to buy or sell.
 
-The [latest ledger](../../structure/consistency.mdx) known to Horizon is included as an HTTP header in the response.
-
-Learn more about [offers](../../../../../../learn/glossary.mdx#decentralized-exchange).
+The response includes the [latest ledger](../../structure/consistency.mdx) known in an HTTP header.
 
 <EndpointsTable title="Endpoints">
 

diff --git a/docs/data/apis/horizon/api-reference/resources/offers/object.mdx b/docs/data/apis/horizon/api-reference/resources/offers/object.mdx
@@ -55,7 +55,7 @@ When Horizon returns information about an offer, it uses the following format:
 
 </AttributeTable>
 
-The [latest ledger](../../structure/consistency.mdx) known to Horizon is included as an HTTP header in the response.
+The response includes the [latest ledger](../../structure/consistency.mdx) known in an HTTP header.
 
 <ExampleResponse>
 

diff --git a/docs/data/apis/horizon/api-reference/resources/operations/object/buy-offer.mdx b/docs/data/apis/horizon/api-reference/resources/operations/object/buy-offer.mdx
@@ -8,6 +8,8 @@ import { AttributeTable } from "@site/src/components/AttributeTable";
 
 Creates, updates, or deletes a buy offer to trade assets. A buy offer specifies a certain amount of the buying asset that should be sold in exchange for the minimum quantity of the selling asset.
 
+If an entire buy offer isn't fulfilled by existing liquidity, the remaining order volume gets converted to a sell offer representation internally.
+
 See the [`Manage Buy Offer` errors](../../../errors/result-codes/operation-specific/manage-buy-offer.mdx).
 
 <AttributeTable>

diff --git a/docs/data/apis/horizon/api-reference/resources/trades/README.mdx b/docs/data/apis/horizon/api-reference/resources/trades/README.mdx
@@ -7,9 +7,7 @@ import { EndpointsTable } from "@site/src/components/EndpointsTable";
 
 When an offer is fully or partially fulfilled, a trade happens. Trades can also be caused by successful path payments, because path payments involve fulfilling offers.
 
-A trade occurs between two parties—`base` and `counter`. Which is which is either arbitrary or determined by the calling query.
-
-Learn more about [trades](/docs/learn/glossary/#decentralized-exchange).
+A trade occurs between two parties: `base` and `counter`. Name is either arbitrary or determined by the calling query.
 
 <EndpointsTable title="Endpoints">
 

diff --git a/docs/data/apis/horizon/api-reference/retrieve-an-order-book.api.mdx b/docs/data/apis/horizon/api-reference/retrieve-an-order-book.api.mdx
@@ -1,7 +1,7 @@
 ---
 id: retrieve-an-order-book
 title: "Retrieve an Order Book"
-description: "The order book endpoint provides an order book's bids and asks and can be used in [streaming](https://developers.stellar.org/docs/data/apis/horizon/api-reference/structure/streaming) mode."
+description: "The order book endpoint provides an order book's bids and asks and can be used in [streaming](./structure/streaming.mdx) mode."
 sidebar_label: "Retrieve an Order Book"
 hide_title: true
 hide_table_of_contents: true
@@ -36,7 +36,7 @@ import Heading from "@theme/Heading";
 
 
 
-The order book endpoint provides an order book's bids and asks and can be used in [streaming](https://developers.stellar.org/docs/data/apis/horizon/api-reference/structure/streaming) mode.
+The order book endpoint provides an order book's bids and asks and can be used in [streaming](./structure/streaming.mdx) mode.
 
 When filtering for a specific order book, you must use use all six of these arguments: `base_asset_type`, `base_asset_issuer`, `base_asset_code`, `counter_asset_type`, `counter_asset_issuer`, and `counter_asset_code`. If the base or counter asset is XLM, you only need to indicate the asset type as `native` and do not need to designate the code or the issuer.
 

diff --git a/docs/data/apis/horizon/api-reference/structure/pagination/README.mdx b/docs/data/apis/horizon/api-reference/structure/pagination/README.mdx
@@ -13,6 +13,8 @@ Each individual transaction, operation, ledger, etc. is returned as a record, an
 
 To move between pages of a collection of records, use the links in the `next` and `prev` attributes nested under the top-level `_links` attribute.
 
+---
+
 <AttributeTable>
 
 - ATTRIBUTE
@@ -39,7 +41,15 @@ To move between pages of a collection of records, use the links in the `next` an
 
 </AttributeTable>
 
-<CodeExample title="Example Request">
+---
+
+## Larger Queries
+
+For fewer round trips, you can specify the `limit` parameter up to `200` to receive more items in each response. You can also lower it for calls with a smaller scope. Learn more in the [call arguments](./page-arguments.mdx).
+
+## Example Request
+
+<CodeExample>
 
 ```js
 var StellarSdk = require("stellar-sdk");

diff --git a/docs/data/apis/horizon/api-reference/structure/pagination/page-arguments.mdx b/docs/data/apis/horizon/api-reference/structure/pagination/page-arguments.mdx
@@ -29,7 +29,7 @@ import { CodeExample } from "@site/src/components/CodeExample";
   - A designation of the order in which records should appear. Options include `asc`(ascending) or `desc` (descending). If this argument isn’t set, it defaults to `asc`.
 - limit
   - optional
-  - The maximum number of records returned. The limit can range from 1 to 200 - an upper limit that is hardcoded in Horizon for performance reasons. If this argument isn’t designated, it defaults to 10.
+  - The maximum number of records returned. The limit can range from 1 to 200&mdash;an upper limit that is hardcoded in Horizon for performance reasons. If this argument isn’t designated, it defaults to 10.
 
 </AttributeTable>
-Original file line number
+Diff line change
@@ Expand Up @@
     :::danger
-    Implementing a custom account contract requires a very good understanding of authentication and authorization and requires rigorous testing and review. The example here is _not_ a full-fledged account contract - use it as an API reference only.
+    Implementing a custom account contract requires a very good understanding of authentication and authorization and requires rigorous testing and review. The example here is _not_ a full-fledged account contract; use it as an API reference only.
     :::
@@ Expand Down @@