From 63155e2337c45a5f40062b03c30706e1c384fa2d Mon Sep 17 00:00:00 2001
From: "john.xlm" <60260750+JFWooten4@users.noreply.github.com>
Date: Sun, 26 Apr 2026 08:45:19 -0400
Subject: [PATCH 1/2] Remove trailing slashes from Markdown links

---
 .../agentic-payments/mpp/charge-guide.mdx     |  2 +-
 docs/build/agentic-payments/x402/README.mdx   |  2 +-
 .../x402/built-on-stellar.mdx                 |  2 +-
 .../x402/quickstart-guide.mdx                 |  4 ++--
 .../application-design-considerations.mdx     | 12 +++++-----
 .../anchor-integration/sep10.mdx              |  2 +-
 docs/build/apps/guestbook/overview.mdx        |  2 +-
 .../apps/guestbook/passkeys-prerequisites.mdx |  6 ++---
 .../ingest-sdk/ingestion-pipeline-code.mdx    |  2 +-
 docs/build/apps/ingest-sdk/overview.mdx       |  2 +-
 docs/build/apps/privacy.mdx                   |  6 ++---
 docs/build/apps/zk.mdx                        |  4 ++--
 docs/build/building-with-ai.mdx               |  2 +-
 .../create-restoration-footprint-js.mdx       |  2 +-
 .../contract-accounts/advanced-patterns.mdx   |  2 +-
 .../guides/contract-accounts/examples.mdx     |  4 ++--
 .../contract-accounts/smart-wallets.mdx       |  4 ++--
 .../guides/conventions/deploy-contract.mdx    |  2 +-
 .../conventions/upgrading-contracts.mdx       |  2 +-
 docs/build/guides/dapps/docker.mdx            |  2 +-
 docs/build/guides/dapps/initialization.mdx    |  2 +-
 docs/build/guides/dapps/react.mdx             |  2 +-
 .../dapps/soroban-contract-init-template.mdx  |  4 ++--
 .../fees/analyzing-smart-contract-cost.mdx    |  2 +-
 docs/build/guides/freighter/README.mdx        |  2 +-
 .../guides/freighter/prompt-to-sign-tx.mdx    |  2 +-
 docs/build/guides/tokens/deploying-a-sac.mdx  |  2 +-
 .../install-deploy-contract-with-code.mdx     |  2 +-
 .../simulateTransaction-Deep-Dive.mdx         |  2 +-
 .../transactions/upload-wasm-bytecode.mdx     |  6 ++---
 .../securing-web-based-projects.mdx           | 14 +++++------
 .../example-contracts/bls-signature.mdx       |  4 ++--
 .../getting-started/hello-world-frontend.mdx  |  6 ++---
 .../smart-contracts/getting-started/setup.mdx |  4 ++--
 docs/build/smart-contracts/overview.mdx       |  2 +-
 .../analytics-providers.mdx                   | 24 +++++++++----------
 .../hubble/analyst-guide/connecting.mdx       |  4 ++--
 .../connecting-to-bigquery/README.mdx         |  4 ++--
 docs/data/apis/horizon/README.mdx             |  4 ++--
 .../apis/horizon/admin-guide/configuring.mdx  |  4 ++--
 .../admin-guide/ingestion-filtering.mdx       |  2 +-
 .../apis/horizon/admin-guide/ingestion.mdx    |  2 +-
 .../apis/horizon/admin-guide/installing.mdx   |  4 ++--
 .../apis/horizon/admin-guide/monitoring.mdx   |  6 ++---
 docs/data/apis/horizon/providers.mdx          |  6 ++---
 .../data/apis/rpc/admin-guide/configuring.mdx |  4 ++--
 docs/data/apis/rpc/admin-guide/monitoring.mdx |  4 ++--
 .../rpc/api-reference/methods/getEvents.mdx   |  2 +-
 .../rpc/api-reference/methods/getFeeStats.mdx |  2 +-
 .../rpc/api-reference/methods/getHealth.mdx   |  2 +-
 .../api-reference/methods/getLatestLedger.mdx |  2 +-
 .../rpc/api-reference/methods/getLedgers.mdx  |  2 +-
 .../rpc/api-reference/methods/getNetwork.mdx  |  2 +-
 .../api-reference/methods/getTransaction.mdx  |  2 +-
 .../api-reference/methods/getTransactions.mdx |  2 +-
 docs/data/apis/rpc/providers.mdx              | 24 +++++++++----------
 docs/data/indexers/README.mdx                 |  2 +-
 .../galexie/admin_guide/installing.mdx        |  2 +-
 .../galexie/admin_guide/monitoring.mdx        |  2 +-
 .../galexie/admin_guide/prerequisites.mdx     |  2 +-
 .../galexie/admin_guide/setup.mdx             |  2 +-
 .../build-your-own/galexie/providers.mdx      |  4 ++--
 docs/data/oracles/oracle-providers.mdx        | 12 +++++-----
 .../stellar-transaction.mdx                   |  2 +-
 .../contract-interactions/tests.mdx           |  2 +-
 .../transaction-simulation.mdx                |  2 +-
 .../errors-and-debugging/debugging.mdx        |  2 +-
 .../contract-development/rust-dialect.mdx     |  2 +-
 .../types/fully-typed-contracts.mdx           |  2 +-
 docs/learn/fundamentals/data-format/xdr.mdx   |  2 +-
 docs/learn/fundamentals/lumens.mdx            |  4 ++--
 .../transactions/signatures-multisig.mdx      |  2 +-
 .../migrate/evm/smart-contract-deployment.mdx |  2 +-
 .../migrate/evm/solidity-and-rust-basics.mdx  |  2 +-
 docs/networks/README.mdx                      |  2 +-
 docs/networks/resource-limits-fees.mdx        |  2 +-
 .../api-reference/platform/rpc/overview.mdx   |  2 +-
 .../sep24/setting-up-production-server.mdx    |  2 +-
 .../admin-guide/deploy-the-sdp.mdx            |  2 +-
 .../admin-guide/embedded-wallets.mdx          | 10 ++++----
 .../admin-guide/getting-started.mdx           |  4 ++--
 .../admin-guide/monitoring.mdx                |  2 +-
 .../admin-guide/troubleshooting.mdx           |  4 ++--
 .../create-direct-payment.api.mdx             |  2 +-
 .../list-all-disbursement-receivers.api.mdx   |  2 +-
 .../api-reference/list-all-payments.api.mdx   |  2 +-
 .../api-reference/retrieve-a-payment.api.mdx  |  2 +-
 docs/tokens/README.mdx                        |  2 +-
 docs/tokens/anatomy-of-an-asset.mdx           |  2 +-
 docs/tokens/publishing-asset-info.mdx         |  2 +-
 .../developer-tools/analytics-platforms.mdx   |  2 +-
 docs/tools/developer-tools/anchor-tools.mdx   |  4 ++--
 .../tools/developer-tools/block-explorers.mdx |  4 ++--
 .../developer-tools/network-insights.mdx      |  2 +-
 docs/tools/developer-tools/network-status.mdx |  6 ++---
 docs/tools/developer-tools/online-ide.mdx     |  2 +-
 docs/tools/developer-tools/security-tools.mdx |  4 ++--
 docs/tools/developer-tools/wallets.mdx        | 12 +++++-----
 docs/tools/infra-tools/cross-chain.mdx        |  6 ++---
 docs/tools/lab/quickstart-with-lab.mdx        |  2 +-
 .../upload-deploy-contract.mdx                |  2 +-
 docs/tools/openzeppelin-contracts.mdx         |  6 ++---
 .../quickstart/advanced-usage/container.mdx   |  2 +-
 .../quickstart/getting-started/README.mdx     |  2 +-
 docs/tools/ramps/README.mdx                   |  2 +-
 docs/tools/scaffold-stellar.mdx               |  4 ++--
 docs/tools/sdks/client-sdks.mdx               | 10 ++++----
 docs/tools/sdks/contract-sdks.mdx             |  4 ++--
 docs/validators/admin-guide/monitoring.mdx    |  6 ++---
 docs/validators/admin-guide/prerequisites.mdx |  4 ++--
 static/llms.txt                               | 20 ++++++++--------
 111 files changed, 215 insertions(+), 215 deletions(-)

diff --git a/docs/build/agentic-payments/mpp/charge-guide.mdx b/docs/build/agentic-payments/mpp/charge-guide.mdx
index cc57237914..785bf389d3 100644
--- a/docs/build/agentic-payments/mpp/charge-guide.mdx
+++ b/docs/build/agentic-payments/mpp/charge-guide.mdx
@@ -49,7 +49,7 @@ In **pull** mode (default), the client builds and signs the full transaction env
 
 This tutorial walks through building a payment-gated API with Node.js and Express using `@stellar/mpp`.
 
-To follow this guide, you will need [Node.js](https://nodejs.org/) installed locally. Recommend using the latest LTS version.
+To follow this guide, you will need [Node.js](https://nodejs.org) installed locally. Recommend using the latest LTS version.
 
 ## Create a project
 
diff --git a/docs/build/agentic-payments/x402/README.mdx b/docs/build/agentic-payments/x402/README.mdx
index 0126f2140e..821c60eed2 100644
--- a/docs/build/agentic-payments/x402/README.mdx
+++ b/docs/build/agentic-payments/x402/README.mdx
@@ -114,7 +114,7 @@ This version supports x402 v2 specification. For x402 v1 support, please use a p
 - [x402 on Stellar (Landing page)](https://stellar.org/x402) — Stellar x402 overview and resources
 - [x402 on Stellar (Blog)](https://stellar.org/blog/foundation-news/x402-on-stellar) — Foundation news and announcement
 - [x402 protocol (Coinbase Developer Platform)](https://docs.cdp.coinbase.com/x402) — Official x402 protocol overview and spec
-- [x402 protocol specification](https://www.x402.org/) — x402 Specification and Whitepaper
+- [x402 protocol specification](https://www.x402.org) — x402 Specification and Whitepaper
 - [Coinbase x402 GitHub](https://github.com/coinbase/x402) — Official x402 Protocol GitHub Repo
 - [x402-stellar (npm)](https://www.npmjs.com/package/x402-stellar) — npm package for x402 on Stellar
 - [Signing Soroban invocations](../../guides/transactions/signing-soroban-invocations.mdx) — Auth-entry signing and transaction signing on Stellar
diff --git a/docs/build/agentic-payments/x402/built-on-stellar.mdx b/docs/build/agentic-payments/x402/built-on-stellar.mdx
index cc9f0ded74..21acb6b4d6 100644
--- a/docs/build/agentic-payments/x402/built-on-stellar.mdx
+++ b/docs/build/agentic-payments/x402/built-on-stellar.mdx
@@ -183,7 +183,7 @@ If you want to run your own instance of the facilitator instead of using the hos
 - [@x402/stellar (npm)](https://www.npmjs.com/package/@x402/stellar) — npm package for x402 on Stellar
 - [x402-stellar (repo)](https://github.com/stellar/x402-stellar) — Tools, examples, and references for x402 on Stellar
 - [x402 on Stellar](./README.mdx) — Overview of the x402 protocol on Stellar
-- [x402 protocol specification](https://www.x402.org/) — x402 specification and whitepaper
+- [x402 protocol specification](https://www.x402.org) — x402 specification and whitepaper
 - [OpenZeppelin x402 Facilitator Plugin][oz-plugin] — Source code
 - [OpenZeppelin x402 Facilitator Docs][oz-facilitator-guide] — Full configuration and setup guide
 - [OpenZeppelin Stellar Relayer SDK](https://github.com/OpenZeppelin/openzeppelin-relayer-sdk) — SDK for interacting with the Relayer
diff --git a/docs/build/agentic-payments/x402/quickstart-guide.mdx b/docs/build/agentic-payments/x402/quickstart-guide.mdx
index 45b7ecff39..2782e04d27 100644
--- a/docs/build/agentic-payments/x402/quickstart-guide.mdx
+++ b/docs/build/agentic-payments/x402/quickstart-guide.mdx
@@ -7,7 +7,7 @@ keywords: [x402, x402 quickstart, x402 tutorial, 402]
 
 This tutorial shows how to build the simplest possible paid API with Node.js and Express using the x402 packages with settlement on the Stellar network.
 
-To follow this guide, you will need [Node.js](https://nodejs.org/) installed locally. Recommend using the latest LTS version.
+To follow this guide, you will need [Node.js](https://nodejs.org) installed locally. Recommend using the latest LTS version.
 
 ## Create A Project
 
@@ -317,7 +317,7 @@ The server is set up as an MVP for machine-to-machine payments. If you want to e
 - [x402 on Stellar (Landing page)](https://stellar.org/x402) - Stellar x402 overview and resources
 - [x402 on Stellar (Blog)](https://stellar.org/blog/foundation-news/x402-on-stellar) - Foundation news and announcement
 - [x402 protocol (Coinbase Developer Platform)](https://docs.cdp.coinbase.com/x402) - Official x402 protocol overview and spec
-- [x402 protocol specification](https://www.x402.org/) - x402 Specification and Whitepaper
+- [x402 protocol specification](https://www.x402.org) - x402 Specification and Whitepaper
 - [Coinbase x402 GitHub](https://github.com/coinbase/x402) - Official x402 Protocol GitHub Repo
 - [x402-stellar (npm)](https://www.npmjs.com/package/x402-stellar) - npm package for x402 on Stellar
 - [Signing Soroban invocations](../../guides/transactions/signing-soroban-invocations.mdx) - Auth-entry signing and transaction signing on Stellar
diff --git a/docs/build/apps/application-design-considerations.mdx b/docs/build/apps/application-design-considerations.mdx
index 8ee0355321..f9e55f90c5 100644
--- a/docs/build/apps/application-design-considerations.mdx
+++ b/docs/build/apps/application-design-considerations.mdx
@@ -34,10 +34,10 @@ Building an application with [multi-signature](../../learn/fundamentals/transact
 
 There are several apps and services that specialize in adding additional security layers to users' accounts. Check them out if you're interested in integrating a third-party key management service:
 
-- [Ledger](https://www.ledger.com/)
-- [Trezor](https://trezor.io/)
-- [StellarGuard](https://stellarguard.me/)
-- [LobstrVault](https://vault.lobstr.co/)
+- [Ledger](https://www.ledger.com)
+- [Trezor](https://trezor.io)
+- [StellarGuard](https://stellarguard.me)
+- [LobstrVault](https://vault.lobstr.co)
 
 ## Application security
 
@@ -49,8 +49,8 @@ For more information, check out our guide to [securing web-based products](https
 
 A wallet typically has these basic functions: key storage, account creation, transaction signing, and queries to the Stellar database. There are some services that take care of all of these functions for you, so you can build whatever you’d like around it. Check out some of these wallet services below.
 
-- [Albedo](https://albedo.link/)
-- [Freighter](https://www.freighter.app/)
+- [Albedo](https://albedo.link)
+- [Freighter](https://www.freighter.app)
 
 ## Account creation strategies
 
diff --git a/docs/build/apps/example-application-tutorial/anchor-integration/sep10.mdx b/docs/build/apps/example-application-tutorial/anchor-integration/sep10.mdx
index ebe458603a..304422ae42 100644
--- a/docs/build/apps/example-application-tutorial/anchor-integration/sep10.mdx
+++ b/docs/build/apps/example-application-tutorial/anchor-integration/sep10.mdx
@@ -194,7 +194,7 @@ function validateChallengeTransaction({
 
 ## Sign and submit the challenge transaction
 
-In response, the user signs the transaction. You may have noticed we present this challenge transaction to the user with our regular confirmation modal. Once they've signed the transaction, the application sends it back to the anchor with a `POST` request. If the signature checks out, the success response will contain a [JSON Web Token (JWT)](https://jwt.io/), which BasicPay stores in the `webAuthStore` store to use for future interactions with the anchor.
+In response, the user signs the transaction. You may have noticed we present this challenge transaction to the user with our regular confirmation modal. Once they've signed the transaction, the application sends it back to the anchor with a `POST` request. If the signature checks out, the success response will contain a [JSON Web Token (JWT)](https://jwt.io), which BasicPay stores in the `webAuthStore` store to use for future interactions with the anchor.
 
 ```html title=/src/routes/dashboard/transfers/+page.svelte
 <script>
diff --git a/docs/build/apps/guestbook/overview.mdx b/docs/build/apps/guestbook/overview.mdx
index 741ef5116f..75ff78d203 100644
--- a/docs/build/apps/guestbook/overview.mdx
+++ b/docs/build/apps/guestbook/overview.mdx
@@ -22,7 +22,7 @@ Although Ye Olde Guestbook is a full-fledged application on Stellar's Testnet, i
 To build this guestbook application, we'll need a few pieces.
 
 - **Application framework:** we're using SvelteKit, opting for a type-checked project using TypeScript. SvelteKit (and Svelte on its own) is quite a capable framework, and we'll be using some of its features in this project. However, we will not be diving into those Svelte-specific areas very heavily in this tutorial. The source code of the project is freely open and available and has some decent informational comments throughout if you would like to peruse it for those purposes.
-- **Frontend framework:** We're using [Skeleton](https://www.skeleton.dev/) to simplify the use of [Tailwind CSS](https://tailwindcss.com/).
+- **Frontend framework:** We're using [Skeleton](https://www.skeleton.dev) to simplify the use of [Tailwind CSS](https://tailwindcss.com).
 - **A way to interact with the network:** this is a TypeScript application, and we're using the `@stellar/stellar-sdk` for this. You could make traditional `fetch` requests if you wanted to, depending on your deployment decisions. In either case, we'll need the SDK to interact with keypairs and transactions. We'll also be using a data indexer to access historical network events, and we'll cover more of this at a later point in the tutorial.
 - **A way to interact with a user's account:** we're foregoing the traditional wallets here, and we'll use `passkey-kit` to give our users a smart wallet to interact with. They can interact with this smart wallet (via passkey-kit) through methods they're already familiar with (thumbprints, face ID, etc.).
 
diff --git a/docs/build/apps/guestbook/passkeys-prerequisites.mdx b/docs/build/apps/guestbook/passkeys-prerequisites.mdx
index f02b11911d..9bf206cccc 100644
--- a/docs/build/apps/guestbook/passkeys-prerequisites.mdx
+++ b/docs/build/apps/guestbook/passkeys-prerequisites.mdx
@@ -35,7 +35,7 @@ The `PRIVATE_` and `PUBLIC_` environment variables are a SvelteKit convention, a
 
 ## Mercury
 
-Now, on to [Mercury](https://www.mercurydata.app/). This is a data indexer, running on both Testnet and Mainnet. The team is developing some bleeding-edge data tools that are beginning to redefine what's possible with network data. One such development is the [ZephyrVM](https://docs.mercurydata.app/zephyr-full-customization/introduction): Mercury's cloud execution environment. In short, Zephyr allows you to write (Rust) programs that will run at the close of _every_ ledger on the Stellar network. Inside that program, you can access any kind of current or past data, interact with external web services, create serverless functions, and populate databases. Similar to Launchtube, we won't be _directly_ interacting with Mercury inside the Ye Olde Guestbook dapp. Those interactions will be handled by the `passkey-kit` package. Also similar to Launchtube, this one takes some setting up.
+Now, on to [Mercury](https://www.mercurydata.app). This is a data indexer, running on both Testnet and Mainnet. The team is developing some bleeding-edge data tools that are beginning to redefine what's possible with network data. One such development is the [ZephyrVM](https://docs.mercurydata.app/zephyr-full-customization/introduction): Mercury's cloud execution environment. In short, Zephyr allows you to write (Rust) programs that will run at the close of _every_ ledger on the Stellar network. Inside that program, you can access any kind of current or past data, interact with external web services, create serverless functions, and populate databases. Similar to Launchtube, we won't be _directly_ interacting with Mercury inside the Ye Olde Guestbook dapp. Those interactions will be handled by the `passkey-kit` package. Also similar to Launchtube, this one takes some setting up.
 
 The `passkey-kit` package doesn't "ship" with a Zephyr program in the published package, but it _does_ have all the Zephyr goodness you'll need in the source repository. Here's how you get that Zephyr program running on Mercury so you can access the indexed smart wallet events. By the way, these commands are probably best run _outside_ the directory where you're building your guestbook dapp.
 
@@ -46,7 +46,7 @@ The `passkey-kit` package doesn't "ship" with a Zephyr program in the published
    cd passkey-kit/zephyr
    ```
 
-2. Get an authentication token from the Mercury website. You can login to the [Testnet dashboard](https://test.mercurydata.app/) here. Click on the **Get access token** button under the "Active subscriptions" section. You'll be given a JWT which will be valid for the next seven days.
+2. Get an authentication token from the Mercury website. You can login to the [Testnet dashboard](https://test.mercurydata.app) here. Click on the **Get access token** button under the "Active subscriptions" section. You'll be given a JWT which will be valid for the next seven days.
 
    ![Mercury Data JWT Token](/assets/guestbook/mercury_token.png)
 
@@ -90,6 +90,6 @@ It's possible something has gone wrong during your execution of the processes ab
 
 1. **Generate a new Launchtube token.** It's possible the Launchtube token you're using has run out of credits. Since we're using Testnet for this tutorial, there's no harm in generating a brand new token any time by visiting `https://testnet.launchtube.xyz/gen` in your browser.
 2. **Make sure your Zephyr program successfully deployed.** I've been stuck more than once with a not-working Mercury request because the Zephyr program hadn't actually deployed successfully. Make sure the `mercury-cli deploy` command's output doesn't have any errors in it.
-3. **Check the [Mercury documentation](https://docs.mercurydata.app/).** It's quite good and can help you get past a lot of the hurdles you might face.
+3. **Check the [Mercury documentation](https://docs.mercurydata.app).** It's quite good and can help you get past a lot of the hurdles you might face.
 
 In any case, feel free to ask questions or drop a chat in the [`#passkeys`](https://discord.com/channels/897514728459468821/1250851135561142423) and [`#launchtube`](https://discord.com/channels/897514728459468821/1293204627361108141) channels in the Stellar Developer Discord server. There's usually somebody around who's ready and willing to help out!
diff --git a/docs/build/apps/ingest-sdk/ingestion-pipeline-code.mdx b/docs/build/apps/ingest-sdk/ingestion-pipeline-code.mdx
index e687bf6357..3e426423e9 100644
--- a/docs/build/apps/ingest-sdk/ingestion-pipeline-code.mdx
+++ b/docs/build/apps/ingest-sdk/ingestion-pipeline-code.mdx
@@ -232,7 +232,7 @@ func main() {
 
 ### `config.toml`
 
-The CDP configuration settings, this file defines the data storage which contains the pre-generated Ledger Metadata files. The [S3 Public Blockchain](https://registry.opendata.aws/aws-public-blockchain/) bucket for [Stellar Pubnet](hhttps://aws-public-blockchain.s3.us-east-2.amazonaws.com/index.html#v1.1/stellar/ledgers/pubnet/) is used in this example.
+The CDP configuration settings, this file defines the data storage which contains the pre-generated Ledger Metadata files. The [S3 Public Blockchain](https://registry.opendata.aws/aws-public-blockchain) bucket for [Stellar Pubnet](hhttps://aws-public-blockchain.s3.us-east-2.amazonaws.com/index.html#v1.1/stellar/ledgers/pubnet) is used in this example.
 
 <CodeExample>
 
diff --git a/docs/build/apps/ingest-sdk/overview.mdx b/docs/build/apps/ingest-sdk/overview.mdx
index a7438616d6..2e3088772c 100644
--- a/docs/build/apps/ingest-sdk/overview.mdx
+++ b/docs/build/apps/ingest-sdk/overview.mdx
@@ -19,7 +19,7 @@ This tutorial walks through how an application can leverage [CDP architecture](h
 
 To use this example CDP pipeline for live Stellar network transaction data, you'll need:
 
-- A developer workstation with [Go](https://go.dev/learn/) programming language runtime installed
+- A developer workstation with [Go](https://go.dev/learn) programming language runtime installed
 - An IDE to edit Go code, [VSCode](https://code.visualstudio.com/download) is good if one is needed
 - A newly initialized, empty Go project folder. `mkdir pipeline; cd pipeline; go mod init example/pipeline`
 - Some familiarity to the [Stellar Ledger Metadata model](../../../learn/fundamentals/stellar-data-structures/README.mdx). It is defined in an IDL format expressed in [XDR encoding](https://github.com/stellar/stellar-xdr).
diff --git a/docs/build/apps/privacy.mdx b/docs/build/apps/privacy.mdx
index b57bde36f8..5872ed5398 100644
--- a/docs/build/apps/privacy.mdx
+++ b/docs/build/apps/privacy.mdx
@@ -37,7 +37,7 @@ Research prototype, not audited. Do not use in production with real assets.
 Proofs are generated client-side in the browser via WebAssembly — user secrets never leave the device.
 
 - **Repo**: [NethermindEth/stellar-private-payments](https://github.com/NethermindEth/stellar-private-payments)
-- **Docs**: [nethermindeth.github.io/stellar-private-payments](https://nethermindeth.github.io/stellar-private-payments/)
+- **Docs**: [nethermindeth.github.io/stellar-private-payments](https://nethermindeth.github.io/stellar-private-payments)
 
 ## Confidential Tokens
 
@@ -45,9 +45,9 @@ Confidential Tokens let users keep token balances and transaction amounts privat
 
 This makes confidential tokens well-suited for payments where parties need confidentiality without sacrificing public auditability.
 
-The [Confidential Token Association](https://www.confidentialtoken.org/) — whose members include the Stellar Development Foundation, Nethermind, OpenZeppelin, and Zama — is developing an open standard for encryption-based onchain confidentiality compatible with existing token interfaces. Implementation on Stellar is in progress.
+The [Confidential Token Association](https://www.confidentialtoken.org) — whose members include the Stellar Development Foundation, Nethermind, OpenZeppelin, and Zama — is developing an open standard for encryption-based onchain confidentiality compatible with existing token interfaces. Implementation on Stellar is in progress.
 
-- **Website**: [confidentialtoken.org](https://www.confidentialtoken.org/)
+- **Website**: [confidentialtoken.org](https://www.confidentialtoken.org)
 - **Overview/demo video**: [youtube.com/watch?v=6NnDqVQYOHM](https://www.youtube.com/watch?v=6NnDqVQYOHM)
 
 ## Onchain ZK Verifiers
diff --git a/docs/build/apps/zk.mdx b/docs/build/apps/zk.mdx
index 1ea2cb3a4f..821ac4b260 100644
--- a/docs/build/apps/zk.mdx
+++ b/docs/build/apps/zk.mdx
@@ -25,8 +25,8 @@ While BN254 host functions provide the cryptographic operations needed for proof
 - [Soroban SDK BN254 documentation - types and functions](https://docs.rs/soroban-sdk/latest/soroban_sdk/_migrating/v25_bn254/index.html)
 - [CAP-74 proposal](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0074.md)
 - [Noir Ultrahonk Soroban Verifier Contract](https://github.com/indextree/ultrahonk_soroban_contract)
-- [Noir documentation (circuits)](https://noir-lang.org/docs/)
-- [Risc0 documentation (circuits)](https://dev.risczero.com/)
+- [Noir documentation (circuits)](https://noir-lang.org/docs)
+- [Risc0 documentation (circuits)](https://dev.risczero.com)
 
 ## Poseidon
 
diff --git a/docs/build/building-with-ai.mdx b/docs/build/building-with-ai.mdx
index 1728c37b30..f47be843c2 100644
--- a/docs/build/building-with-ai.mdx
+++ b/docs/build/building-with-ai.mdx
@@ -32,7 +32,7 @@ The skill can be installed on any AI coding tool that supports the [Agent Skills
 | --- | --- |
 | [Claude Code](https://docs.anthropic.com/en/docs/claude-code) | `~/.claude/skills/` |
 | [OpenCode](https://opencode.ai) | `~/.config/opencode/skills/` |
-| [OpenAI Codex](https://openai.com/index/openai-codex/) | `~/.codex/skills/` |
+| [OpenAI Codex](https://openai.com/index/openai-codex) | `~/.codex/skills/` |
 
 ### Installation
 
diff --git a/docs/build/guides/archival/create-restoration-footprint-js.mdx b/docs/build/guides/archival/create-restoration-footprint-js.mdx
index 514da1a331..3b06bd5f3b 100644
--- a/docs/build/guides/archival/create-restoration-footprint-js.mdx
+++ b/docs/build/guides/archival/create-restoration-footprint-js.mdx
@@ -87,7 +87,7 @@ async function createRestorationFootprint(
 
 ## Code walkthrough
 
-As we're making use of [Stellar SDK for JavaScript](https://stellar.github.io/js-stellar-sdk/) `js-stellar-sdk`, first we import the module.
+As we're making use of [Stellar SDK for JavaScript](https://stellar.github.io/js-stellar-sdk) `js-stellar-sdk`, first we import the module.
 
 Our function will require the following parameters:
 
diff --git a/docs/build/guides/contract-accounts/advanced-patterns.mdx b/docs/build/guides/contract-accounts/advanced-patterns.mdx
index 7bcc064d2b..e8fc4fd586 100644
--- a/docs/build/guides/contract-accounts/advanced-patterns.mdx
+++ b/docs/build/guides/contract-accounts/advanced-patterns.mdx
@@ -45,5 +45,5 @@ See the [Complex Account example](../../smart-contracts/example-contracts/comple
 
 - See these patterns applied in the [contract account examples](./examples.mdx).
 - Explore reference implementations and libraries:
-  - [OpenZeppelin Stellar contracts](https://github.com/OpenZeppelin/stellar-contracts/)
+  - [OpenZeppelin Stellar contracts](https://github.com/OpenZeppelin/stellar-contracts)
   - [Crossmint smart account](https://github.com/Crossmint/stellar-smart-account)
diff --git a/docs/build/guides/contract-accounts/examples.mdx b/docs/build/guides/contract-accounts/examples.mdx
index b2f215f3f0..3da9a45dc9 100644
--- a/docs/build/guides/contract-accounts/examples.mdx
+++ b/docs/build/guides/contract-accounts/examples.mdx
@@ -24,7 +24,7 @@ A smart wallet that demonstrates the use of multi-sig and policy signers to, sur
 
 An app that uses passkeys to sign Stellar smart contract transactions.
 
-- View the [demo](https://passkey.sorobanbyexample.org/)
+- View the [demo](https://passkey.sorobanbyexample.org)
 - View the [code](https://github.com/kalepail/soroban-passkey)
 - Watch the [demo video](https://www.youtube.com/watch?v=y38_O4oIvbY)
 - Watch the [discussion](/meetings/2024/05/09)
@@ -34,7 +34,7 @@ An app that uses passkeys to sign Stellar smart contract transactions.
 
 A passkey-powered multi-signer abstract account contract example.
 
-- View the [demo](https://superpeach.xyz/)
+- View the [demo](https://superpeach.xyz)
 - View the [code](https://github.com/kalepail/superpeach)
 - Watch the [demo video](https://youtu.be/0Agiwso2OMc?si=CHD9U8s-YLyqbXUJ)
 
diff --git a/docs/build/guides/contract-accounts/smart-wallets.mdx b/docs/build/guides/contract-accounts/smart-wallets.mdx
index 02c9684790..966db466ae 100644
--- a/docs/build/guides/contract-accounts/smart-wallets.mdx
+++ b/docs/build/guides/contract-accounts/smart-wallets.mdx
@@ -13,7 +13,7 @@ Smart wallets are contract accounts that act as user wallets. They hold assets a
 
 ## WebAuthn
 
-[WebAuthn](https://www.w3.org/TR/webauthn/) is a browser standard for passwordless authentication using public key cryptography. A device creates a keypair and proves possession with a challenge/response flow. Keys stay on the device or synced across devices through cloud providers.
+[WebAuthn](https://www.w3.org/TR/webauthn) is a browser standard for passwordless authentication using public key cryptography. A device creates a keypair and proves possession with a challenge/response flow. Keys stay on the device or synced across devices through cloud providers.
 
 Benefits:
 
@@ -41,7 +41,7 @@ Benefits:
 ## Tooling
 
 - **Passkey Kit**: TypeScript SDK for creating contract accounts and signing with passkeys.
-  - Demo: [passkey-kit-demo.pages.dev](https://passkey-kit-demo.pages.dev/)
+  - Demo: [passkey-kit-demo.pages.dev](https://passkey-kit-demo.pages.dev)
   - Code: [github.com/kalepail/passkey-kit](https://github.com/kalepail/passkey-kit)
 - **Launchtube**: relay for submitting transactions and handling fees/sequence numbers.
   - Code: [github.com/stellar/launchtube](https://github.com/stellar/launchtube)
diff --git a/docs/build/guides/conventions/deploy-contract.mdx b/docs/build/guides/conventions/deploy-contract.mdx
index 2c811fa6c5..af26902492 100644
--- a/docs/build/guides/conventions/deploy-contract.mdx
+++ b/docs/build/guides/conventions/deploy-contract.mdx
@@ -24,7 +24,7 @@ This guide walks through the process of deploying a smart contract from installe
 
 ### Prerequisites:
 
-- Basic understanding of [Rust programming language](https://www.rust-lang.org/). To brush up on Rust, check out [Rustlings](https://github.com/rust-lang/rustlings) or [The Rust book](https://doc.rust-lang.org/book/).
+- Basic understanding of [Rust programming language](https://www.rust-lang.org). To brush up on Rust, check out [Rustlings](https://github.com/rust-lang/rustlings) or [The Rust book](https://doc.rust-lang.org/book).
 - Familiarity with [Stellar smart contracts](../../smart-contracts/getting-started/hello-world.mdx)
 - Installed Cargo, [Stellar CLI](../../smart-contracts/getting-started/setup.mdx#install-the-stellar-cli) and Soroban SDK
 
diff --git a/docs/build/guides/conventions/upgrading-contracts.mdx b/docs/build/guides/conventions/upgrading-contracts.mdx
index 120877bad6..b95e8a1a0d 100644
--- a/docs/build/guides/conventions/upgrading-contracts.mdx
+++ b/docs/build/guides/conventions/upgrading-contracts.mdx
@@ -22,7 +22,7 @@ Upgrading a smart contract allows you to improve or modify your contract without
 
 ### Prerequisites:
 
-- Basic understanding of the [Rust programming language]. To brush up on Rust, check out [Rustlings](https://github.com/rust-lang/rustlings) or [The Rust book](https://doc.rust-lang.org/book/).
+- Basic understanding of the [Rust programming language]. To brush up on Rust, check out [Rustlings](https://github.com/rust-lang/rustlings) or [The Rust book](https://doc.rust-lang.org/book).
 - Familiarity with [Stellar smart contracts](../../smart-contracts/getting-started/hello-world.mdx)
 - Installed [Stellar CLI](../../smart-contracts/getting-started/setup.mdx#install-the-stellar-cli) and Soroban SDK
 
diff --git a/docs/build/guides/dapps/docker.mdx b/docs/build/guides/dapps/docker.mdx
index 27f343670a..cc64889c2e 100644
--- a/docs/build/guides/dapps/docker.mdx
+++ b/docs/build/guides/dapps/docker.mdx
@@ -6,7 +6,7 @@ draft: true
 
 ## What is Docker?
 
-Welcome to the world of [Docker](https://www.docker.com/), an essential tool for software development. Docker packages software into units known as containers, ensuring consistency, isolation, portability, and scalability.
+Welcome to the world of [Docker](https://www.docker.com), an essential tool for software development. Docker packages software into units known as containers, ensuring consistency, isolation, portability, and scalability.
 
 Docker is particularly useful in dapp development. It helps manage microservices, maintain consistent environments throughout development stages, and simulate a decentralized network during testing.
 
diff --git a/docs/build/guides/dapps/initialization.mdx b/docs/build/guides/dapps/initialization.mdx
index aa78bdddc8..1f9a08b158 100644
--- a/docs/build/guides/dapps/initialization.mdx
+++ b/docs/build/guides/dapps/initialization.mdx
@@ -7,7 +7,7 @@ When setting up an example Soroban Dapp, correct initialization is crucial. This
 
 ## Building the Soroban Token Smart Contract
 
-In dapps like the [Example Payment Dapp](https://github.com/stellar/soroban-react-payment/), the [Soroban Token smart contracts](https://github.com/stellar/soroban-examples/tree/main/token) are used to represent the tokenized asset that users can send and receive. Here is an example of how to build and deploy the Soroban Token smart contracts:
+In dapps like the [Example Payment Dapp](https://github.com/stellar/soroban-react-payment), the [Soroban Token smart contracts](https://github.com/stellar/soroban-examples/tree/main/token) are used to represent the tokenized asset that users can send and receive. Here is an example of how to build and deploy the Soroban Token smart contracts:
 
 Start by cloning the Soroban examples repository:
 
diff --git a/docs/build/guides/dapps/react.mdx b/docs/build/guides/dapps/react.mdx
index 57812d9786..734d2e6dcf 100644
--- a/docs/build/guides/dapps/react.mdx
+++ b/docs/build/guides/dapps/react.mdx
@@ -4,7 +4,7 @@ description: Connect dapp frontends to contracts and Freighter wallet using @sor
 draft: true
 ---
 
-This section elaborates on how the frontends from your dapp can interact with the example contracts and access chain data, and connect to a freighter wallet. This will be illustrated by utilizing libraries provided by [`@soroban-react`](https://soroban-react.gitbook.io/index/), a simple, powerful framework for building modern Dapps using React. `@soroban-react` was created and is maintained by an amazing member of the community!
+This section elaborates on how the frontends from your dapp can interact with the example contracts and access chain data, and connect to a freighter wallet. This will be illustrated by utilizing libraries provided by [`@soroban-react`](https://soroban-react.gitbook.io/index), a simple, powerful framework for building modern Dapps using React. `@soroban-react` was created and is maintained by an amazing member of the community!
 
 :::info
 
diff --git a/docs/build/guides/dapps/soroban-contract-init-template.mdx b/docs/build/guides/dapps/soroban-contract-init-template.mdx
index 95ff577387..d851265083 100644
--- a/docs/build/guides/dapps/soroban-contract-init-template.mdx
+++ b/docs/build/guides/dapps/soroban-contract-init-template.mdx
@@ -25,7 +25,7 @@ Building our own template will be a great way to learn how they work. They're no
 
 ## Search GitHub for other Soroban templates
 
-The official template maintained by Stellar Development Foundation (SDF), as used in [Build a Dapp Frontend](../../apps/dapp-frontend.mdx), lives on GitHub at [stellar/soroban-template-astro](https://github.com/stellar/soroban-astro-template). It uses the [Astro](https://astro.build/) web framework. While Astro works with React, Vue, Svelte, and any other UI library, the template opts not to use them, preferring Astro's own templating language, which uses vanilla JavaScript with no UI library.
+The official template maintained by Stellar Development Foundation (SDF), as used in [Build a Dapp Frontend](../../apps/dapp-frontend.mdx), lives on GitHub at [stellar/soroban-template-astro](https://github.com/stellar/soroban-astro-template). It uses the [Astro](https://astro.build) web framework. While Astro works with React, Vue, Svelte, and any other UI library, the template opts not to use them, preferring Astro's own templating language, which uses vanilla JavaScript with no UI library.
 
 (You may wonder why it makes this unpopular choice. A fair question! The team wanted to balance actual utility with broad approachability. Not everyone learning Stellar and Soroban is familiar with React, or any other UI library. It also demonstrates that core Soroban libraries all work with any JavaScript project.)
 
@@ -62,7 +62,7 @@ So keep that in mind. We're making a fairly simple Node project, and telling it
 
 ### 1. Initialize an NPM project
 
-So let's make a simple Node project! Rather than initializing an Astro project, like the official frontend template, let's try something new. The [State of JS survey](https://2022.stateofjs.com/en-US/libraries/front-end-frameworks/#front_end_frameworks_experience_linechart) tells me that something called "Solid" is fairly new and well-loved. [What does it say to do?](https://www.solidjs.com/)
+So let's make a simple Node project! Rather than initializing an Astro project, like the official frontend template, let's try something new. The [State of JS survey](https://2022.stateofjs.com/en-US/libraries/front-end-frameworks/#front_end_frameworks_experience_linechart) tells me that something called "Solid" is fairly new and well-loved. [What does it say to do?](https://www.solidjs.com)
 
 ```bash
 npx degit solidjs/templates/ts soroban-template-solid
diff --git a/docs/build/guides/fees/analyzing-smart-contract-cost.mdx b/docs/build/guides/fees/analyzing-smart-contract-cost.mdx
index acdd9d8184..0595343f67 100644
--- a/docs/build/guides/fees/analyzing-smart-contract-cost.mdx
+++ b/docs/build/guides/fees/analyzing-smart-contract-cost.mdx
@@ -558,7 +558,7 @@ Also, using [simulateTransaction](../../../data/apis/rpc/api-reference/methods/s
 
 ### 4. Static analysis tools
 
-Tools like [Clippy](https://doc.rust-lang.org/clippy/) (part of the Rust compiler) can identify potential performance issues during the compilation stage. These tools can warn about:
+Tools like [Clippy](https://doc.rust-lang.org/clippy) (part of the Rust compiler) can identify potential performance issues during the compilation stage. These tools can warn about:
 
 - Unnecessary allocations
 - Redundant code
diff --git a/docs/build/guides/freighter/README.mdx b/docs/build/guides/freighter/README.mdx
index 5698d770e7..bf9a834ec4 100644
--- a/docs/build/guides/freighter/README.mdx
+++ b/docs/build/guides/freighter/README.mdx
@@ -4,4 +4,4 @@ hide_table_of_contents: true
 sidebar_position: 70
 ---
 
-[Freighter](https://www.freighter.app/) is a browser extension wallet provided by the Stellar Development Foundation. It provides users a way to interact with Soroban tokens directly from the web browser.
+[Freighter](https://www.freighter.app) is a browser extension wallet provided by the Stellar Development Foundation. It provides users a way to interact with Soroban tokens directly from the web browser.
diff --git a/docs/build/guides/freighter/prompt-to-sign-tx.mdx b/docs/build/guides/freighter/prompt-to-sign-tx.mdx
index d5e49be305..9675e1eddf 100644
--- a/docs/build/guides/freighter/prompt-to-sign-tx.mdx
+++ b/docs/build/guides/freighter/prompt-to-sign-tx.mdx
@@ -4,7 +4,7 @@ hide_table_of_contents: true
 description: Sign smart contract transactions using the Freighter browser extension
 ---
 
-If you're building a JS dapp, easily sign Soroban transactions using the [Freighter browser extension](https://www.freighter.app/) and its corresponding client library [@stellar/freighter-api](https://www.npmjs.com/package/@stellar/freighter-api):
+If you're building a JS dapp, easily sign Soroban transactions using the [Freighter browser extension](https://www.freighter.app) and its corresponding client library [@stellar/freighter-api](https://www.npmjs.com/package/@stellar/freighter-api):
 
 1. Follow the setup instructions to [connect to the Testnet](./connect-testnet.mdx), if required during development.
 
diff --git a/docs/build/guides/tokens/deploying-a-sac.mdx b/docs/build/guides/tokens/deploying-a-sac.mdx
index a48ec89bf6..c98cfaeeee 100644
--- a/docs/build/guides/tokens/deploying-a-sac.mdx
+++ b/docs/build/guides/tokens/deploying-a-sac.mdx
@@ -27,7 +27,7 @@ In this guide, you'll learn how to deploy a [Stellar Asset Contract (SAC)](../..
 
 Before you begin, make sure you have the following:
 
-- Basic understanding of [Rust programming language](https://www.rust-lang.org/). To brush up on Rust, check out [Rustlings](https://github.com/rust-lang/rustlings) or [The Rust book](https://doc.rust-lang.org/book/).
+- Basic understanding of [Rust programming language](https://www.rust-lang.org). To brush up on Rust, check out [Rustlings](https://github.com/rust-lang/rustlings) or [The Rust book](https://doc.rust-lang.org/book).
 - [Soroban Rust SDK](../../../tools/sdks/contract-sdks.mdx#soroban-rust-sdk) installed and configured in your development environment.
 - Basic understanding of the Soroban Rust SDK and familiarity with Soroban's core concepts and Rust programming.
 
diff --git a/docs/build/guides/transactions/install-deploy-contract-with-code.mdx b/docs/build/guides/transactions/install-deploy-contract-with-code.mdx
index 421d0b0c1e..0868abc6d0 100644
--- a/docs/build/guides/transactions/install-deploy-contract-with-code.mdx
+++ b/docs/build/guides/transactions/install-deploy-contract-with-code.mdx
@@ -22,7 +22,7 @@ This guide will walk you through the process of installing and deploying a smart
 
 Before you begin, ensure you have the following installed:
 
-1. [Rust](https://www.rust-lang.org/) and Cargo (for compiling smart contracts)
+1. [Rust](https://www.rust-lang.org) and Cargo (for compiling smart contracts)
 2. [Node.js](https://nodejs.org/en) and npm (for running JavaScript deployment scripts)
 3. [Soroban CLI](../../smart-contracts/getting-started/setup.mdx#install-the-stellar-cli)
 
diff --git a/docs/build/guides/transactions/simulateTransaction-Deep-Dive.mdx b/docs/build/guides/transactions/simulateTransaction-Deep-Dive.mdx
index 6277eb7b0c..e842fad216 100644
--- a/docs/build/guides/transactions/simulateTransaction-Deep-Dive.mdx
+++ b/docs/build/guides/transactions/simulateTransaction-Deep-Dive.mdx
@@ -409,4 +409,4 @@ For more information and examples, check out the code and other documentation:
 - [openRpc json Specification](https://github.com/stellar/stellar-docs/tree/main/openrpc)
 - [preflight.go](https://github.com/stellar/stellar-rpc/blob/release/v22.1.2/cmd/stellar-rpc/internal/preflight/preflight.go)
 - [Soroban Example Code](https://github.com/stellar/soroban-examples)
-- [Stellar SDK Documentation](https://stellar.github.io/js-stellar-sdk/)
+- [Stellar SDK Documentation](https://stellar.github.io/js-stellar-sdk)
diff --git a/docs/build/guides/transactions/upload-wasm-bytecode.mdx b/docs/build/guides/transactions/upload-wasm-bytecode.mdx
index 8883523b9a..a6be82a5cb 100644
--- a/docs/build/guides/transactions/upload-wasm-bytecode.mdx
+++ b/docs/build/guides/transactions/upload-wasm-bytecode.mdx
@@ -27,7 +27,7 @@ This process uploads the contract code to the Stellar Testnet in a transaction,
 
 Before you begin, ensure you have the following installed to compile a smart contract:
 
-1. [Rust](https://www.rust-lang.org/) and Cargo (for compiling smart contracts)
+1. [Rust](https://www.rust-lang.org) and Cargo (for compiling smart contracts)
 2. The [Stellar CLI](https://github.com/stellar/stellar-cli)
 
 ## Initialize and build a sample Rust contract
@@ -50,7 +50,7 @@ After building the contract for release, the generated .wasm file is at the path
 We can use one of the [client SDKs](../../../tools/sdks/client-sdks.mdx), install necessary dependencies for your chosen programming language:
 
 - JavaScript SDK: [Node.js](https://nodejs.org/en) and npm
-- Python SDK: [pip](https://pip.pypa.io/en/stable/installation/)
+- Python SDK: [pip](https://pip.pypa.io/en/stable/installation)
 
 Create a new directory for your project and navigate into it:
 
@@ -152,7 +152,7 @@ try {
 
 </TabItem>
 <TabItem value="py" label="Python">
-This guide will walk you through installing the Wasm of the contract using the Python SDK: [py-stellar-base](https://stellar-sdk.readthedocs.io/en/soroban/).
+This guide will walk you through installing the Wasm of the contract using the Python SDK: [py-stellar-base](https://stellar-sdk.readthedocs.io/en/soroban).
 
 Create a new Python script, and install the necessary dependencies:
 
diff --git a/docs/build/security-docs/securing-web-based-projects.mdx b/docs/build/security-docs/securing-web-based-projects.mdx
index e12a2237ff..f03f9288d2 100644
--- a/docs/build/security-docs/securing-web-based-projects.mdx
+++ b/docs/build/security-docs/securing-web-based-projects.mdx
@@ -7,7 +7,7 @@ Any application managing cryptocurrency is a frequent target of malicious actors
 
 ## SSL/TLS
 
-Ensure that TLS is enabled. Redirect HTTP to HTTPS where necessary to ensure that Man in the Middle attacks can’t occur and sensitive data is securely transferred between the client and browser. Enable TLS and get an SSL certificate for free at [LetsEncrypt](https://letsencrypt.org/getting-started/).
+Ensure that TLS is enabled. Redirect HTTP to HTTPS where necessary to ensure that Man in the Middle attacks can’t occur and sensitive data is securely transferred between the client and browser. Enable TLS and get an SSL certificate for free at [LetsEncrypt](https://letsencrypt.org/getting-started).
 
 If you don’t have SSL/TLS enabled, stop everything and do this first.
 
@@ -15,11 +15,11 @@ If you don’t have SSL/TLS enabled, stop everything and do this first.
 
 CSP headers tell the browser where it can download static resources from. For example, if you astralwallet.io and it requests a JavaScript file from myevilsite.com, your browser will block it unless it was whitelisted with CSP headers. You can read about how to implement CSP headers [here](https://developer.mozilla.org/en-US/docs/Web/HTTP/CSP).
 
-Most web frameworks have a configuration file or extensions to specify your CSP policy, and the headers are auto-generated for you. For example, see [Helmet](https://www.npmjs.com/package/helmet) for Node.js. This would have prevented the [Blackwallet Hack](https://www.ccn.com/yet-another-crypto-wallet-hack-causes-users-lose-400000/).
+Most web frameworks have a configuration file or extensions to specify your CSP policy, and the headers are auto-generated for you. For example, see [Helmet](https://www.npmjs.com/package/helmet) for Node.js. This would have prevented the [Blackwallet Hack](https://www.ccn.com/yet-another-crypto-wallet-hack-causes-users-lose-400000).
 
 ## HTTP strict-transport-security headers
 
-This is an HTTP header that tells the browser that all future connections to a particular site should use HTTPS. To implement this, add the [header](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Strict-Transport-Security) to your website. Some web frameworks (like [Django](https://docs.djangoproject.com/en/2.0/topics/security/#ssl-https)) have this built-in. This would have prevented the [MyEtherWallet DNS Hack](https://bitcoinmagazine.com/articles/popular-ether-wallet-mew-hijacked-dns-attack/).
+This is an HTTP header that tells the browser that all future connections to a particular site should use HTTPS. To implement this, add the [header](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Strict-Transport-Security) to your website. Some web frameworks (like [Django](https://docs.djangoproject.com/en/2.0/topics/security/#ssl-https)) have this built-in. This would have prevented the [MyEtherWallet DNS Hack](https://bitcoinmagazine.com/articles/popular-ether-wallet-mew-hijacked-dns-attack).
 
 ## Storing sensitive data
 
@@ -35,7 +35,7 @@ Ideally, you don’t have to store much sensitive data. If you must, be sure to
 
 Attackers often need to spend time exploring your website for unexpected or overlooked behavior. Examining logs defensively can help you catch onto what they’re trying to achieve. You can at least block their IP or automate blocking based on suspicious behavior.
 
-It’s also worth setting up an error reporting (like [Sentry](https://sentry.io/welcome/)). Often, people trigger strange bugs when trying to hack things.
+It’s also worth setting up an error reporting (like [Sentry](https://sentry.io/welcome)). Often, people trigger strange bugs when trying to hack things.
 
 ## Authentication weaknesses
 
@@ -47,11 +47,11 @@ Hash passwords with a time-tested scheme are good. And Balloon Hashing is also w
 
 We strongly prefer 2FA and require U2F or [TOTP](https://tools.ietf.org/html/rfc6238) 2FA for sensitive actions. 2FA is important as email accounts are usually not very secure. Having a second factor of authentication ensures that users who accidentally stay logged on or have their password guessed are still protected.
 
-Finally, require strong passwords. Common and short passwords can be brute-forced. Dropbox has a great [open-source tool](https://blogs.dropbox.com/tech/2012/04/zxcvbn-realistic-password-strength-estimation/) that gauges password strength fairly quickly, making it usable for user interactions.
+Finally, require strong passwords. Common and short passwords can be brute-forced. Dropbox has a great [open-source tool](https://blogs.dropbox.com/tech/2012/04/zxcvbn-realistic-password-strength-estimation) that gauges password strength fairly quickly, making it usable for user interactions.
 
 ## Denial of service attacks (DOS)
 
-DOS attacks are usually accomplished by overloading your web servers with traffic. To mitigate this risk, rate limit traffic from IPs and browser fingerprints. Sometimes people will use proxies to bypass IP rate-limiting. In the end, malicious actors can always find ways to spoof their identity, so the surest way to block DOS attacks is to implement proof of work checks in your client or use a managed service like [Cloudflare](https://www.cloudflare.com/ddos/).
+DOS attacks are usually accomplished by overloading your web servers with traffic. To mitigate this risk, rate limit traffic from IPs and browser fingerprints. Sometimes people will use proxies to bypass IP rate-limiting. In the end, malicious actors can always find ways to spoof their identity, so the surest way to block DOS attacks is to implement proof of work checks in your client or use a managed service like [Cloudflare](https://www.cloudflare.com/ddos).
 
 ## Lockdown unused ports
 
@@ -63,7 +63,7 @@ Phishing attacks will thwart any well-formed security infrastructure. Have clear
 
 ## Scan your website and libraries for vulnerabilities
 
-Use a tool like [Snyk](https://snyk.io/) to scan your third-party client libraries for vulnerabilities. Make sure to keep your third-party libraries up to date. Often, upgrades are triggered by security exploits. You can use [Mozilla Observatory](https://observatory.mozilla.org/) to check your HTTP security as well.
+Use a tool like [Snyk](https://snyk.io) to scan your third-party client libraries for vulnerabilities. Make sure to keep your third-party libraries up to date. Often, upgrades are triggered by security exploits. You can use [Mozilla Observatory](https://observatory.mozilla.org) to check your HTTP security as well.
 
 ## Cross-Site Request Forgery Protection (CSRF), SQL injections
 
diff --git a/docs/build/smart-contracts/example-contracts/bls-signature.mdx b/docs/build/smart-contracts/example-contracts/bls-signature.mdx
index e93119c14e..9f04bafcab 100644
--- a/docs/build/smart-contracts/example-contracts/bls-signature.mdx
+++ b/docs/build/smart-contracts/example-contracts/bls-signature.mdx
@@ -39,7 +39,7 @@ It is good to have an understanding of how a contract account works, so walk thr
 
 ## Background on BLS Signature
 
-There are plenty of good resources on BLS signature, for example the "BLS12-381 For The Rest Of Us" has a section on [BLS digital signature](https://hackmd.io/@benjaminion/bls12-381#BLS-digital-signatures). [BLS Signature for Busy People](https://gist.github.com/paulmillr/18b802ad219b1aee34d773d08ec26ca2) is a also a good resource for a quick overview. For full reference check out the [IETF draft](https://datatracker.ietf.org/doc/draft-irtf-cfrg-bls-signature/).
+There are plenty of good resources on BLS signature, for example the "BLS12-381 For The Rest Of Us" has a section on [BLS digital signature](https://hackmd.io/@benjaminion/bls12-381#BLS-digital-signatures). [BLS Signature for Busy People](https://gist.github.com/paulmillr/18b802ad219b1aee34d773d08ec26ca2) is a also a good resource for a quick overview. For full reference check out the [IETF draft](https://datatracker.ietf.org/doc/draft-irtf-cfrg-bls-signature).
 
 In short, we are verifying the following relation:
 
@@ -61,7 +61,7 @@ with a single pairing on chain, you can verify N signatures on the same message
 
 ### Hash of message `H(m)`
 
-The message will need to be hashed on the curve `H(m)` for pairing operation to be applied. We follow the approach outlined in [RFC 9380 - Hashing to Elliptic Curves](https://datatracker.ietf.org/doc/rfc9380/).
+The message will need to be hashed on the curve `H(m)` for pairing operation to be applied. We follow the approach outlined in [RFC 9380 - Hashing to Elliptic Curves](https://datatracker.ietf.org/doc/rfc9380).
 
 The hashing method requires a unique domain separation tag (DST), it is highly advisable that your application choose a unique DST. For the requirements of DST, refer to section 3.1 of the RFC,
 
diff --git a/docs/build/smart-contracts/getting-started/hello-world-frontend.mdx b/docs/build/smart-contracts/getting-started/hello-world-frontend.mdx
index 91f2ec456e..8dfdc9a636 100644
--- a/docs/build/smart-contracts/getting-started/hello-world-frontend.mdx
+++ b/docs/build/smart-contracts/getting-started/hello-world-frontend.mdx
@@ -18,13 +18,13 @@ This example shows one way of creating a binding between a contract and a fronte
 
 ## Initialize a frontend toolchain from scratch
 
-You can build a Stellar dapp with any frontend toolchain or integrate it into any existing full-stack app. For this tutorial, we're going to use [Astro](https://astro.build/). Astro works with React, Vue, Svelte, any other UI library, or no UI library at all. In this tutorial, we're not using a UI library. The smart contract-specific parts of this tutorial will be similar no matter what frontend toolchain you use.
+You can build a Stellar dapp with any frontend toolchain or integrate it into any existing full-stack app. For this tutorial, we're going to use [Astro](https://astro.build). Astro works with React, Vue, Svelte, any other UI library, or no UI library at all. In this tutorial, we're not using a UI library. The smart contract-specific parts of this tutorial will be similar no matter what frontend toolchain you use.
 
 If you're new to frontend, don't worry. We won't go too deep. But it will be useful for you to see and experience the frontend development process used by smart contract apps. We'll cover the relevant bits of JavaScript and Astro, but teaching all of frontend development and Astro is beyond the scope of this tutorial.
 
 Let's get started.
 
-You're going to need [Node.js](https://nodejs.org/en/download/package-manager/) v20 or greater. If you haven't yet, install it now.
+You're going to need [Node.js](https://nodejs.org/en/download/package-manager) v20 or greater. If you haven't yet, install it now.
 
 We want to create an Astro project with the Hello World contract from the previous lessons integrated. To do this, we install the default Astro project:
 
@@ -155,7 +155,7 @@ Scaffold Stellar is a plugin on the Stellar CLI, so you'll run commands as `stel
 
 3. Install Node dependencies & set up environment variables
 
-Make sure you already have [Node.js](https://nodejs.org/en/download/package-manager/), and run:
+Make sure you already have [Node.js](https://nodejs.org/en/download/package-manager), and run:
 
 ```sh
 cd <my-project> # make sure you're in your new project's directory
diff --git a/docs/build/smart-contracts/getting-started/setup.mdx b/docs/build/smart-contracts/getting-started/setup.mdx
index 8e764f14bd..0bf23f3598 100644
--- a/docs/build/smart-contracts/getting-started/setup.mdx
+++ b/docs/build/smart-contracts/getting-started/setup.mdx
@@ -44,7 +44,7 @@ On Windows, download and run [rustup-init.exe](https://static.rust-lang.org/rust
 
 :::tip
 
-The Stellar CLI uses emojis in its output. To properly render them on Windows, it is recommended to use the [Windows Terminal](https://learn.microsoft.com/en-us/windows/terminal/). See [how to install Windows Terminal](https://learn.microsoft.com/en-us/windows/terminal/install) on Microsoft Learn. If the CLI is used in the built in Windows Command Prompt or Windows PowerShell the CLI will function as expected but the emojis will appear as question marks.
+The Stellar CLI uses emojis in its output. To properly render them on Windows, it is recommended to use the [Windows Terminal](https://learn.microsoft.com/en-us/windows/terminal). See [how to install Windows Terminal](https://learn.microsoft.com/en-us/windows/terminal/install) on Microsoft Learn. If the CLI is used in the built in Windows Command Prompt or Windows PowerShell the CLI will function as expected but the emojis will appear as question marks.
 
 :::
 
@@ -169,7 +169,7 @@ Using the installer:
 2. Go to your Downloads folder, double click the installer and follow the wizard instructions.
 3. Restart your terminal to use the `stellar` command.
 
-Using [winget](https://learn.microsoft.com/en-us/windows/package-manager/winget/):
+Using [winget](https://learn.microsoft.com/en-us/windows/package-manager/winget):
 
 <StellarCliWingetVersion />
 
diff --git a/docs/build/smart-contracts/overview.mdx b/docs/build/smart-contracts/overview.mdx
index daca69ff8e..4303f7d88f 100644
--- a/docs/build/smart-contracts/overview.mdx
+++ b/docs/build/smart-contracts/overview.mdx
@@ -7,7 +7,7 @@ description: "An overview of Stellar smart contracts, including information abou
 
 # Overview
 
-Soroban is the smart contracts platform on the Stellar network. These contracts are small programs written in the [Rust language](https://www.rust-lang.org/) and compiled as [WebAssembly](https://webassembly.org/) (Wasm) for deployment.
+Soroban is the smart contracts platform on the Stellar network. These contracts are small programs written in the [Rust language](https://www.rust-lang.org) and compiled as [WebAssembly](https://webassembly.org) (Wasm) for deployment.
 
 :::note
 
diff --git a/docs/data/analytics/analytics-providers/analytics-providers.mdx b/docs/data/analytics/analytics-providers/analytics-providers.mdx
index 380e4f487d..fdc0bb4114 100644
--- a/docs/data/analytics/analytics-providers/analytics-providers.mdx
+++ b/docs/data/analytics/analytics-providers/analytics-providers.mdx
@@ -8,20 +8,20 @@ The following is a list of data analytics platforms that make a complete histori
 | Platform | Description | Home page and Signup | Pricing | Data Access | Dashboard access |
 | --- | --- | --- | --- | --- | --- |
 | Hubble | SDF provides a publicly available raw dataset with a complete historical record of Stellar network data, updated every 15 minutes. | [Hubble](https://console.cloud.google.com/bigquery?project=crypto-stellar&ws=!1m4!1m3!3m2!1scrypto-stellar!2scrypto_stellar) <br></br> [Signup](https://cloud.google.com/?hl=en) | End users incur the cost to execute queries. Visit the [BigQuery Pricing](https://cloud.google.com/bigquery/pricing#analysis_pricing_models) page to learn more. | Please see the [Analyst Guide](./hubble/analyst-guide) for more information. | N/A |
-| Dune | Raw dataset for the Stellar network available in the Dune portal. Updated every hour. You can compare different chains on the platform. | [Dune](https://dune.com/) <br></br>[Signup](https://dune.com/auth/register) | Free for simpler queries. Need to pay for complex queries. | To access datasets, click [here](https://dune.com/queries?category=canonical&namespace=stellar). | Explore community dashboards, network overview, and datasets [here](https://dune.com/blockchains/stellar). |
-| Artemis | Aggregated dataset for the Stellar network available in BigQuery as well as the Artemis portal. Provides dashboards to compare Stellar chain activity with ecosystem chains. | [Artemis](https://www.artemis.xyz/) <br></br>[Signup](https://app.artemisanalytics.com/artemis-terminal-auth?flow=SIGN_UP) | Free dashboards. Need to pay for accessing the raw dataset. | For accessing Artemis-transformed Stellar dataset, upgrade to the enterprise plan and then star [this dataset](https://console.cloud.google.com/bigquery?ws=!1m4!1m3!3m2!1sartemis-bigquery-share!2sshared_us). | Explore [chain compare](https://app.artemisanalytics.com/chains?selectedChains=stellar) and [application activity](https://app.artemis.xyz/application-activity/stellar) dashboards. |
-| Nansen | Aggregated dataset for the Stellar network available in the Nansen portal. Provides dashboards to compare Stellar chain activity with ecosystem chains. | [Nansen](https://app.nansen.ai/) <br></br>[Signup](https://app.nansen.ai/auth/signup) | Free dashboards. Need to pay for accessing the raw dataset. | For accessing Nansen-transformed Stellar dataset, upgrade to the Pioneer plan and then star [this dataset](https://console.cloud.google.com/bigquery?project=nansen-query). | Explore [chain activity, entity, and ecosystem](https://app.nansen.ai/macro/blockchains?chain=stellar&tab=overview). |
-| Ortege | Ortege hosts data services to make blockchain data more accessible through real time APIs and a managed [Lakehouse](https://docs.ortege.ai/en/ortege-products/ortege-lakehouse) for analytics exploration. The lakehouse follows a standardize schema across blockchains, making it easy to plug-and-play across L1s. | [Ortege](https://www.ortege.ai/) <br></br>[Signup](https://app.ortege.ai/register/form) | Free for simpler queries, for larger workloads, user must purchase credits in the warehouse | Here is a [link](https://docs.ortege.ai/en/ortege-products/ortege-lakehouse/data-catalog/in-house-datasets) to their data catalog for data access. | Explore curated dashboards [here](https://app.ortege.ai/dashboard/list/), or build your own |
-| Flipside | Raw dataset access to run queries, create dashboards and gain actionable intelligence on various crypto ecosystems. Flipside sponsors analytics bounties to encourage open source sharing of insights as well as developer quests. | [Flipside](https://flipsidecrypto.xyz/home/) <br></br>[Signup](https://flipsidecrypto.xyz/home/sign-up) | Entire data access (raw, dashboards) is free. | To access the dataset, sign up on Flipside and find the "Stellar" database in [Flipside studio](https://flipsidecrypto.xyz/studio/). | Explore [community dashboards](https://flipsidecrypto.xyz/insights/dashboards?search=stellar). |
-| DefiLlama | TVL aggregator for DeFi (Decentralized Finance). | [DefiLlama](https://defillama.com/) | Free(open source) access to TVL dashboard | For data access, checkout [API Docs](https://defillama.com/docs/api) | Explore the [TVL Dashboard](https://defillama.com/chain/Stellar). |
-| Messari | Messari serves as a central hub for research and data related to the cryptoeconomy. With customizable and user-friendly features. | [Messari](https://messari.io/) | Free access to dashboards and data ([subscription](https://messari.io/account/plan) for more advanced access) | For data access, checkout [API Docs](https://docs.messari.io/reference/introduction) | Explore the [Stellar Portal](https://stellar.messari.io/). |
-| rwa.xyz | Aggregated information about tokenized real-world assets. | [rwa.xyz](https://www.rwa.xyz/) | Free access to dashboards and general rwa information | For data access, checkout [Data & API Platform](https://app.rwa.xyz/platform-overview) | Explore the [Stellar Dashboard](https://app.rwa.xyz/networks/stellar). |
-| Token Terminal | Token Terminal is a full stack onchain data platform focused on standardizing financial and alternative data for the most widely used blockchains and decentralized applications. | [Token Terminal](https://tokenterminal.com/) | Free access to dashboards. Paid [API access](https://tokenterminal.com/explorer/account/api) | For data access, checkout [API Docs](https://tokenterminal.com/docs/api-reference/introduction) | Explore the [Stellar Dashboard](https://tokenterminal.com/explorer/projects/stellar). |
-| SonarX | SonarX provides a one-stop-shop for indexed Stellar data. | [SonarX](https://www.sonarx.com/) | Paid access to raw and curated datasets. | There are two products for data access, [Real-Time Data](https://www.sonarx.com/product/realtime) and [Historical Streaming](https://www.sonarx.com/product/historical) | N/A |
-| Range | The blockchain security and intelligence platform; helping the best teams build and use DeFi protocols, blockchains, rollups, and cross-chain bridges with peace of mind. | [Range](https://www.range.org/) | Free access to analytics. Paid access to APIs and Security Products | Stellar has their own [Home Page](https://stellar.range.org/) and we are featured on their [Stable Coin](https://stable.range.org/) explorer as well. | Explore the [Stellar Dashboard](https://stellar.range.org/). |
+| Dune | Raw dataset for the Stellar network available in the Dune portal. Updated every hour. You can compare different chains on the platform. | [Dune](https://dune.com) <br></br>[Signup](https://dune.com/auth/register) | Free for simpler queries. Need to pay for complex queries. | To access datasets, click [here](https://dune.com/queries?category=canonical&namespace=stellar). | Explore community dashboards, network overview, and datasets [here](https://dune.com/blockchains/stellar). |
+| Artemis | Aggregated dataset for the Stellar network available in BigQuery as well as the Artemis portal. Provides dashboards to compare Stellar chain activity with ecosystem chains. | [Artemis](https://www.artemis.xyz) <br></br>[Signup](https://app.artemisanalytics.com/artemis-terminal-auth?flow=SIGN_UP) | Free dashboards. Need to pay for accessing the raw dataset. | For accessing Artemis-transformed Stellar dataset, upgrade to the enterprise plan and then star [this dataset](https://console.cloud.google.com/bigquery?ws=!1m4!1m3!3m2!1sartemis-bigquery-share!2sshared_us). | Explore [chain compare](https://app.artemisanalytics.com/chains?selectedChains=stellar) and [application activity](https://app.artemis.xyz/application-activity/stellar) dashboards. |
+| Nansen | Aggregated dataset for the Stellar network available in the Nansen portal. Provides dashboards to compare Stellar chain activity with ecosystem chains. | [Nansen](https://app.nansen.ai) <br></br>[Signup](https://app.nansen.ai/auth/signup) | Free dashboards. Need to pay for accessing the raw dataset. | For accessing Nansen-transformed Stellar dataset, upgrade to the Pioneer plan and then star [this dataset](https://console.cloud.google.com/bigquery?project=nansen-query). | Explore [chain activity, entity, and ecosystem](https://app.nansen.ai/macro/blockchains?chain=stellar&tab=overview). |
+| Ortege | Ortege hosts data services to make blockchain data more accessible through real time APIs and a managed [Lakehouse](https://docs.ortege.ai/en/ortege-products/ortege-lakehouse) for analytics exploration. The lakehouse follows a standardize schema across blockchains, making it easy to plug-and-play across L1s. | [Ortege](https://www.ortege.ai) <br></br>[Signup](https://app.ortege.ai/register/form) | Free for simpler queries, for larger workloads, user must purchase credits in the warehouse | Here is a [link](https://docs.ortege.ai/en/ortege-products/ortege-lakehouse/data-catalog/in-house-datasets) to their data catalog for data access. | Explore curated dashboards [here](https://app.ortege.ai/dashboard/list), or build your own |
+| Flipside | Raw dataset access to run queries, create dashboards and gain actionable intelligence on various crypto ecosystems. Flipside sponsors analytics bounties to encourage open source sharing of insights as well as developer quests. | [Flipside](https://flipsidecrypto.xyz/home) <br></br>[Signup](https://flipsidecrypto.xyz/home/sign-up) | Entire data access (raw, dashboards) is free. | To access the dataset, sign up on Flipside and find the "Stellar" database in [Flipside studio](https://flipsidecrypto.xyz/studio). | Explore [community dashboards](https://flipsidecrypto.xyz/insights/dashboards?search=stellar). |
+| DefiLlama | TVL aggregator for DeFi (Decentralized Finance). | [DefiLlama](https://defillama.com) | Free(open source) access to TVL dashboard | For data access, checkout [API Docs](https://defillama.com/docs/api) | Explore the [TVL Dashboard](https://defillama.com/chain/Stellar). |
+| Messari | Messari serves as a central hub for research and data related to the cryptoeconomy. With customizable and user-friendly features. | [Messari](https://messari.io) | Free access to dashboards and data ([subscription](https://messari.io/account/plan) for more advanced access) | For data access, checkout [API Docs](https://docs.messari.io/reference/introduction) | Explore the [Stellar Portal](https://stellar.messari.io). |
+| rwa.xyz | Aggregated information about tokenized real-world assets. | [rwa.xyz](https://www.rwa.xyz) | Free access to dashboards and general rwa information | For data access, checkout [Data & API Platform](https://app.rwa.xyz/platform-overview) | Explore the [Stellar Dashboard](https://app.rwa.xyz/networks/stellar). |
+| Token Terminal | Token Terminal is a full stack onchain data platform focused on standardizing financial and alternative data for the most widely used blockchains and decentralized applications. | [Token Terminal](https://tokenterminal.com) | Free access to dashboards. Paid [API access](https://tokenterminal.com/explorer/account/api) | For data access, checkout [API Docs](https://tokenterminal.com/docs/api-reference/introduction) | Explore the [Stellar Dashboard](https://tokenterminal.com/explorer/projects/stellar). |
+| SonarX | SonarX provides a one-stop-shop for indexed Stellar data. | [SonarX](https://www.sonarx.com) | Paid access to raw and curated datasets. | There are two products for data access, [Real-Time Data](https://www.sonarx.com/product/realtime) and [Historical Streaming](https://www.sonarx.com/product/historical) | N/A |
+| Range | The blockchain security and intelligence platform; helping the best teams build and use DeFi protocols, blockchains, rollups, and cross-chain bridges with peace of mind. | [Range](https://www.range.org) | Free access to analytics. Paid access to APIs and Security Products | Stellar has their own [Home Page](https://stellar.range.org) and we are featured on their [Stable Coin](https://stable.range.org) explorer as well. | Explore the [Stellar Dashboard](https://stellar.range.org). |
 
 <!-- Allium login not working as of the writing of this doc
-| Allium | Raw dataset access to the Stellar network. | [Allium](https://www.allium.so/) | Free data access and queries | For data access, checkout [Allium Docs](https://docs.allium.so/) | N/A | -->
+| Allium | Raw dataset access to the Stellar network. | [Allium](https://www.allium.so) | Free data access and queries | For data access, checkout [Allium Docs](https://docs.allium.so) | N/A | -->
 
 ## Run Your Own Hubble
 
diff --git a/docs/data/analytics/hubble/analyst-guide/connecting.mdx b/docs/data/analytics/hubble/analyst-guide/connecting.mdx
index 2224d33845..a1e79f9f54 100644
--- a/docs/data/analytics/hubble/analyst-guide/connecting.mdx
+++ b/docs/data/analytics/hubble/analyst-guide/connecting.mdx
@@ -127,7 +127,7 @@ There are various ways to extract and load data using BigQuery. See the [BigQuer
 
 To connect Hubble as a data source:
 
-1. Open [Looker Studio](https://lookerstudio.google.com/)
+1. Open [Looker Studio](https://lookerstudio.google.com)
 2. Click on **Create** > **Data Source**
 3. Search for the BigQuery connector
 4. _(Optional)_ Change the name of the data source at the top of the webpage
@@ -139,6 +139,6 @@ To connect Hubble as a data source:
 
 And you're connected!
 
-General information about Looker Studio can be found [here](https://support.google.com/looker-studio/).
+General information about Looker Studio can be found [here](https://support.google.com/looker-studio).
 
 General information about connecting data sources can be found [here](https://support.google.com/looker-studio/topic/6370331?hl=en&ref_topic=7441382&sjid=14945902445646860578-NA).
diff --git a/docs/data/analytics/hubble/developer-guide/connecting-to-bigquery/README.mdx b/docs/data/analytics/hubble/developer-guide/connecting-to-bigquery/README.mdx
index 2224d33845..a1e79f9f54 100644
--- a/docs/data/analytics/hubble/developer-guide/connecting-to-bigquery/README.mdx
+++ b/docs/data/analytics/hubble/developer-guide/connecting-to-bigquery/README.mdx
@@ -127,7 +127,7 @@ There are various ways to extract and load data using BigQuery. See the [BigQuer
 
 To connect Hubble as a data source:
 
-1. Open [Looker Studio](https://lookerstudio.google.com/)
+1. Open [Looker Studio](https://lookerstudio.google.com)
 2. Click on **Create** > **Data Source**
 3. Search for the BigQuery connector
 4. _(Optional)_ Change the name of the data source at the top of the webpage
@@ -139,6 +139,6 @@ To connect Hubble as a data source:
 
 And you're connected!
 
-General information about Looker Studio can be found [here](https://support.google.com/looker-studio/).
+General information about Looker Studio can be found [here](https://support.google.com/looker-studio).
 
 General information about connecting data sources can be found [here](https://support.google.com/looker-studio/topic/6370331?hl=en&ref_topic=7441382&sjid=14945902445646860578-NA).
diff --git a/docs/data/apis/horizon/README.mdx b/docs/data/apis/horizon/README.mdx
index 4675889855..4525e96bd9 100644
--- a/docs/data/apis/horizon/README.mdx
+++ b/docs/data/apis/horizon/README.mdx
@@ -30,8 +30,8 @@ Running Horizon within your own infrastructure provides a number of benefits. Yo
 
 The Stellar Development Foundation (SDF) runs two instances of Horizon:
 
-- [horizon-testnet.stellar.org](https://horizon-testnet.stellar.org/) for interacting with the [testnet](../../../networks/README.mdx)
-- [horizon-futurenet.stellar.org](https://horizon-futurenet.stellar.org/) for interacting with the [futurenet](../../..//README.mdx)
+- [horizon-testnet.stellar.org](https://horizon-testnet.stellar.org) for interacting with the [testnet](../../../networks/README.mdx)
+- [horizon-futurenet.stellar.org](https://horizon-futurenet.stellar.org) for interacting with the [futurenet](../../..//README.mdx)
 
 ## In These Docs
 
diff --git a/docs/data/apis/horizon/admin-guide/configuring.mdx b/docs/data/apis/horizon/admin-guide/configuring.mdx
index 2b7739f3fd..c3cd79696f 100644
--- a/docs/data/apis/horizon/admin-guide/configuring.mdx
+++ b/docs/data/apis/horizon/admin-guide/configuring.mdx
@@ -108,7 +108,7 @@ The `stellar-horizon` binary searches process environment variables for configur
 
 ### Bare-metal
 
-- Non-package manager: use O/S environment variables to pass configurations. There are many tools you can use to manage them, such as [direnv](http://direnv.net/) or [dotenv](https://github.com/bkeepers/dotenv).
+- Non-package manager: use O/S environment variables to pass configurations. There are many tools you can use to manage them, such as [direnv](http://direnv.net) or [dotenv](https://github.com/bkeepers/dotenv).
 - [Package manager](./installing.mdx#package-manager): the provided `stellar-horizon-cmd` wrapper will start a new process and create environment variables in the process from `/etc/default/stellar-horizon` and then launch the 'stellar-horizon'. To set configurations, edit the file at `/etc/default/stellar-horizon`.
 
   :::info
@@ -120,7 +120,7 @@ The `stellar-horizon` binary searches process environment variables for configur
 ### Containerized
 
 - Non-Helm: pass all configuration parameters to the horizon docker image as [docker environment variables](https://docs.docker.com/engine/reference/commandline/run/#env).
-- Helm: pass all configuration parameters in the [Helm install command](https://helm.sh/docs/helm/helm_install/) as a values file.
+- Helm: pass all configuration parameters in the [Helm install command](https://helm.sh/docs/helm/helm_install) as a values file.
 
 ## Initialize Horizon Database
 
diff --git a/docs/data/apis/horizon/admin-guide/ingestion-filtering.mdx b/docs/data/apis/horizon/admin-guide/ingestion-filtering.mdx
index 076f1fc638..5db636acf9 100644
--- a/docs/data/apis/horizon/admin-guide/ingestion-filtering.mdx
+++ b/docs/data/apis/horizon/admin-guide/ingestion-filtering.mdx
@@ -41,7 +41,7 @@ Filtering is enabled by default with no filter rules defined. When no filter rul
 - enable Horizon admin port with environmental configuration parameter `ADMIN_PORT=XXXXX`, this will allow you to access the port.
 - define filter whitelists. submit Admin HTTP API requests to view and update the filter rules:
 
-  Refer to the [Horizon Admin API Docs](https://github.com/stellar/stellar-horizon/blob/main/internal/httpx/static/admin_oapi.yml) which are also published on Horizon running instances as Open API 3.0 doc on the Admin Port when enabled at `http://localhost:<admin_port>/`. You can paste the contents from that url into any OAPI tool such as [Swagger](https://editor.swagger.io/) which will render a visual explorer of the API endpoints. On the swagger editor you can also load the published Horizon admin.oapi.yml directly as a url, choose `File->Import URL`:
+  Refer to the [Horizon Admin API Docs](https://github.com/stellar/stellar-horizon/blob/main/internal/httpx/static/admin_oapi.yml) which are also published on Horizon running instances as Open API 3.0 doc on the Admin Port when enabled at `http://localhost:<admin_port>/`. You can paste the contents from that url into any OAPI tool such as [Swagger](https://editor.swagger.io) which will render a visual explorer of the API endpoints. On the swagger editor you can also load the published Horizon admin.oapi.yml directly as a url, choose `File->Import URL`:
 
   ```
    https://raw.githubusercontent.com/stellar/stellar-horizon/main/internal/httpx/static/admin_oapi.yml
diff --git a/docs/data/apis/horizon/admin-guide/ingestion.mdx b/docs/data/apis/horizon/admin-guide/ingestion.mdx
index 88c684176a..cb840e5ab9 100644
--- a/docs/data/apis/horizon/admin-guide/ingestion.mdx
+++ b/docs/data/apis/horizon/admin-guide/ingestion.mdx
@@ -92,4 +92,4 @@ horizon2> stellar-horizon db reingest range 15001 30000 --parallel-workers 2
 
 #### Monitoring Ingestion Process
 
-For high-availability deployments, it is recommended to implement monitoring of ingestion process for visibility on performance/health. Refer to [Monitoring](./monitoring.mdx) for accessing logs and metrics from Horizon. Stellar publishes the example [Horizon Grafana Dashboard](https://grafana.com/grafana/dashboards/13793-stellar-horizon/), which demonstrates queries against key horizon ingestion metrics, specifically look at the `Local Ingestion Delay [Ledgers]` and `Last ledger age` in the `Health Summary` panel.
+For high-availability deployments, it is recommended to implement monitoring of ingestion process for visibility on performance/health. Refer to [Monitoring](./monitoring.mdx) for accessing logs and metrics from Horizon. Stellar publishes the example [Horizon Grafana Dashboard](https://grafana.com/grafana/dashboards/13793-stellar-horizon), which demonstrates queries against key horizon ingestion metrics, specifically look at the `Local Ingestion Delay [Ledgers]` and `Last ledger age` in the `Health Summary` panel.
diff --git a/docs/data/apis/horizon/admin-guide/installing.mdx b/docs/data/apis/horizon/admin-guide/installing.mdx
index 8e4bde1bca..b3627efc7b 100644
--- a/docs/data/apis/horizon/admin-guide/installing.mdx
+++ b/docs/data/apis/horizon/admin-guide/installing.mdx
@@ -42,11 +42,11 @@ Refer to the list of [Horizon releases](https://github.com/stellar/stellar-horiz
 
 Run `stellar-horizon --help` from a terminal. If the help for Horizon is displayed, your installation was successful.
 
-Some shells (such as [zsh](https://www.zsh.org/)) cache PATH lookups. You may need to clear your cache (by using `rehash` in zsh, for example) or restart your shell before trying to run the command above.
+Some shells (such as [zsh](https://www.zsh.org)) cache PATH lookups. You may need to clear your cache (by using `rehash` in zsh, for example) or restart your shell before trying to run the command above.
 
 #### Helm Chart Installation
 
-If the deployment can be done on Kubernetes, there is a [Horizon Helm Chart](https://github.com/stellar/helm-charts/blob/main/charts/horizon) available. Install the [Helm CLI tool](https://helm.sh/docs/intro/install/), if you haven't already on your workstation, minimum of version 3. Next, add the Stellar repo to the helm client's list of repos and confirm that you can view the list of available chart versions for the repo:
+If the deployment can be done on Kubernetes, there is a [Horizon Helm Chart](https://github.com/stellar/helm-charts/blob/main/charts/horizon) available. Install the [Helm CLI tool](https://helm.sh/docs/intro/install), if you haven't already on your workstation, minimum of version 3. Next, add the Stellar repo to the helm client's list of repos and confirm that you can view the list of available chart versions for the repo:
 
 <CodeExample>
 
diff --git a/docs/data/apis/horizon/admin-guide/monitoring.mdx b/docs/data/apis/horizon/admin-guide/monitoring.mdx
index a6e7930e97..3a330117ac 100644
--- a/docs/data/apis/horizon/admin-guide/monitoring.mdx
+++ b/docs/data/apis/horizon/admin-guide/monitoring.mdx
@@ -52,7 +52,7 @@ horizon_http_requests_duration_seconds{method="GET",route="/",status="200",strea
 
 ### Queries
 
-Build queries against the metrics data model to highlight the performance of a given Horizon deployment. Refer to Stellar's [Grafana Horizon Dashboard](https://grafana.com/grafana/dashboards/13793-stellar-horizon/) for examples of metrics queries to derive application performance:
+Build queries against the metrics data model to highlight the performance of a given Horizon deployment. Refer to Stellar's [Grafana Horizon Dashboard](https://grafana.com/grafana/dashboards/13793-stellar-horizon) for examples of metrics queries to derive application performance:
 
 - Number of requests per minute.
 - Number of requests per route (the most popular routes).
@@ -70,7 +70,7 @@ Choose the [revisions tab](https://grafana.com/grafana/dashboards/13793-stellar-
 
 ### Alerts
 
-Once queries are developed on a Grafana dashboard, it enables a convenient follow-on step to add [alert rules](https://grafana.com/docs/grafana/latest/alerting/alerting-rules/create-grafana-managed-rule/) based on specific queries to trigger notifications when thresholds are exceeded.
+Once queries are developed on a Grafana dashboard, it enables a convenient follow-on step to add [alert rules](https://grafana.com/docs/grafana/latest/alerting/alerting-rules/create-grafana-managed-rule) based on specific queries to trigger notifications when thresholds are exceeded.
 
 Here are some example alerts to consider with potential causes and solutions.
 
@@ -113,4 +113,4 @@ Entering interactive mode (type "help" for commands, "o" for options)
 
 ## I'm Stuck! Help!
 
-If any of the above steps don't work or you are otherwise prevented from correctly setting up Horizon, please join our community and let us know. Either post a question at [our Stack Exchange](https://stellar.stackexchange.com/) or chat with us on [Horizon Discord](https://discord.com/channels/897514728459468821/912466080960766012) to ask for help.
+If any of the above steps don't work or you are otherwise prevented from correctly setting up Horizon, please join our community and let us know. Either post a question at [our Stack Exchange](https://stellar.stackexchange.com) or chat with us on [Horizon Discord](https://discord.com/channels/897514728459468821/912466080960766012) to ask for help.
diff --git a/docs/data/apis/horizon/providers.mdx b/docs/data/apis/horizon/providers.mdx
index 953143aa0e..5ffe9a4b5f 100644
--- a/docs/data/apis/horizon/providers.mdx
+++ b/docs/data/apis/horizon/providers.mdx
@@ -16,10 +16,10 @@ These providers allow access to the Futurenet, Testnet and Mainnet network.
 | Provider | Futurenet | Testnet | Mainnet | Full History |
 | --- | --- | --- | --- | --- |
 | [Blockdaemon\*](https://www.blockdaemon.com/apply/soroban) | ❌ | ✅ | ✅ | ✅ |
-| [Validation Cloud\*](https://app.validationcloud.io/) | ❌ | ✅ | ✅ | ✅ |
+| [Validation Cloud\*](https://app.validationcloud.io) | ❌ | ✅ | ✅ | ✅ |
 | [QuickNode](https://www.quicknode.com/docs/stellar) | ❌ | ✅ | ✅ | ❌ |
-| [Ankr](https://www.ankr.com/rpc/advanced-api/) | ❌ | ✅ | ✅ | ❌ |
-| [Obsrvr](https://www.withObsrvr.com/) | ❌ | ✅ | ✅ | ❌ |
+| [Ankr](https://www.ankr.com/rpc/advanced-api) | ❌ | ✅ | ✅ | ❌ |
+| [Obsrvr](https://www.withObsrvr.com) | ❌ | ✅ | ✅ | ❌ |
 | [Nodies](https://nodies.org) | ❌ | ✅ | ✅ | ❌ |
 
 \*Blockdaemon and Validation Cloud provide full historical data for Horizon.
diff --git a/docs/data/apis/rpc/admin-guide/configuring.mdx b/docs/data/apis/rpc/admin-guide/configuring.mdx
index 00dec8b62b..b83557c69d 100644
--- a/docs/data/apis/rpc/admin-guide/configuring.mdx
+++ b/docs/data/apis/rpc/admin-guide/configuring.mdx
@@ -3,7 +3,7 @@ title: Configuring
 sidebar_position: 25
 ---
 
-For production, we recommend running Stellar RPC with a [TOML](https://toml.io/en/) configuration file rather than CLI flags. This is similar to creating a configuration file for Stellar-Core as we did previously. For example, using [our docker image](https://hub.docker.com/r/stellar/stellar-rpc):
+For production, we recommend running Stellar RPC with a [TOML](https://toml.io/en) configuration file rather than CLI flags. This is similar to creating a configuration file for Stellar-Core as we did previously. For example, using [our docker image](https://hub.docker.com/r/stellar/stellar-rpc):
 
 ```bash
 docker run -p 8001:8001 -p 8000:8000 \
@@ -241,7 +241,7 @@ Note that the above generated configuration contains the default values and you
 
 Then, you should create a configuration file for [Stellar Core](https://github.com/stellar/stellar-core). You can find sample configuration files for [Testnet](https://github.com/stellar/go-stellar-sdk/blob/main/ingest/ledgerbackend/configs/captive-core-testnet.cfg) and [Pubnet](https://github.com/stellar/go-stellar-sdk/blob/main/ingest/ledgerbackend/configs/captive-core-pubnet.cfg)
 
-When using docker, you should create and mount a volume [mount a volume](https://docs.docker.com/storage/volumes/) on your container where the above configuration is stored.
+When using docker, you should create and mount a volume [mount a volume](https://docs.docker.com/storage/volumes) on your container where the above configuration is stored.
 
 If you are running locally on a unix-style machine, you could create a folder in your home directory called `~/rpc-config`
 
diff --git a/docs/data/apis/rpc/admin-guide/monitoring.mdx b/docs/data/apis/rpc/admin-guide/monitoring.mdx
index 705814ff03..991276bbfd 100644
--- a/docs/data/apis/rpc/admin-guide/monitoring.mdx
+++ b/docs/data/apis/rpc/admin-guide/monitoring.mdx
@@ -3,7 +3,7 @@ title: Monitoring
 sidebar_position: 60
 ---
 
-If you run Stellar RPC with the `--admin-endpoint` configured and [expose the port](https://docs.docker.com/engine/reference/commandline/run/#publish), you'll have access to the [Prometheus](https://prometheus.io/) metrics via the `/metrics` endpoint. For example, if the admin endpoint is `0.0.0.0:8001` and you're running the Stellar RPC Docker image:
+If you run Stellar RPC with the `--admin-endpoint` configured and [expose the port](https://docs.docker.com/engine/reference/commandline/run/#publish), you'll have access to the [Prometheus](https://prometheus.io) metrics via the `/metrics` endpoint. For example, if the admin endpoint is `0.0.0.0:8001` and you're running the Stellar RPC Docker image:
 
 ```bash
 curl localhost:8001/metrics
@@ -33,7 +33,7 @@ time=<timestamp in YYYY-MM-DDTHH:MM:SS.000Z format> level=<debug|info|error> msg
 
 ## Grafana dashboard
 
-We provide a [Grafana dashboard](https://grafana.com/grafana/dashboards/19229-soroban-rpc/) with different metrics to monitor your RPC instance.
+We provide a [Grafana dashboard](https://grafana.com/grafana/dashboards/19229-soroban-rpc) with different metrics to monitor your RPC instance.
 
 ## Verify the RPC Instance
 
diff --git a/docs/data/apis/rpc/api-reference/methods/getEvents.mdx b/docs/data/apis/rpc/api-reference/methods/getEvents.mdx
index 093fac5731..9d7de6e1ba 100644
--- a/docs/data/apis/rpc/api-reference/methods/getEvents.mdx
+++ b/docs/data/apis/rpc/api-reference/methods/getEvents.mdx
@@ -12,7 +12,7 @@ import rpcSpec from "@site/static/stellar-rpc.openrpc.json";
 
 ### Using the Lab
 
-Let's test the example request for **Native XLM Transfer Events** directly on [the Stellar Laboratory](https://laboratory.stellar.org/).
+Let's test the example request for **Native XLM Transfer Events** directly on [the Stellar Laboratory](https://laboratory.stellar.org).
 
 The new Lab supports **sharable URLs** that prefill input fields based on query parameters. This makes it easy to share and revisit specific configurations.
 
diff --git a/docs/data/apis/rpc/api-reference/methods/getFeeStats.mdx b/docs/data/apis/rpc/api-reference/methods/getFeeStats.mdx
index b8bc052c09..26b6dcf1d8 100644
--- a/docs/data/apis/rpc/api-reference/methods/getFeeStats.mdx
+++ b/docs/data/apis/rpc/api-reference/methods/getFeeStats.mdx
@@ -12,7 +12,7 @@ import rpcSpec from "@site/static/stellar-rpc.openrpc.json";
 
 ### Using the Lab
 
-You can view the current **mainnet fee stats** using [`mainnet.sorobanrpc.com`](https://sorobanrpc.com), powered by Overcat's RPC service, directly in the [Stellar Laboratory](https://laboratory.stellar.org/).
+You can view the current **mainnet fee stats** using [`mainnet.sorobanrpc.com`](https://sorobanrpc.com), powered by Overcat's RPC service, directly in the [Stellar Laboratory](https://laboratory.stellar.org).
 
 👉 [View Mainnet Fee Stats on the Lab](https://lab.stellar.org/endpoints/rpc/get-fee-stats?$=network$id=mainnet&label=Mainnet&horizonUrl=https:////horizon.stellar.org&rpcUrl=https:////mainnet.sorobanrpc.com&passphrase=Public%20Global%20Stellar%20Network%20/;%20September%202015;;)
 
diff --git a/docs/data/apis/rpc/api-reference/methods/getHealth.mdx b/docs/data/apis/rpc/api-reference/methods/getHealth.mdx
index 44b4c88e5e..a57c582963 100644
--- a/docs/data/apis/rpc/api-reference/methods/getHealth.mdx
+++ b/docs/data/apis/rpc/api-reference/methods/getHealth.mdx
@@ -12,7 +12,7 @@ import rpcSpec from "@site/static/stellar-rpc.openrpc.json";
 
 ### Using the Lab
 
-You can check the **node health status** on both **Testnet** and **Mainnet** using the `getHealth` RPC method directly in the [Stellar Laboratory](https://laboratory.stellar.org/).
+You can check the **node health status** on both **Testnet** and **Mainnet** using the `getHealth` RPC method directly in the [Stellar Laboratory](https://laboratory.stellar.org).
 
 👉 [View Testnet Node Health on the Lab](https://lab.stellar.org/endpoints/rpc/get-health?$=network$id=testnet&label=Testnet&horizonUrl=https:////horizon-testnet.stellar.org&rpcUrl=https:////soroban-testnet.stellar.org&passphrase=Test%20SDF%20Network%20/;%20September%202015;;)
 
diff --git a/docs/data/apis/rpc/api-reference/methods/getLatestLedger.mdx b/docs/data/apis/rpc/api-reference/methods/getLatestLedger.mdx
index 8088ca9c9f..f68002218d 100644
--- a/docs/data/apis/rpc/api-reference/methods/getLatestLedger.mdx
+++ b/docs/data/apis/rpc/api-reference/methods/getLatestLedger.mdx
@@ -12,7 +12,7 @@ import rpcSpec from "@site/static/stellar-rpc.openrpc.json";
 
 ### Using the Lab
 
-You can check the **latest known ledger** on both **Testnet** and **Mainnet** using the `getLatestLedger` RPC method directly in the [Stellar Laboratory](https://laboratory.stellar.org/).
+You can check the **latest known ledger** on both **Testnet** and **Mainnet** using the `getLatestLedger` RPC method directly in the [Stellar Laboratory](https://laboratory.stellar.org).
 
 👉 [View Testnet Latest Ledger on the Lab](https://lab.stellar.org/endpoints/rpc/get-latest-ledger?$=network$id=testnet&label=Testnet&horizonUrl=https:////horizon-testnet.stellar.org&rpcUrl=https:////soroban-testnet.stellar.org&passphrase=Test%20SDF%20Network%20/;%20September%202015;;)
 
diff --git a/docs/data/apis/rpc/api-reference/methods/getLedgers.mdx b/docs/data/apis/rpc/api-reference/methods/getLedgers.mdx
index 049b364693..47d1696cc5 100644
--- a/docs/data/apis/rpc/api-reference/methods/getLedgers.mdx
+++ b/docs/data/apis/rpc/api-reference/methods/getLedgers.mdx
@@ -12,7 +12,7 @@ import rpcSpec from "@site/static/stellar-rpc.openrpc.json";
 
 ### Using the Lab
 
-You can retrieve a list of **past ledgers** using the `getLedgers` method in the [Stellar Laboratory](https://laboratory.stellar.org/). This endpoint returns detailed ledger data starting from a specified point, with support for pagination—as long as the requested range falls within the history retention of the RPC provider.
+You can retrieve a list of **past ledgers** using the `getLedgers` method in the [Stellar Laboratory](https://laboratory.stellar.org). This endpoint returns detailed ledger data starting from a specified point, with support for pagination—as long as the requested range falls within the history retention of the RPC provider.
 
 The method also supports an optional `XDR format` parameter, which allows developers to choose between **unpacked JSON** or **base64-encoded XDR strings** for the response format.
 
diff --git a/docs/data/apis/rpc/api-reference/methods/getNetwork.mdx b/docs/data/apis/rpc/api-reference/methods/getNetwork.mdx
index 8cd9b8a766..6809d381ce 100644
--- a/docs/data/apis/rpc/api-reference/methods/getNetwork.mdx
+++ b/docs/data/apis/rpc/api-reference/methods/getNetwork.mdx
@@ -12,7 +12,7 @@ import rpcSpec from "@site/static/stellar-rpc.openrpc.json";
 
 ### Using the Lab
 
-You can check **general information about the currently configured network** on both **Testnet** and **Mainnet** using the `getNetwork` RPC method directly in the [Stellar Laboratory](https://laboratory.stellar.org/).
+You can check **general information about the currently configured network** on both **Testnet** and **Mainnet** using the `getNetwork` RPC method directly in the [Stellar Laboratory](https://laboratory.stellar.org).
 
 👉 [View Testnet getNetwork on the Lab](https://lab.stellar.org/endpoints/rpc/get-network?$=network$id=testnet&label=Testnet&horizonUrl=https:////horizon-testnet.stellar.org&rpcUrl=https:////soroban-testnet.stellar.org&passphrase=Test%20SDF%20Network%20/;%20September%202015;;)
 
diff --git a/docs/data/apis/rpc/api-reference/methods/getTransaction.mdx b/docs/data/apis/rpc/api-reference/methods/getTransaction.mdx
index 7fcdac6dbb..3106513395 100644
--- a/docs/data/apis/rpc/api-reference/methods/getTransaction.mdx
+++ b/docs/data/apis/rpc/api-reference/methods/getTransaction.mdx
@@ -77,7 +77,7 @@ public class GetTransactionExample {
 
 ### Using the Lab
 
-You can use the `getTransaction` method in the [Stellar Laboratory](https://laboratory.stellar.org/) to **retrieve details about a specific transaction**. This is especially useful for checking the status of a transaction to determine whether it has been successfully recorded on the blockchain.
+You can use the `getTransaction` method in the [Stellar Laboratory](https://laboratory.stellar.org) to **retrieve details about a specific transaction**. This is especially useful for checking the status of a transaction to determine whether it has been successfully recorded on the blockchain.
 
 The **default transaction history retention window** in `stellar-rpc` is **24 hours**, but this can be adjusted (up to 7 days) for private Soroban RPC instances using the `transaction-retention-window` configuration setting. For transaction debugging beyond that window, consider indexing the data yourself, using a third-party indexer, or querying **Hubble**—Stellar’s public BigQuery dataset.
 
diff --git a/docs/data/apis/rpc/api-reference/methods/getTransactions.mdx b/docs/data/apis/rpc/api-reference/methods/getTransactions.mdx
index cfc41adf05..474e247160 100644
--- a/docs/data/apis/rpc/api-reference/methods/getTransactions.mdx
+++ b/docs/data/apis/rpc/api-reference/methods/getTransactions.mdx
@@ -14,7 +14,7 @@ import rpcSpec from "@site/static/stellar-rpc.openrpc.json";
 
 The `getTransactions` method returns a **paginated list of transactions** starting from a user-defined point. You can continue paginating through results as long as the requested range falls within the **history retention window** of the corresponding RPC provider.
 
-Use this method in the [Stellar Laboratory](https://laboratory.stellar.org/) to explore recent activity within a given time frame or ledger range.
+Use this method in the [Stellar Laboratory](https://laboratory.stellar.org) to explore recent activity within a given time frame or ledger range.
 
 👉 [View Transactions on the Lab](https://lab.stellar.org/endpoints/rpc/get-transactions?$=network$id=testnet&label=Testnet&horizonUrl=https:////horizon-testnet.stellar.org&rpcUrl=https:////soroban-testnet.stellar.org&passphrase=Test%20SDF%20Network%20/;%20September%202015;&endpoints$params$startLedger=573331;;)
 
diff --git a/docs/data/apis/rpc/providers.mdx b/docs/data/apis/rpc/providers.mdx
index c98ce99fa0..03594bf2b6 100644
--- a/docs/data/apis/rpc/providers.mdx
+++ b/docs/data/apis/rpc/providers.mdx
@@ -10,17 +10,17 @@ These providers allow access to the Futurenet, Testnet and Mainnet network.
 | Provider | Futurenet | Testnet | Mainnet | Dedicated Nodes | RPC Archive |
 | --- | --- | --- | --- | --- | --- |
 | [Blockdaemon](https://www.blockdaemon.com/apply/soroban) | ❌ | ✅ | ✅ | ✅ | ❌ |
-| [Validation Cloud](https://app.validationcloud.io/) | ❌ | ✅ | ✅ | ❌ | ❌ |
+| [Validation Cloud](https://app.validationcloud.io) | ❌ | ✅ | ✅ | ❌ | ❌ |
 | [QuickNode](https://www.quicknode.com/docs/stellar) | ❌ | ✅ | ✅ | ✅ | ❌ |
 | [NowNodes](https://nownodes.io/nodes/stellar-xlm) | ✅ | ✅ | ✅ | ✅ | ❌ |
-| [Gateway\*](https://gateway.fm/public-rpc/) | ❌ | ✅ | ✅ | ✅ | ✅ |
-| [Ankr](https://www.ankr.com/rpc/stellar/) | ❌ | ✅ | ✅ | ❌ | ✅ |
-| [Infstones](https://infstones.com/) | ❌ | ❌ | ✅ | ✅ | ❌ |
-| [Obsrvr\*](https://www.withObsrvr.com/) | ❌ | ✅ | ✅ | ❌ | ✅ |
+| [Gateway\*](https://gateway.fm/public-rpc) | ❌ | ✅ | ✅ | ✅ | ✅ |
+| [Ankr](https://www.ankr.com/rpc/stellar) | ❌ | ✅ | ✅ | ❌ | ✅ |
+| [Infstones](https://infstones.com) | ❌ | ❌ | ✅ | ✅ | ❌ |
+| [Obsrvr\*](https://www.withObsrvr.com) | ❌ | ✅ | ✅ | ❌ | ✅ |
 | [Nodies](https://nodies.org) | ❌ | ✅ | ✅ | ❌ | ❌ |
 | [OnFinality\*](https://onfinality.io/networks/stellar) | ❌ | ❌ | ✅ | ✅ | ✅ |
-| [Lightsail Network - Quasar\*](https://quasar.lightsail.network/) | ❌ | ❌ | ✅ | ❌ | ✅ |
-| [Uniblock](https://www.uniblock.dev/) | ❌ | ✅ | ✅ | ❌ | ❌ |
+| [Lightsail Network - Quasar\*](https://quasar.lightsail.network) | ❌ | ❌ | ✅ | ❌ | ✅ |
+| [Uniblock](https://www.uniblock.dev) | ❌ | ✅ | ✅ | ❌ | ❌ |
 | [Exaion](https://crypto.exaion.com) | ❌ | ❌ | ✅ | ✅ | ✅ |
 | [Alchemy](https://dashboard.alchemy.com/?utm_source=chain_partner&utm_medium=referral&utm_campaign=stellar) | ❌ | ✅ | ✅ | ✅ | ❌ |
 
@@ -32,17 +32,17 @@ _The "Dedicated Nodes" column represents providers who host full nodes as a serv
 
 | Provider | Network | URL |
 | --- | --- | --- |
-| [Liquify](https://www.liquify.io/) | Futurenet | RPC: `https://stellar.liquify.com/api=41EEWAH79Y5OCGI7/futurenet` |
+| [Liquify](https://www.liquify.io) | Futurenet | RPC: `https://stellar.liquify.com/api=41EEWAH79Y5OCGI7/futurenet` |
 |  | Testnet | RPC: `https://stellar.liquify.com/api=41EEWAH79Y5OCGI7/testnet` |
 |  | Mainnet | RPC: `https://stellar-mainnet.liquify.com/api=41EEWAH79Y5OCGI7/mainnet` |
-| [Gateway](https://gateway.fm/) | Testnet | RPC: `https://soroban-rpc.testnet.stellar.gateway.fm` |
+| [Gateway](https://gateway.fm) | Testnet | RPC: `https://soroban-rpc.testnet.stellar.gateway.fm` |
 |  | Mainnet | RPC: `https://soroban-rpc.mainnet.stellar.gateway.fm` |
-| [sorobanrpc.com](https://sorobanrpc.com/) | Mainnet | RPC: `https://mainnet.sorobanrpc.com` |
+| [sorobanrpc.com](https://sorobanrpc.com) | Mainnet | RPC: `https://mainnet.sorobanrpc.com` |
 | [Nodies](https://nodies.org) | Testnet | RPC: `https://stellar-soroban-testnet-public.nodies.app` |
 |  | Mainnet | RPC: `https://stellar-soroban-public.nodies.app` |
 | [SDF](http://www.stellar.org) | Futurenet | RPC: `https://rpc-futurenet.stellar.org` |
 |  | Testnet | RPC: `https://soroban-testnet.stellar.org` |
 | [OnFinality](https://onfinality.io/networks/stellar) | Mainnet | RPC: `https://stellar.api.onfinality.io/public` |
-| [Lightsail Network - Quasar](https://quasar.lightsail.network/) | Mainnet | RPC `https://rpc.lightsail.network/` |
+| [Lightsail Network - Quasar](https://quasar.lightsail.network) | Mainnet | RPC `https://rpc.lightsail.network/` |
 |  | Mainnet | Full Archive RPC: `https://archive-rpc.lightsail.network/` |
-| [Ankr](https://www.ankr.com/rpc/stellar/) | Mainnet | Full Archive RPC `https://rpc.ankr.com/stellar_soroban` |
+| [Ankr](https://www.ankr.com/rpc/stellar) | Mainnet | Full Archive RPC `https://rpc.ankr.com/stellar_soroban` |
diff --git a/docs/data/indexers/README.mdx b/docs/data/indexers/README.mdx
index 817513a0bf..a20f240a89 100644
--- a/docs/data/indexers/README.mdx
+++ b/docs/data/indexers/README.mdx
@@ -44,7 +44,7 @@ Consider again the NFT example. Wouldn't it be great to return all needed NFT da
 Well-known options:
 
 - [The Graph]: one of the earliest and most popular-at-the-time options on Ethereum. They now offer three main products:
-  1. [Subgraphs](https://thegraph.com/docs/en/subgraphs/developing/subgraphs/): their main & most famous offering, providing a [decentralized approach](https://thegraph.com/docs/en/subgraphs/developing/publishing/publishing-a-subgraph/) to custom data transformation & hosting. The Graph's use of GraphQL APIs made GraphQL a popular choice for this entire category of indexing.
+  1. [Subgraphs](https://thegraph.com/docs/en/subgraphs/developing/subgraphs): their main & most famous offering, providing a [decentralized approach](https://thegraph.com/docs/en/subgraphs/developing/publishing/publishing-a-subgraph) to custom data transformation & hosting. The Graph's use of GraphQL APIs made GraphQL a popular choice for this entire category of indexing.
   2. **Token API**, for Indexing [Use Case #1](#portfolio-apis) described above
   3. **Substreams**, for [Use Case #3](#analytics) described below
 
diff --git a/docs/data/indexers/build-your-own/galexie/admin_guide/installing.mdx b/docs/data/indexers/build-your-own/galexie/admin_guide/installing.mdx
index 9d83f777d8..1678882975 100644
--- a/docs/data/indexers/build-your-own/galexie/admin_guide/installing.mdx
+++ b/docs/data/indexers/build-your-own/galexie/admin_guide/installing.mdx
@@ -12,7 +12,7 @@ In order to install Galexie into a kubernetes cluster follow these steps:
 - Run `helm repo add stellar https://helm.stellar.org/charts`
 - Run `helm install <RELEASE_NAME> stellar/galexie --set datastore.params.path=<FULL_PATH_TO_GALEXIE_OBJECTS>`
 
-Additional configuration can be set with the `--set` flags or by using a [helm values file](https://helm.sh/docs/chart_template_guide/values_files/) with the chart.
+Additional configuration can be set with the `--set` flags or by using a [helm values file](https://helm.sh/docs/chart_template_guide/values_files) with the chart.
 
 ## Install Container on a host
 
diff --git a/docs/data/indexers/build-your-own/galexie/admin_guide/monitoring.mdx b/docs/data/indexers/build-your-own/galexie/admin_guide/monitoring.mdx
index f1b7941890..564d28b77d 100644
--- a/docs/data/indexers/build-your-own/galexie/admin_guide/monitoring.mdx
+++ b/docs/data/indexers/build-your-own/galexie/admin_guide/monitoring.mdx
@@ -38,7 +38,7 @@ Use these metrics to build queries that monitor Galexie’s performance and expo
 - Queue Length: Use `galexie_upload_queue_length` to view the number of objects waiting to be uploaded.
 - Latest Exported Ledger: Track `galexie_last_exported_ledger` to ensure that ledger exports are up-to-date.
 
-For a quick start, download our pre-built Grafana dashboard for Galexie [here](https://grafana.com/grafana/dashboards/22285-stellar-galexie/). This dashboard provides pre-configured queries and visualizations to help you monitor Galexie's health. You can customize it to fit your specific needs.
+For a quick start, download our pre-built Grafana dashboard for Galexie [here](https://grafana.com/grafana/dashboards/22285-stellar-galexie). This dashboard provides pre-configured queries and visualizations to help you monitor Galexie's health. You can customize it to fit your specific needs.
 
 ### Logging
 
diff --git a/docs/data/indexers/build-your-own/galexie/admin_guide/prerequisites.mdx b/docs/data/indexers/build-your-own/galexie/admin_guide/prerequisites.mdx
index a5b29940e9..311c9a978b 100644
--- a/docs/data/indexers/build-your-own/galexie/admin_guide/prerequisites.mdx
+++ b/docs/data/indexers/build-your-own/galexie/admin_guide/prerequisites.mdx
@@ -28,7 +28,7 @@ Galexie exports Stellar ledger metadata to Google Cloud Storage (GCS) or Amazon
 ### Running the Galexie Container on an Instance
 
 - Instance like AWS EC2 or GCP VM
-- Any host machine with a OCI complaint container runtime installed like Docker ([Docker installation guide](https://docs.docker.com/engine/install/)).
+- Any host machine with a OCI complaint container runtime installed like Docker ([Docker installation guide](https://docs.docker.com/engine/install)).
 
 > **_NOTE:_** While it is possible to natively install Galexie (without a container runtime), this requires manual dependency management and is recommended only for advanced users.
 
diff --git a/docs/data/indexers/build-your-own/galexie/admin_guide/setup.mdx b/docs/data/indexers/build-your-own/galexie/admin_guide/setup.mdx
index e02b2e5f07..1d1f2f8719 100644
--- a/docs/data/indexers/build-your-own/galexie/admin_guide/setup.mdx
+++ b/docs/data/indexers/build-your-own/galexie/admin_guide/setup.mdx
@@ -55,7 +55,7 @@ When using GCP IAM to authenticate Galexie to access a bucket, the following per
 
 If you already have an S3 bucket ready for Galexie to push data, you can skip this section. If not, follow these steps:
 
-1. Visit the AWS Console's Storage section (https://console.aws.amazon.com/s3/) and create a new bucket.
+1. Visit the AWS Console's Storage section (https://console.aws.amazon.com/s3) and create a new bucket.
 2. Choose a descriptive name for the bucket, such as `stellar-ledger-data`. Refer to [S3 General purpose bucket naming rules](https://cloud.google.com/storage/docs/buckets#naming) for bucket naming conventions. Note down the bucket name, you will need it later during the configuration process.
 
 ### Amazon Web Services (AWS) Authentication
diff --git a/docs/data/indexers/build-your-own/galexie/providers.mdx b/docs/data/indexers/build-your-own/galexie/providers.mdx
index 5bc79f9ba1..1229460b1c 100644
--- a/docs/data/indexers/build-your-own/galexie/providers.mdx
+++ b/docs/data/indexers/build-your-own/galexie/providers.mdx
@@ -9,8 +9,8 @@ These providers allow access to the Futurenet, Testnet and Mainnet network.
 
 | Provider | Futurenet | Testnet | Mainnet | URI |
 | --- | --- | --- | --- | --- |
-| [AWS Public Blockchain\*](https://registry.opendata.aws/aws-public-blockchain/) | ❌ | ✅ | ✅ | `s3://aws-public-blockchain/v1.1/stellar/ledgers/` |
-| [Lightsail Network - Quasar](https://quasar.lightsail.network/) | ❌ | ❌ | ✅ | `https://galexie.lightsail.network/v1/` |
+| [AWS Public Blockchain\*](https://registry.opendata.aws/aws-public-blockchain) | ❌ | ✅ | ✅ | `s3://aws-public-blockchain/v1.1/stellar/ledgers/` |
+| [Lightsail Network - Quasar](https://quasar.lightsail.network) | ❌ | ❌ | ✅ | `https://galexie.lightsail.network/v1/` |
 
 \*AWS Public Blockchain populated by Goldsky
 
diff --git a/docs/data/oracles/oracle-providers.mdx b/docs/data/oracles/oracle-providers.mdx
index aa4f8d6f87..17feb0cbf9 100644
--- a/docs/data/oracles/oracle-providers.mdx
+++ b/docs/data/oracles/oracle-providers.mdx
@@ -37,7 +37,7 @@ Publicly availble free price oracles are compatible with [SEP40](https://github.
 | [`CCYOZJCOPG34LLQQ7N24YXBM7LL62R7ONMZ3G6WZAAYPB5OYKOMJRN63`](https://stellar.expert/explorer/testnet/contract/CCYOZJCOPG34LLQQ7N24YXBM7LL62R7ONMZ3G6WZAAYPB5OYKOMJRN63) | External CEXs & DEXs | Testnet |
 | [`CCSSOHTBL3LEWUCBBEB5NJFC2OKFRC74OWEIJIZLRJBGAAU4VMU5NV4W`](https://stellar.expert/explorer/testnet/contract/CCSSOHTBL3LEWUCBBEB5NJFC2OKFRC74OWEIJIZLRJBGAAU4VMU5NV4W) | Fiat exchange rates | Testnet |
 
-## [Band](https://www.bandprotocol.com/)
+## [Band](https://www.bandprotocol.com)
 
 Band is a cross-chain data oracle aggregating and connecting real-world data and APIs to smart contracts.
 
@@ -50,9 +50,9 @@ The network is designed to modularize and offload the task of constatly monitori
 | [`CCQXWMZVM3KRTXTUPTN53YHL272QGKF32L7XEDNZ2S6OSUFK3NFBGG5M`](https://stellar.expert/explorer/public/contract/CCQXWMZVM3KRTXTUPTN53YHL272QGKF32L7XEDNZ2S6OSUFK3NFBGG5M) | Mainnet |
 | [`CBRV5ZEQSSCQ4FFO64OF46I3UASBVEJNE5C2MCFWVIXL4Z7DMD7PJJMF`](https://stellar.expert/explorer/testnet/contract/CBRV5ZEQSSCQ4FFO64OF46I3UASBVEJNE5C2MCFWVIXL4Z7DMD7PJJMF) | Testnet |
 
-To learn more about this oracle, please see their [docs](https://docs.bandchain.org/) or visit their [GitHub](https://github.com/bandprotocol/band-std-reference-contracts-soroban).
+To learn more about this oracle, please see their [docs](https://docs.bandchain.org) or visit their [GitHub](https://github.com/bandprotocol/band-std-reference-contracts-soroban).
 
-## [DIA Oracles](https://www.diadata.org/)
+## [DIA Oracles](https://www.diadata.org)
 
 [DIA](https://www.diadata.org) is a cross-chain, trustless oracle network that delivers verifiable price feeds. dApps on Stellar can consume these feeds from DIA's deployed contracts. DIA sources raw trade data directly from primary markets and supplies aggregated values on-chain, ensuring transparency and data integrity.
 
@@ -77,9 +77,9 @@ The DIA oracle on Stellar includes price feeds for the following assets:
 
 | Asset | Blockchain | Address | Markets Overview |
 | --- | --- | --- | --- |
-| USDC | Ethereum | 0xA0b86991c6218b36c1d19D4a2e9Eb0cE3606eB48 | [USDC Markets](https://www.diadata.org/app/price/asset/Ethereum/0xA0b86991c6218b36c1d19D4a2e9Eb0cE3606eB48/) |
-| BTC | Bitcoin | 0x0000000000000000000000000000000000000000 | [BTC Markets](https://www.diadata.org/app/price/asset/Bitcoin/0x0000000000000000000000000000000000000000/) |
-| DIA | Ethereum | 0x84cA8bc7997272c7CfB4D0Cd3D55cd942B3c9419 | [DIA Markets](https://www.diadata.org/app/price/asset/Ethereum/0x84cA8bc7997272c7CfB4D0Cd3D55cd942B3c9419/) |
+| USDC | Ethereum | 0xA0b86991c6218b36c1d19D4a2e9Eb0cE3606eB48 | [USDC Markets](https://www.diadata.org/app/price/asset/Ethereum/0xA0b86991c6218b36c1d19D4a2e9Eb0cE3606eB48) |
+| BTC | Bitcoin | 0x0000000000000000000000000000000000000000 | [BTC Markets](https://www.diadata.org/app/price/asset/Bitcoin/0x0000000000000000000000000000000000000000) |
+| DIA | Ethereum | 0x84cA8bc7997272c7CfB4D0Cd3D55cd942B3c9419 | [DIA Markets](https://www.diadata.org/app/price/asset/Ethereum/0x84cA8bc7997272c7CfB4D0Cd3D55cd942B3c9419) |
 
 ### Request a Custom Oracle
 
diff --git a/docs/learn/fundamentals/contract-development/contract-interactions/stellar-transaction.mdx b/docs/learn/fundamentals/contract-development/contract-interactions/stellar-transaction.mdx
index c938b71eb0..bc08835bbe 100644
--- a/docs/learn/fundamentals/contract-development/contract-interactions/stellar-transaction.mdx
+++ b/docs/learn/fundamentals/contract-development/contract-interactions/stellar-transaction.mdx
@@ -149,7 +149,7 @@ npm install --save @stellar/stellar-sdk
 
 :::tip
 
-The [`py-stellar-base`](https://stellar-sdk.readthedocs.io/en/soroban/) Python SDK has stable support for interacting with Soroban smart contracts as of [v9.0.0](https://github.com/StellarCN/py-stellar-base/releases/tag/9.0.0).
+The [`py-stellar-base`](https://stellar-sdk.readthedocs.io/en/soroban) Python SDK has stable support for interacting with Soroban smart contracts as of [v9.0.0](https://github.com/StellarCN/py-stellar-base/releases/tag/9.0.0).
 
 ```bash
 pip install stellar-sdk
diff --git a/docs/learn/fundamentals/contract-development/contract-interactions/tests.mdx b/docs/learn/fundamentals/contract-development/contract-interactions/tests.mdx
index 68211d97d2..688a4beecc 100644
--- a/docs/learn/fundamentals/contract-development/contract-interactions/tests.mdx
+++ b/docs/learn/fundamentals/contract-development/contract-interactions/tests.mdx
@@ -15,7 +15,7 @@ pub fn register_test_contract(e: &Env, contract_id: &[u8; 32]) {
 }
 ```
 
-Some contracts, such as the token contract, also provide a [friendlier interface](https://github.com/stellar/soroban-token-contract/blob/42380647bb817bf01c739c19286f18be881e0e41/src/testutils.rs#L26-L191) to facilitate testing. There are many ways these interfaces might make testing easier, but one common one is to allow automatic message signing by passing a [ed25519_dalek::Keypair](https://docs.rs/ed25519-dalek/latest/ed25519_dalek/).
+Some contracts, such as the token contract, also provide a [friendlier interface](https://github.com/stellar/soroban-token-contract/blob/42380647bb817bf01c739c19286f18be881e0e41/src/testutils.rs#L26-L191) to facilitate testing. There are many ways these interfaces might make testing easier, but one common one is to allow automatic message signing by passing a [ed25519_dalek::Keypair](https://docs.rs/ed25519-dalek/latest/ed25519_dalek).
 
 Note that everything described in this section is only available if the `testutils` feature is enabled.
 
diff --git a/docs/learn/fundamentals/contract-development/contract-interactions/transaction-simulation.mdx b/docs/learn/fundamentals/contract-development/contract-interactions/transaction-simulation.mdx
index 66d1f82510..6a3ef6616c 100644
--- a/docs/learn/fundamentals/contract-development/contract-interactions/transaction-simulation.mdx
+++ b/docs/learn/fundamentals/contract-development/contract-interactions/transaction-simulation.mdx
@@ -46,7 +46,7 @@ From a developer's perspective, the difference between these is whether or not a
 
 ### SDK Usage
 
-Below, we'll demonstrate the various ways in which you can invoke transaction simulation as well as highlight some utilities available in the [TypeScript SDK](https://stellar.github.io/js-stellar-sdk/) for authorization.
+Below, we'll demonstrate the various ways in which you can invoke transaction simulation as well as highlight some utilities available in the [TypeScript SDK](https://stellar.github.io/js-stellar-sdk) for authorization.
 
 We'll cover three types of invocations:
 
diff --git a/docs/learn/fundamentals/contract-development/errors-and-debugging/debugging.mdx b/docs/learn/fundamentals/contract-development/errors-and-debugging/debugging.mdx
index ef96c185fd..1921a75911 100644
--- a/docs/learn/fundamentals/contract-development/errors-and-debugging/debugging.mdx
+++ b/docs/learn/fundamentals/contract-development/errors-and-debugging/debugging.mdx
@@ -33,7 +33,7 @@ This configuration is referred to as **"local-testing mode"** and since it elimi
 - Tests can use numerous standard testing and debugging techniques:
   - [The standard Rust `#[test]` harness](https://doc.rust-lang.org/reference/attributes/testing.html), including push-button IDE support for running and re-running single tests.
   - [Standard IDE-supported debuggers](https://code.visualstudio.com/docs/languages/rust#_debugging), including IDE support for setting breakpoints and inspecting values in both contract and host.
-  - Lightweight debugging via [standard logging](https://docs.rs/log/latest/log/) or [tracing](https://docs.rs/tracing/latest/tracing/).
+  - Lightweight debugging via [standard logging](https://docs.rs/log/latest/log) or [tracing](https://docs.rs/tracing/latest/tracing).
   - Systematic testing such as [fuzzing](https://crates.io/crates/cargo-fuzz), [property-testing](https://crates.io/crates/proptest), or even [model checking](https://crates.io/crates/kani-verifier) or [formal verification](https://github.com/xldenis/creusot).
   - The simplest of all debugging approaches, [printing to standard error](https://doc.rust-lang.org/std/macro.eprintln.html).
 
diff --git a/docs/learn/fundamentals/contract-development/rust-dialect.mdx b/docs/learn/fundamentals/contract-development/rust-dialect.mdx
index 17d9a7d63d..8324cfe51e 100644
--- a/docs/learn/fundamentals/contract-development/rust-dialect.mdx
+++ b/docs/learn/fundamentals/contract-development/rust-dialect.mdx
@@ -34,7 +34,7 @@ The guest does, however, have a small linear memory available to it in cases whe
 
 This restriction is due to the limited ability of Wasm to support code-sharing: there is no standard way for the Wasm sandbox to provide shared "standard library" code within a guest, such as a memory allocator, nor does the host have adequate insight into the contents of the guest's memory to provide an allocator itself. Every contract that wishes to use dynamic allocation must therefore carry its own copy of an allocator.
 
-Many instances where dynamic memory allocation might _seem_ to be required can also be addressed just as well with a library such as [heapless](https://docs.rs/heapless/latest/heapless/). This library (and others of its kind) provide data structures with familiar APIs that _appear_ dynamic, but are actually implemented in terms of a single stack or static allocation, with a fixed maximum size established at construction: attempts to grow the dynamic size beyond the maximum size simply fail. In the context of a contract, this can sometimes be preferable behavior, and avoids the question of dynamic allocation entirely.
+Many instances where dynamic memory allocation might _seem_ to be required can also be addressed just as well with a library such as [heapless](https://docs.rs/heapless/latest/heapless). This library (and others of its kind) provide data structures with familiar APIs that _appear_ dynamic, but are actually implemented in terms of a single stack or static allocation, with a fixed maximum size established at construction: attempts to grow the dynamic size beyond the maximum size simply fail. In the context of a contract, this can sometimes be preferable behavior, and avoids the question of dynamic allocation entirely.
 
 ## Non-standard I/O
 
diff --git a/docs/learn/fundamentals/contract-development/types/fully-typed-contracts.mdx b/docs/learn/fundamentals/contract-development/types/fully-typed-contracts.mdx
index 57442c832d..bfd616bd33 100644
--- a/docs/learn/fundamentals/contract-development/types/fully-typed-contracts.mdx
+++ b/docs/learn/fundamentals/contract-development/types/fully-typed-contracts.mdx
@@ -21,7 +21,7 @@ sidebar_label: Fully-Typed Contracts
   />
 </head>
 
-When you compile a contract created with [soroban-sdk](../../../../tools/sdks/contract-sdks.mdx#soroban-rust-sdk), the Wasm file ends up with a [custom section](https://webassembly.github.io/spec/core/appendix/custom.html) containing a machine-readable description of your contract's interface types, sometimes called its [spec](https://github.com/stellar/rs-soroban-sdk/tree/main/soroban-spec) or its [API](https://github.com/stellar/soroban-docs/pull/381#issuecomment-1507283476). This is similar to [ABIs](https://www.quicknode.com/guides/ethereum-development/smart-contracts/what-is-an-abi/) in Ethereum, except that Soroban will store every single one of them on-chain from day one, and they include comments from the contract's author.
+When you compile a contract created with [soroban-sdk](../../../../tools/sdks/contract-sdks.mdx#soroban-rust-sdk), the Wasm file ends up with a [custom section](https://webassembly.github.io/spec/core/appendix/custom.html) containing a machine-readable description of your contract's interface types, sometimes called its [spec](https://github.com/stellar/rs-soroban-sdk/tree/main/soroban-spec) or its [API](https://github.com/stellar/soroban-docs/pull/381#issuecomment-1507283476). This is similar to [ABIs](https://www.quicknode.com/guides/ethereum-development/smart-contracts/what-is-an-abi) in Ethereum, except that Soroban will store every single one of them on-chain from day one, and they include comments from the contract's author.
 
 These interface types are formatted using [XDR](../../../fundamentals/data-format/xdr.mdx), a data format used widely throughout Stellar. It can be tricky to create or consume XDR manually, but tooling can fetch these interface types to make your life easier. [Stellar CLI](../../../../tools/cli/README.mdx#cli) and [Stellar SDK](../../../../tools/sdks/client-sdks.mdx#javascript-sdk) are two such tools to do so. Let's look at each.
 
diff --git a/docs/learn/fundamentals/data-format/xdr.mdx b/docs/learn/fundamentals/data-format/xdr.mdx
index f1f0a2c800..02fae85c2f 100644
--- a/docs/learn/fundamentals/data-format/xdr.mdx
+++ b/docs/learn/fundamentals/data-format/xdr.mdx
@@ -31,7 +31,7 @@ The XDR data is still included (encoded as a base64 string) inside the JSON in c
 
 ## Digging into XDR structures
 
-Since the XDR format is a fundamental underpinning of the Stellar Network, we often find it necessary to dig into these raw binary data structures for clients to interact with things like transactions and authorization entries. It can be hard to understand because of its structure, but this section will aim to enlighten you on the ways to interact with it in a handful of popular languages. The Protocol's schema is defined in the [`stellar/stellar-xdr`](https://github.com/stellar/stellar-xdr/) repository, though that contains far more than what we'll need for our purposes.
+Since the XDR format is a fundamental underpinning of the Stellar Network, we often find it necessary to dig into these raw binary data structures for clients to interact with things like transactions and authorization entries. It can be hard to understand because of its structure, but this section will aim to enlighten you on the ways to interact with it in a handful of popular languages. The Protocol's schema is defined in the [`stellar/stellar-xdr`](https://github.com/stellar/stellar-xdr) repository, though that contains far more than what we'll need for our purposes.
 
 ### XDR's Common Forms
 
diff --git a/docs/learn/fundamentals/lumens.mdx b/docs/learn/fundamentals/lumens.mdx
index 669ba49b08..b8f702bad7 100644
--- a/docs/learn/fundamentals/lumens.mdx
+++ b/docs/learn/fundamentals/lumens.mdx
@@ -82,11 +82,11 @@ Adding this number to the Original Supply, you get the total lumens that have ev
 
 **burnedLumens** These are all the lumens sent to accounts with no signers, meaning the funds are inaccessible and have been removed forever from Stellar’s lumen supply.
 
-While any address with no signers is counted here, the vast majority of the lumens in this sum are in a single locked address. On November 4, 2019, SDF [reduced](https://www.stellar.org/blog/sdfs-next-steps/) its lumen holdings to better reflect its mission and the growth of the Stellar ecosystem. To do so, the Foundation sent 55,442,095,285.7418 lumens to [GALA…LUTO](https://stellar.expert/explorer/public/account/GALAXYVOIDAOPZTDLHILAJQKCVVFMD4IKLXLSZV5YHO7VY74IWZILUTO).
+While any address with no signers is counted here, the vast majority of the lumens in this sum are in a single locked address. On November 4, 2019, SDF [reduced](https://www.stellar.org/blog/sdfs-next-steps) its lumen holdings to better reflect its mission and the growth of the Stellar ecosystem. To do so, the Foundation sent 55,442,095,285.7418 lumens to [GALA…LUTO](https://stellar.expert/explorer/public/account/GALAXYVOIDAOPZTDLHILAJQKCVVFMD4IKLXLSZV5YHO7VY74IWZILUTO).
 
 **totalSupply** The Total Supply is the number of lumens now in existence: 50,001,803,905.97172. The Total Supply includes four major categories of lumens, which the API treats in detail.
 
-**upgradeReserve** The Upgrade Reserve is a special address that’s neither circulating nor a part of SDF’s mandate. When Stellar [changed its consensus algorithm](https://www.stellar.org/blog/upgraded-network-is-here/) in 2015 and relaunched the network these lumens were set aside, to be claimed, one-for-one, by holders of the old network tokens. The [Upgrade Reserve account](https://stellar.expert/explorer/public/account/GBEZOC5U4TVH7ZY5N3FLYHTCZSI6VFGTULG7PBITLF5ZEBPJXFT46YZM) is essentially an escrow, and we don’t expect many claimants to come and pull those lumens into the circulating supply at this point.
+**upgradeReserve** The Upgrade Reserve is a special address that’s neither circulating nor a part of SDF’s mandate. When Stellar [changed its consensus algorithm](https://www.stellar.org/blog/upgraded-network-is-here) in 2015 and relaunched the network these lumens were set aside, to be claimed, one-for-one, by holders of the old network tokens. The [Upgrade Reserve account](https://stellar.expert/explorer/public/account/GBEZOC5U4TVH7ZY5N3FLYHTCZSI6VFGTULG7PBITLF5ZEBPJXFT46YZM) is essentially an escrow, and we don’t expect many claimants to come and pull those lumens into the circulating supply at this point.
 
 **feePool** The Fee Pool is where network fees collect. The lumens do not belong to any particular account. No one has access to the fee pool, so these lumens are non-circulating. Network validators could theoretically vote for a protocol change that would affect the fee pool, so we include it in the total supply. Stellar’s transaction fees are extremely low so the fee pool grows very slowly. The Fee Pool is tracked by the protocol itself, and the current number is visible on the [List All Ledgers](../../data/apis/horizon/api-reference/list-all-ledgers.api.mdx) Horizon API endpoint as `_embedded.records.fee_pool`. See all Stellar Mainnet Horizon data providers [here](../../data/apis/horizon/providers.mdx).
 
diff --git a/docs/learn/fundamentals/transactions/signatures-multisig.mdx b/docs/learn/fundamentals/transactions/signatures-multisig.mdx
index 0b1ba943e7..c38f5dd40c 100644
--- a/docs/learn/fundamentals/transactions/signatures-multisig.mdx
+++ b/docs/learn/fundamentals/transactions/signatures-multisig.mdx
@@ -58,7 +58,7 @@ Hash(x) signing is a different concept from transaction hashes. Transaction hash
 
 :::
 
-Adding a signature of type hash(x) allows anyone who knows x to sign the transaction. This type of signer is especially useful in [atomic cross-chain swaps](https://en.bitcoin.it/wiki/Atomic_cross-chain_trading) which are needed for inter-blockchain protocols like [lightning networks](https://lightning.network/).
+Adding a signature of type hash(x) allows anyone who knows x to sign the transaction. This type of signer is especially useful in [atomic cross-chain swaps](https://en.bitcoin.it/wiki/Atomic_cross-chain_trading) which are needed for inter-blockchain protocols like [lightning networks](https://lightning.network).
 
 First, create a random 256-bit value, which we call x. The SHA256 hash of that value can be added as a signer of type hash(x). Then in order to authorize a transaction, x is added as one of the signatures of the transaction. Keep in mind that x will be known to the world as soon as a transaction is submitted to the network with x as a signature. This means anyone will be able to sign for that account with the hash(x) signer at that point. Often you want there to be additional signers so someone must have a particular secret key and know x in order to reach the weight threshold required to authorize transactions on the account.
 
diff --git a/docs/learn/migrate/evm/smart-contract-deployment.mdx b/docs/learn/migrate/evm/smart-contract-deployment.mdx
index 7ec4662223..add84e9cc7 100644
--- a/docs/learn/migrate/evm/smart-contract-deployment.mdx
+++ b/docs/learn/migrate/evm/smart-contract-deployment.mdx
@@ -9,7 +9,7 @@ import TabItem from "@theme/TabItem";
 
 # Smart Contract Development with Soroban and Hardhat
 
-In this tutorial, we will discover the similarities in smart contract deployment by examining workflows with Soroban and [Hardhat](https://hardhat.org/). We will dive into the intricacies of each framework, learn to write secure and efficient smart contract code, and harness the power of Rust and Soroban to create customized contract logic.
+In this tutorial, we will discover the similarities in smart contract deployment by examining workflows with Soroban and [Hardhat](https://hardhat.org). We will dive into the intricacies of each framework, learn to write secure and efficient smart contract code, and harness the power of Rust and Soroban to create customized contract logic.
 
 ## Table of Contents
 
diff --git a/docs/learn/migrate/evm/solidity-and-rust-basics.mdx b/docs/learn/migrate/evm/solidity-and-rust-basics.mdx
index fec9533bbb..61d79dc6b2 100644
--- a/docs/learn/migrate/evm/solidity-and-rust-basics.mdx
+++ b/docs/learn/migrate/evm/solidity-and-rust-basics.mdx
@@ -461,7 +461,7 @@ Here's a line-by-line explanation of what the code is doing:
 #![no_std]
 ```
 
-This is a Rust attribute that tells the Rust compiler not to link the [Rust standard library](https://doc.rust-lang.org/std/). The standard library is extensive, and when deploying Soroban applications, we want to streamline the process as much as possible. By using `no_std`, we establish a leaner, "barebones" starting point for projects, encompassing only the Rust core and a few other essential components, rather than the full breadth of the standard library.
+This is a Rust attribute that tells the Rust compiler not to link the [Rust standard library](https://doc.rust-lang.org/std). The standard library is extensive, and when deploying Soroban applications, we want to streamline the process as much as possible. By using `no_std`, we establish a leaner, "barebones" starting point for projects, encompassing only the Rust core and a few other essential components, rather than the full breadth of the standard library.
 
 ```rust
 use soroban_sdk::{contractimpl, log, Env, Symbol};
diff --git a/docs/networks/README.mdx b/docs/networks/README.mdx
index 082db986ae..30f7cd7100 100644
--- a/docs/networks/README.mdx
+++ b/docs/networks/README.mdx
@@ -59,7 +59,7 @@ Testnet and Futurenet are reset periodically to the genesis ledger to declutter
 
 Futurenet resets are on a less regular cadence than Testnet resets and don't have a set schedule.
 
-Testnet resets typically happen 2-4 times per year at 17:00 UTC and are announced at least two weeks in advance on the [Stellar Dashboard](https://dashboard.stellar.org/) and through several developer community channels.
+Testnet resets typically happen 2-4 times per year at 17:00 UTC and are announced at least two weeks in advance on the [Stellar Dashboard](https://dashboard.stellar.org) and through several developer community channels.
 
 Here are the scheduled 2026 dates:
 
diff --git a/docs/networks/resource-limits-fees.mdx b/docs/networks/resource-limits-fees.mdx
index 96be646a9b..01906df444 100644
--- a/docs/networks/resource-limits-fees.mdx
+++ b/docs/networks/resource-limits-fees.mdx
@@ -5,7 +5,7 @@ title: Resource Limits & Fees
 
 ## Where to find the current resource limits and fees
 
-### [Stellar Lab](https://lab.stellar.org/)
+### [Stellar Lab](https://lab.stellar.org)
 
 The Stellar Lab's [Network Limits](https://lab.stellar.org/network-limits) page displays real-time network settings for [Testnet](https://lab.stellar.org/network-limits?$=network$id=testnet&label=Testnet&horizonUrl=https:////horizon-testnet.stellar.org&rpcUrl=https:////soroban-testnet.stellar.org&passphrase=Test%20SDF%20Network%20/;%20September%202015;;), [Mainnet](https://lab.stellar.org/network-limits?$=network$id=mainnet&label=Mainnet&horizonUrl=https:////horizon.stellar.org&rpcUrl=https:////mainnet.sorobanrpc.com&passphrase=Public%20Global%20Stellar%20Network%20/;%20September%202015;;), and [Futurenet](https://lab.stellar.org/network-limits?$=network$id=futurenet&label=Futurenet&horizonUrl=https:////horizon-futurenet.stellar.org&rpcUrl=https:////rpc-futurenet.stellar.org&passphrase=Test%20SDF%20Future%20Network%20/;%20October%202022;;). The page offers both `table` and `JSON` display options for easy viewing.
 
diff --git a/docs/platforms/anchor-platform/api-reference/platform/rpc/overview.mdx b/docs/platforms/anchor-platform/api-reference/platform/rpc/overview.mdx
index aa544d766e..544a5413ec 100644
--- a/docs/platforms/anchor-platform/api-reference/platform/rpc/overview.mdx
+++ b/docs/platforms/anchor-platform/api-reference/platform/rpc/overview.mdx
@@ -5,7 +5,7 @@ sidebar_position: 10
 
 JSON-RPC is a stateless, light-weight remote procedure call (RPC) protocol.
 
-It's simple and easy to use, as it uses a single HTTP endpoint and a JSON object that contains the method name and parameters. It is transport agnostic in that the concepts can be used within the same process, over sockets, over http, or in many various message passing environments. It uses [JSON](http://www.json.org/) ([RFC 4627](http://www.ietf.org/rfc/rfc4627.txt)) as data format.
+It's simple and easy to use, as it uses a single HTTP endpoint and a JSON object that contains the method name and parameters. It is transport agnostic in that the concepts can be used within the same process, over sockets, over http, or in many various message passing environments. It uses [JSON](http://www.json.org) ([RFC 4627](http://www.ietf.org/rfc/rfc4627.txt)) as data format.
 
 :::note
 
diff --git a/docs/platforms/anchor-platform/sep-guide/sep24/setting-up-production-server.mdx b/docs/platforms/anchor-platform/sep-guide/sep24/setting-up-production-server.mdx
index 149e81566c..ac6a3af6f9 100644
--- a/docs/platforms/anchor-platform/sep-guide/sep24/setting-up-production-server.mdx
+++ b/docs/platforms/anchor-platform/sep-guide/sep24/setting-up-production-server.mdx
@@ -9,7 +9,7 @@ Once the test server is live and you have tested both deposit and withdraw flows
 
 Make sure to keep the test server up, and deploy the production (mainnet) system in a separate environment. Having two deploys allows you to validate new features on the testnet before moving them to the final production deploy. You can also have a third staging environment if there's a big team working on this codebase and/or there will be many pushes to be tested internally before sharing with other institutions.
 
-To switch to Stellar's public (mainnet) network, all you have to do is change the network [passphrase](../../../../networks/README.mdx#network-passphrases) (for authenticating requests) and [Horizon URL](https://horizon.stellar.org/).
+To switch to Stellar's public (mainnet) network, all you have to do is change the network [passphrase](../../../../networks/README.mdx#network-passphrases) (for authenticating requests) and [Horizon URL](https://horizon.stellar.org).
 
 You can copy your existing development configs to create a production configuration.
 
diff --git a/docs/platforms/stellar-disbursement-platform/admin-guide/deploy-the-sdp.mdx b/docs/platforms/stellar-disbursement-platform/admin-guide/deploy-the-sdp.mdx
index 98ece2b292..d22c2eec7f 100644
--- a/docs/platforms/stellar-disbursement-platform/admin-guide/deploy-the-sdp.mdx
+++ b/docs/platforms/stellar-disbursement-platform/admin-guide/deploy-the-sdp.mdx
@@ -8,7 +8,7 @@ sidebar_position: 30
 ### Minimum System Requirements
 
 - **Stellar Accounts**: You will need a **Distribution Account** (funded) and a **SEP-10 Signing Account**.
-- **Certificates**: When running the SDP in a multi-tenant configuration, you will need to acquire wildcard TLS certificates to facilitate tenant provisioning as the SDP relies on subdomains to differentiate between tenants. This will allow you to provision tenants without having to manually configure TLS certificates for each tenant. You can use a service like [Let's Encrypt](https://letsencrypt.org/) or [Namecheap](https://www.namecheap.com/security/ssl-certificates/) to acquire these certificates.
+- **Certificates**: When running the SDP in a multi-tenant configuration, you will need to acquire wildcard TLS certificates to facilitate tenant provisioning as the SDP relies on subdomains to differentiate between tenants. This will allow you to provision tenants without having to manually configure TLS certificates for each tenant. You can use a service like [Let's Encrypt](https://letsencrypt.org) or [Namecheap](https://www.namecheap.com/security/ssl-certificates) to acquire these certificates.
 
 | Component | Requirement | Notes |
 | :-- | :-- | :-- |
diff --git a/docs/platforms/stellar-disbursement-platform/admin-guide/embedded-wallets.mdx b/docs/platforms/stellar-disbursement-platform/admin-guide/embedded-wallets.mdx
index f6f4b3e8df..bbf3c9401b 100644
--- a/docs/platforms/stellar-disbursement-platform/admin-guide/embedded-wallets.mdx
+++ b/docs/platforms/stellar-disbursement-platform/admin-guide/embedded-wallets.mdx
@@ -63,7 +63,7 @@ When a receiver creates an embedded wallet:
 
 :::info Learn More About Passkeys
 
-For more details about passkey technology, visit [passkeys.dev](https://passkeys.dev/docs/intro/what-are-passkeys/) or read about the [WebAuthn specification](https://www.w3.org/TR/webauthn/).
+For more details about passkey technology, visit [passkeys.dev](https://passkeys.dev/docs/intro/what-are-passkeys) or read about the [WebAuthn specification](https://www.w3.org/TR/webauthn).
 
 :::
 
@@ -234,9 +234,9 @@ To learn more about the technologies behind Embedded Wallets, check out these re
 
 ### Passkeys & WebAuthn
 
-- [passkeys.dev](https://passkeys.dev/) - Comprehensive guide to passkeys
-- [WebAuthn Specification](https://www.w3.org/TR/webauthn/) - W3C standard for web authentication
-- [FIDO Alliance](https://fidoalliance.org/) - The organization behind passkey standards
+- [passkeys.dev](https://passkeys.dev) - Comprehensive guide to passkeys
+- [WebAuthn Specification](https://www.w3.org/TR/webauthn) - W3C standard for web authentication
+- [FIDO Alliance](https://fidoalliance.org) - The organization behind passkey standards
 
 ### Stellar Protocols
 
@@ -246,5 +246,5 @@ To learn more about the technologies behind Embedded Wallets, check out these re
 
 ### Smart Contracts
 
-- [Soroban Documentation](https://soroban.stellar.org/) - Stellar's smart contract platform
+- [Soroban Documentation](https://soroban.stellar.org) - Stellar's smart contract platform
 - [Contract Address Format](https://developers.stellar.org/docs/learn/encyclopedia/contract-development/types/custom-types#addresses) - Understanding C-addresses vs G-addresses
diff --git a/docs/platforms/stellar-disbursement-platform/admin-guide/getting-started.mdx b/docs/platforms/stellar-disbursement-platform/admin-guide/getting-started.mdx
index 0f33ed189c..9683ea4355 100644
--- a/docs/platforms/stellar-disbursement-platform/admin-guide/getting-started.mdx
+++ b/docs/platforms/stellar-disbursement-platform/admin-guide/getting-started.mdx
@@ -9,8 +9,8 @@ This guide covers running the Stellar Disbursement Platform locally, sending a s
 
 - **Docker:** Make sure you have Docker installed on your system. If not, you can download it from [here](https://www.docker.com/products/docker-desktop) and start it once installed.
 - **Git:** You will need Git to clone the repository. You can download it from [here](https://git-scm.com/downloads).
-- **Go:** Required to generate your environment file. Install from [here](https://golang.org/dl/).
-- **jq:** Useful for optional scripts and diagnostics. You can download it from [here](https://jqlang.org/download/)
+- **Go:** Required to generate your environment file. Install from [here](https://golang.org/dl).
+- **jq:** Useful for optional scripts and diagnostics. You can download it from [here](https://jqlang.org/download)
 
 For macOS, Linux, you can install with Homebrew:
 
diff --git a/docs/platforms/stellar-disbursement-platform/admin-guide/monitoring.mdx b/docs/platforms/stellar-disbursement-platform/admin-guide/monitoring.mdx
index 98b4e9ef1d..12465b98eb 100644
--- a/docs/platforms/stellar-disbursement-platform/admin-guide/monitoring.mdx
+++ b/docs/platforms/stellar-disbursement-platform/admin-guide/monitoring.mdx
@@ -22,7 +22,7 @@ When the server starts, it mounts the `/metrics` route and surfaces request, dat
 
 We provide a Docker Compose file that boots Prometheus and Grafana pre-wired to scrape the SDP metrics endpoints.
 
-1. From the [repository root](https://github.com/stellar/stellar-disbursement-platform-backend/), run:
+1. From the [repository root](https://github.com/stellar/stellar-disbursement-platform-backend), run:
 
 ```sh
 cd dev
diff --git a/docs/platforms/stellar-disbursement-platform/admin-guide/troubleshooting.mdx b/docs/platforms/stellar-disbursement-platform/admin-guide/troubleshooting.mdx
index 1eda21009e..6f97315997 100644
--- a/docs/platforms/stellar-disbursement-platform/admin-guide/troubleshooting.mdx
+++ b/docs/platforms/stellar-disbursement-platform/admin-guide/troubleshooting.mdx
@@ -49,7 +49,7 @@ If TSS is down or unreachable, restart it and monitor the logs for errors.
 
 The distribution account must have sufficient XLM to cover the payment amount plus transaction fees.
 
-Use [Stellar Expert](https://stellar.expert/explorer/public/) or the Stellar CLI to check the balance.
+Use [Stellar Expert](https://stellar.expert/explorer/public) or the Stellar CLI to check the balance.
 
 #### 3. Validate Channel Accounts
 
@@ -64,7 +64,7 @@ time="2025-12-19T18:43:37.017Z" level=error msg="[DRY_RUN Crash Reporter] unexpe
 
 </details>
 
-**Diagnosis:** This error means either the **destination account** or the **channel account** doesn't exist on the network. Check both using [Stellar Expert](https://stellar.expert/explorer/public/).
+**Diagnosis:** This error means either the **destination account** or the **channel account** doesn't exist on the network. Check both using [Stellar Expert](https://stellar.expert/explorer/public).
 
 **Solution:**
 
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/create-direct-payment.api.mdx b/docs/platforms/stellar-disbursement-platform/api-reference/create-direct-payment.api.mdx
index 8f802dd9fe..d63ef82b06 100644
--- a/docs/platforms/stellar-disbursement-platform/api-reference/create-direct-payment.api.mdx
+++ b/docs/platforms/stellar-disbursement-platform/api-reference/create-direct-payment.api.mdx
@@ -66,7 +66,7 @@ Creates a new direct payment that is immediately sent to the specified receiver
 <StatusCodes
   id={undefined}
   label={undefined}
-  responses={{"201":{"description":"Direct payment created successfully","content":{"application/json":{"schema":{"type":"object","properties":{"id":{"type":"string","example":"ddf22f55-3259-4822-a4e2-ce01334997f4"},"amount":{"type":"string","description":"The amount of the payment","example":"100.00"},"stellar_transaction_id":{"type":"string","description":"The ID of the transaction in the Stellar network. It can be used tio track the payment in the Stellar network using [Stellar Laboratory](https://laboratory.stellar.org/), or [StellarExpert](https://stellar.expert/).","example":"0b339d1c89d314186b8147c2af4c9a9ed5bbdbcd7ada8d138633907649b"},"circle_transfer_request_id":{"type":"string","description":"The Circle transfer request ID. It is only present when the payment was made using Circle.","example":"74a68b6a-3f67-424b-b8b0-e593a19d7463"},"stellar_operation_id":{"type":"string"},"status":{"type":"string","description":"The status of the payment","enum":["DRAFT","READY","PENDING","PAUSED","SUCCESS","FAILED","CANCELED"],"title":"PaymentStatus"},"status_history":{"type":"array","description":"An aggregated list of metadata objects containing the statuses and the timestamp of when these status changes occurred.","items":{"type":"object","properties":{"status":{"type":"string","description":"The status of the payment","enum":["DRAFT","READY","PENDING","PAUSED","SUCCESS","FAILED","CANCELED"],"title":"PaymentStatus"},"status_message":{"type":"string"},"timestamp":{"type":"string","format":"date-time","example":"2023-02-03T10:45:51Z"}},"title":"PaymentStatusHistoryEntry"},"title":"PaymentStatusHistory"},"type":{"type":"string","description":"The type of the payment.","enum":["DISBURSEMENT","DIRECT"]},"disbursement":{"type":"object","properties":{"id":{"type":"string","description":"The unique identifier of the disbursement","format":"uuid","example":"c51ba1d5-52d3-412f-a59c-6ef32d59ab43"},"name":{"type":"string","description":"The name of the disbursement","example":"disbursement-june-29"},"receiver_registration_message_template":{"type":"string","description":"The custom template used to send invitations to receivers. The `default` message isn't returned. In the message's content it's possible to add the following template variables: `{{.OrganizationName}}` which is the Organization Name configured and `{{.RegistrationLink}}` which is the link generated by SDP to send to the receiver (in case this is not present in the message, it's automatically appended at the end).","example":"You have a payment waiting for you from {{.OrganizationName}}. Click {{.RegistrationLink}} to register."},"registration_contact_type":{"type":"string","enum":["EMAIL","PHONE_NUMBER","EMAIL_AND_WALLET_ADDRESS","PHONE_NUMBER_AND_WALLET_ADDRESS"],"title":"RegistrationContactType"},"status":{"type":"string","enum":["DRAFT","READY","STARTED","PAUSED","COMPLETED"],"title":"DisbursementStatus"},"verification_field":{"type":"string","enum":["DATE_OF_BIRTH","YEAR_MONTH","PIN","NATIONAL_ID_NUMBER"],"title":"VerificationField"},"status_history":{"type":"array","items":{"type":"object","properties":{"user_id":{"type":"string","example":"3f351b9e-ed0f-40fa-a314-14757b42dab1"},"status":{"type":"string","enum":["DRAFT","READY","STARTED","PAUSED","COMPLETED"],"title":"DisbursementStatus"},"timestamp":{"type":"string","format":"date-time","example":"2023-02-03T10:45:51Z"}},"title":"DisbursementStatusHistoryEntry"},"title":"DisbursementStatusHistory"},"file_name":{"type":"string","example":"disbursement-feb-03-2023.csv"},"created_at":{"type":"string","description":"The creation timestamp of the disbursement","format":"date-time","example":"2023-06-30T01:22:57.831975Z"},"updated_at":{"type":"string","description":"The last update timestamp of the disbursement","format":"date-time","example":"2023-06-30T01:22:58.316511Z"}},"title":"DisbursementLite"},"asset":{"type":"object","properties":{"id":{"type":"string","example":"ffaec4b3-46b0-4db4-a4c4-6c3508057705"},"code":{"type":"string","description":"Asset code","example":"USDC"},"issuer":{"type":"string","description":"Asset issuer address","example":"GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"},"created_at":{"type":"string","format":"date-time","example":"2023-02-03T10:45:51Z"},"updated_at":{"type":"string","format":"date-time","example":"2023-02-03T10:45:51Z"},"deleted_at":{"type":"string","format":"date-time","example":"2023-06-03T10:55:51Z"}},"description":"The Stellar asset object","title":"Asset"},"receiver_wallet":{"type":"object","properties":{"id":{"type":"string","example":"803031d4-1d04-4879-b6d9-dc5641f9988e"},"receiver":{"type":"object","properties":{"id":{"type":"string","example":"029e2ed0-feb6-4c40-8b47-0836a85741a2"}},"title":"ReceiverLite"},"wallet":{"type":"object","properties":{"id":{"type":"string","example":"5ada9ed5-455a-4782-a0ee-160767e0deb1"},"name":{"type":"string","example":"Vibrant Assist"},"homepage":{"type":"string","example":"https://vibrantapp.com"},"sep_10_client_domain":{"type":"string","example":"api-dev.vibrantapp.com"},"deep_link_schema":{"type":"string","example":"https://vibrantapp.com/sdp-dev"},"enabled":{"type":"boolean","example":true},"user_managed":{"type":"boolean","example":false}},"title":"WalletLite"},"stellar_address":{"type":"string","example":"GCXAJ3XJ3VK3JFH3QMDFOSKM2NMMZBSO3VIT6EUPQWSDW2J74M23RRSL"},"stellar_memo":{"type":"string"},"stellar_memo_type":{"type":"string"},"sep24_transaction_id":{"type":"string"},"created_at":{"type":"string","example":"2023-02-03T10:45:51.000Z"},"updated_at":{"type":"string","example":"2023-02-03T10:45:51.000Z"},"invitation_sent_at":{"type":"string","example":"2023-02-09T10:45:51.000Z"},"status":{"type":"string","enum":["DRAFT","READY","REGISTERED","FLAGGED"],"title":"ReceiversWalletStatus"},"status_history":{"type":"array","items":{"type":"object","properties":{"status":{"type":"string","enum":["DRAFT","READY","REGISTERED","FLAGGED"],"title":"ReceiversWalletStatus"},"timestamp":{"type":"string","format":"date-time","example":"2023-02-10T10:45:51Z"}},"title":"ReceiversWalletStatusHistoryEntry"}},"otp_confirmed_at":{"type":"string","format":"date-time","example":"2023-02-10T10:45:51Z"},"otp_confirmed_with":{"type":"string"}},"title":"ReceiverWalletLite"},"external_payment_id":{"type":"string","description":"Optional external payment identifier provided by the client.","example":"payment-001"},"created_at":{"type":"string","format":"date-time","example":"2023-02-03T10:45:51Z"},"updated_at":{"type":"string","format":"date-time","example":"2023-02-03T10:45:51Z"}},"title":"Payment"}}}},"400":{"description":"Bad Request","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string","description":"Details about the error"},"extras":{"type":"object","properties":{}}}}}}},"401":{"description":"Unauthorized","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"},"extras":{"type":"object","properties":{"status":{"type":"number"},"message":{"type":"string"}}}}},"example":{"error":"Not authorized","extras":{"status":401,"message":"Not authorized"}}}}},"403":{"description":"Forbidden","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"}}},"example":{"error":"Forbidden"}}}},"404":{"description":"Not Found","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"},"extras":{"type":"object","properties":{"status":{"type":"number"},"message":{"type":"string"}}}}},"example":{"error":"Not found","extras":{"status":404,"message":"Resource not found"}}}}}}}
+  responses={{"201":{"description":"Direct payment created successfully","content":{"application/json":{"schema":{"type":"object","properties":{"id":{"type":"string","example":"ddf22f55-3259-4822-a4e2-ce01334997f4"},"amount":{"type":"string","description":"The amount of the payment","example":"100.00"},"stellar_transaction_id":{"type":"string","description":"The ID of the transaction in the Stellar network. It can be used tio track the payment in the Stellar network using [Stellar Laboratory](https://laboratory.stellar.org), or [StellarExpert](https://stellar.expert).","example":"0b339d1c89d314186b8147c2af4c9a9ed5bbdbcd7ada8d138633907649b"},"circle_transfer_request_id":{"type":"string","description":"The Circle transfer request ID. It is only present when the payment was made using Circle.","example":"74a68b6a-3f67-424b-b8b0-e593a19d7463"},"stellar_operation_id":{"type":"string"},"status":{"type":"string","description":"The status of the payment","enum":["DRAFT","READY","PENDING","PAUSED","SUCCESS","FAILED","CANCELED"],"title":"PaymentStatus"},"status_history":{"type":"array","description":"An aggregated list of metadata objects containing the statuses and the timestamp of when these status changes occurred.","items":{"type":"object","properties":{"status":{"type":"string","description":"The status of the payment","enum":["DRAFT","READY","PENDING","PAUSED","SUCCESS","FAILED","CANCELED"],"title":"PaymentStatus"},"status_message":{"type":"string"},"timestamp":{"type":"string","format":"date-time","example":"2023-02-03T10:45:51Z"}},"title":"PaymentStatusHistoryEntry"},"title":"PaymentStatusHistory"},"type":{"type":"string","description":"The type of the payment.","enum":["DISBURSEMENT","DIRECT"]},"disbursement":{"type":"object","properties":{"id":{"type":"string","description":"The unique identifier of the disbursement","format":"uuid","example":"c51ba1d5-52d3-412f-a59c-6ef32d59ab43"},"name":{"type":"string","description":"The name of the disbursement","example":"disbursement-june-29"},"receiver_registration_message_template":{"type":"string","description":"The custom template used to send invitations to receivers. The `default` message isn't returned. In the message's content it's possible to add the following template variables: `{{.OrganizationName}}` which is the Organization Name configured and `{{.RegistrationLink}}` which is the link generated by SDP to send to the receiver (in case this is not present in the message, it's automatically appended at the end).","example":"You have a payment waiting for you from {{.OrganizationName}}. Click {{.RegistrationLink}} to register."},"registration_contact_type":{"type":"string","enum":["EMAIL","PHONE_NUMBER","EMAIL_AND_WALLET_ADDRESS","PHONE_NUMBER_AND_WALLET_ADDRESS"],"title":"RegistrationContactType"},"status":{"type":"string","enum":["DRAFT","READY","STARTED","PAUSED","COMPLETED"],"title":"DisbursementStatus"},"verification_field":{"type":"string","enum":["DATE_OF_BIRTH","YEAR_MONTH","PIN","NATIONAL_ID_NUMBER"],"title":"VerificationField"},"status_history":{"type":"array","items":{"type":"object","properties":{"user_id":{"type":"string","example":"3f351b9e-ed0f-40fa-a314-14757b42dab1"},"status":{"type":"string","enum":["DRAFT","READY","STARTED","PAUSED","COMPLETED"],"title":"DisbursementStatus"},"timestamp":{"type":"string","format":"date-time","example":"2023-02-03T10:45:51Z"}},"title":"DisbursementStatusHistoryEntry"},"title":"DisbursementStatusHistory"},"file_name":{"type":"string","example":"disbursement-feb-03-2023.csv"},"created_at":{"type":"string","description":"The creation timestamp of the disbursement","format":"date-time","example":"2023-06-30T01:22:57.831975Z"},"updated_at":{"type":"string","description":"The last update timestamp of the disbursement","format":"date-time","example":"2023-06-30T01:22:58.316511Z"}},"title":"DisbursementLite"},"asset":{"type":"object","properties":{"id":{"type":"string","example":"ffaec4b3-46b0-4db4-a4c4-6c3508057705"},"code":{"type":"string","description":"Asset code","example":"USDC"},"issuer":{"type":"string","description":"Asset issuer address","example":"GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"},"created_at":{"type":"string","format":"date-time","example":"2023-02-03T10:45:51Z"},"updated_at":{"type":"string","format":"date-time","example":"2023-02-03T10:45:51Z"},"deleted_at":{"type":"string","format":"date-time","example":"2023-06-03T10:55:51Z"}},"description":"The Stellar asset object","title":"Asset"},"receiver_wallet":{"type":"object","properties":{"id":{"type":"string","example":"803031d4-1d04-4879-b6d9-dc5641f9988e"},"receiver":{"type":"object","properties":{"id":{"type":"string","example":"029e2ed0-feb6-4c40-8b47-0836a85741a2"}},"title":"ReceiverLite"},"wallet":{"type":"object","properties":{"id":{"type":"string","example":"5ada9ed5-455a-4782-a0ee-160767e0deb1"},"name":{"type":"string","example":"Vibrant Assist"},"homepage":{"type":"string","example":"https://vibrantapp.com"},"sep_10_client_domain":{"type":"string","example":"api-dev.vibrantapp.com"},"deep_link_schema":{"type":"string","example":"https://vibrantapp.com/sdp-dev"},"enabled":{"type":"boolean","example":true},"user_managed":{"type":"boolean","example":false}},"title":"WalletLite"},"stellar_address":{"type":"string","example":"GCXAJ3XJ3VK3JFH3QMDFOSKM2NMMZBSO3VIT6EUPQWSDW2J74M23RRSL"},"stellar_memo":{"type":"string"},"stellar_memo_type":{"type":"string"},"sep24_transaction_id":{"type":"string"},"created_at":{"type":"string","example":"2023-02-03T10:45:51.000Z"},"updated_at":{"type":"string","example":"2023-02-03T10:45:51.000Z"},"invitation_sent_at":{"type":"string","example":"2023-02-09T10:45:51.000Z"},"status":{"type":"string","enum":["DRAFT","READY","REGISTERED","FLAGGED"],"title":"ReceiversWalletStatus"},"status_history":{"type":"array","items":{"type":"object","properties":{"status":{"type":"string","enum":["DRAFT","READY","REGISTERED","FLAGGED"],"title":"ReceiversWalletStatus"},"timestamp":{"type":"string","format":"date-time","example":"2023-02-10T10:45:51Z"}},"title":"ReceiversWalletStatusHistoryEntry"}},"otp_confirmed_at":{"type":"string","format":"date-time","example":"2023-02-10T10:45:51Z"},"otp_confirmed_with":{"type":"string"}},"title":"ReceiverWalletLite"},"external_payment_id":{"type":"string","description":"Optional external payment identifier provided by the client.","example":"payment-001"},"created_at":{"type":"string","format":"date-time","example":"2023-02-03T10:45:51Z"},"updated_at":{"type":"string","format":"date-time","example":"2023-02-03T10:45:51Z"}},"title":"Payment"}}}},"400":{"description":"Bad Request","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string","description":"Details about the error"},"extras":{"type":"object","properties":{}}}}}}},"401":{"description":"Unauthorized","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"},"extras":{"type":"object","properties":{"status":{"type":"number"},"message":{"type":"string"}}}}},"example":{"error":"Not authorized","extras":{"status":401,"message":"Not authorized"}}}}},"403":{"description":"Forbidden","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"}}},"example":{"error":"Forbidden"}}}},"404":{"description":"Not Found","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"},"extras":{"type":"object","properties":{"status":{"type":"number"},"message":{"type":"string"}}}}},"example":{"error":"Not found","extras":{"status":404,"message":"Resource not found"}}}}}}}
 >
   
 </StatusCodes>
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/list-all-disbursement-receivers.api.mdx b/docs/platforms/stellar-disbursement-platform/api-reference/list-all-disbursement-receivers.api.mdx
index 6dda53502d..4d6b5080d9 100644
--- a/docs/platforms/stellar-disbursement-platform/api-reference/list-all-disbursement-receivers.api.mdx
+++ b/docs/platforms/stellar-disbursement-platform/api-reference/list-all-disbursement-receivers.api.mdx
@@ -66,7 +66,7 @@ Fetches a list of receivers within a specific disbursement using the disbursemen
 <StatusCodes
   id={undefined}
   label={undefined}
-  responses={{"200":{"description":"A list of Disbursement Receivers","content":{"application/json":{"schema":{"type":"object","properties":{"pagination":{"type":"object","properties":{"next":{"type":"string","example":"?page=3&page_limit=2"},"prev":{"type":"string","example":"?page=1&page_limit=2"},"pages":{"type":"integer","example":8},"total":{"type":"integer","example":16}},"title":"Pagination"},"data":{"type":"array","items":{"type":"object","properties":{"id":{"type":"string","example":"ec3a57c0-5660-4b5a-af76-acadc7b09b93"},"email":{"type":"string","example":"receiver@mail.org"},"phone_number":{"type":"string","example":"+15552368475"},"external_id":{"type":"string","example":"usr129001"},"receiver_wallet":{"type":"object","properties":{"id":{"type":"string","example":"803031d4-1d04-4879-b6d9-dc5641f9988e"},"receiver":{"type":"object","properties":{"id":{"type":"string","example":"029e2ed0-feb6-4c40-8b47-0836a85741a2"}},"title":"ReceiverLite"},"wallet":{"type":"object","properties":{"id":{"type":"string","example":"5ada9ed5-455a-4782-a0ee-160767e0deb1"},"name":{"type":"string","example":"Vibrant Assist"},"homepage":{"type":"string","example":"https://vibrantapp.com"},"sep_10_client_domain":{"type":"string","example":"api-dev.vibrantapp.com"},"deep_link_schema":{"type":"string","example":"https://vibrantapp.com/sdp-dev"},"enabled":{"type":"boolean","example":true},"user_managed":{"type":"boolean","example":false}},"title":"WalletLite"},"stellar_address":{"type":"string","example":"GCXAJ3XJ3VK3JFH3QMDFOSKM2NMMZBSO3VIT6EUPQWSDW2J74M23RRSL"},"stellar_memo":{"type":"string"},"stellar_memo_type":{"type":"string"},"created_at":{"type":"string","example":"2023-02-03T10:45:51.000Z"},"updated_at":{"type":"string","example":"2023-02-03T10:45:51.000Z"},"invited_at":{"type":"string","example":"2023-02-09T10:45:51.000Z"},"last_message_sent_at":{"type":"string","description":"timestamp when the receiver last received an invitation about this wallet","example":"2023-02-10T10:45:51.000Z"},"total_payments":{"type":"string","example":"2"},"payments_received":{"type":"string","example":"2"},"failed_payments":{"type":"string","example":"0"},"remaining_payments":{"type":"string","example":"0"},"received_amounts":{"type":"array","items":{"type":"object","properties":{"asset_code":{"type":"string","example":"USDC"},"asset_issuer":{"type":"string","example":"GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"},"received_amount":{"type":"string","example":"100.00"}},"title":"Amount"}},"status":{"type":"string","enum":["DRAFT","READY","REGISTERED","FLAGGED"],"title":"ReceiversWalletStatus"},"status_history":{"type":"array","items":{"type":"object","properties":{"status":{"type":"string","enum":["DRAFT","READY","REGISTERED","FLAGGED"],"title":"ReceiversWalletStatus"},"timestamp":{"type":"string","format":"date-time","example":"2023-02-10T10:45:51Z"}},"title":"ReceiversWalletStatusHistoryEntry"}}},"title":"ReceiverWallet"},"payment":{"type":"object","properties":{"id":{"type":"string","example":"ddf22f55-3259-4822-a4e2-ce01334997f4"},"amount":{"type":"string","description":"The amount of the payment","example":"100.00"},"stellar_transaction_id":{"type":"string","description":"The ID of the transaction in the Stellar network. It can be used tio track the payment in the Stellar network using [Stellar Laboratory](https://laboratory.stellar.org/), or [StellarExpert](https://stellar.expert/).","example":"0b339d1c89d314186b8147c2af4c9a9ed5bbdbcd7ada8d138633907649b"},"circle_transfer_request_id":{"type":"string","description":"The Circle transfer request ID. It is only present when the payment was made using Circle.","example":"74a68b6a-3f67-424b-b8b0-e593a19d7463"},"stellar_operation_id":{"type":"string"},"status":{"type":"string","description":"The status of the payment","enum":["DRAFT","READY","PENDING","PAUSED","SUCCESS","FAILED","CANCELED"],"title":"PaymentStatus"},"status_history":{"type":"array","description":"An aggregated list of metadata objects containing the statuses and the timestamp of when these status changes occurred.","items":{"type":"object","properties":{"status":{"type":"string","description":"The status of the payment","enum":["DRAFT","READY","PENDING","PAUSED","SUCCESS","FAILED","CANCELED"],"title":"PaymentStatus"},"status_message":{"type":"string"},"timestamp":{"type":"string","format":"date-time","example":"2023-02-03T10:45:51Z"}},"title":"PaymentStatusHistoryEntry"},"title":"PaymentStatusHistory"},"type":{"type":"string","description":"The type of the payment.","enum":["DISBURSEMENT","DIRECT"]},"disbursement":{"type":"object","properties":{"id":{"type":"string","description":"The unique identifier of the disbursement","format":"uuid","example":"c51ba1d5-52d3-412f-a59c-6ef32d59ab43"},"name":{"type":"string","description":"The name of the disbursement","example":"disbursement-june-29"},"receiver_registration_message_template":{"type":"string","description":"The custom template used to send invitations to receivers. The `default` message isn't returned. In the message's content it's possible to add the following template variables: `{{.OrganizationName}}` which is the Organization Name configured and `{{.RegistrationLink}}` which is the link generated by SDP to send to the receiver (in case this is not present in the message, it's automatically appended at the end).","example":"You have a payment waiting for you from {{.OrganizationName}}. Click {{.RegistrationLink}} to register."},"registration_contact_type":{"type":"string","enum":["EMAIL","PHONE_NUMBER","EMAIL_AND_WALLET_ADDRESS","PHONE_NUMBER_AND_WALLET_ADDRESS"],"title":"RegistrationContactType"},"status":{"type":"string","enum":["DRAFT","READY","STARTED","PAUSED","COMPLETED"],"title":"DisbursementStatus"},"verification_field":{"type":"string","enum":["DATE_OF_BIRTH","YEAR_MONTH","PIN","NATIONAL_ID_NUMBER"],"title":"VerificationField"},"status_history":{"type":"array","items":{"type":"object","properties":{"user_id":{"type":"string","example":"3f351b9e-ed0f-40fa-a314-14757b42dab1"},"status":{"type":"string","enum":["DRAFT","READY","STARTED","PAUSED","COMPLETED"],"title":"DisbursementStatus"},"timestamp":{"type":"string","format":"date-time","example":"2023-02-03T10:45:51Z"}},"title":"DisbursementStatusHistoryEntry"},"title":"DisbursementStatusHistory"},"file_name":{"type":"string","example":"disbursement-feb-03-2023.csv"},"created_at":{"type":"string","description":"The creation timestamp of the disbursement","format":"date-time","example":"2023-06-30T01:22:57.831975Z"},"updated_at":{"type":"string","description":"The last update timestamp of the disbursement","format":"date-time","example":"2023-06-30T01:22:58.316511Z"}},"title":"DisbursementLite"},"asset":{"type":"object","properties":{"id":{"type":"string","example":"ffaec4b3-46b0-4db4-a4c4-6c3508057705"},"code":{"type":"string","description":"Asset code","example":"USDC"},"issuer":{"type":"string","description":"Asset issuer address","example":"GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"},"created_at":{"type":"string","format":"date-time","example":"2023-02-03T10:45:51Z"},"updated_at":{"type":"string","format":"date-time","example":"2023-02-03T10:45:51Z"},"deleted_at":{"type":"string","format":"date-time","example":"2023-06-03T10:55:51Z"}},"description":"The Stellar asset object","title":"Asset"},"receiver_wallet":{"type":"object","properties":{"id":{"type":"string","example":"803031d4-1d04-4879-b6d9-dc5641f9988e"},"receiver":{"type":"object","properties":{"id":{"type":"string","example":"029e2ed0-feb6-4c40-8b47-0836a85741a2"}},"title":"ReceiverLite"},"wallet":{"type":"object","properties":{"id":{"type":"string","example":"5ada9ed5-455a-4782-a0ee-160767e0deb1"},"name":{"type":"string","example":"Vibrant Assist"},"homepage":{"type":"string","example":"https://vibrantapp.com"},"sep_10_client_domain":{"type":"string","example":"api-dev.vibrantapp.com"},"deep_link_schema":{"type":"string","example":"https://vibrantapp.com/sdp-dev"},"enabled":{"type":"boolean","example":true},"user_managed":{"type":"boolean","example":false}},"title":"WalletLite"},"stellar_address":{"type":"string","example":"GCXAJ3XJ3VK3JFH3QMDFOSKM2NMMZBSO3VIT6EUPQWSDW2J74M23RRSL"},"stellar_memo":{"type":"string"},"stellar_memo_type":{"type":"string"},"sep24_transaction_id":{"type":"string"},"created_at":{"type":"string","example":"2023-02-03T10:45:51.000Z"},"updated_at":{"type":"string","example":"2023-02-03T10:45:51.000Z"},"invitation_sent_at":{"type":"string","example":"2023-02-09T10:45:51.000Z"},"status":{"type":"string","enum":["DRAFT","READY","REGISTERED","FLAGGED"],"title":"ReceiversWalletStatus"},"status_history":{"type":"array","items":{"type":"object","properties":{"status":{"type":"string","enum":["DRAFT","READY","REGISTERED","FLAGGED"],"title":"ReceiversWalletStatus"},"timestamp":{"type":"string","format":"date-time","example":"2023-02-10T10:45:51Z"}},"title":"ReceiversWalletStatusHistoryEntry"}},"otp_confirmed_at":{"type":"string","format":"date-time","example":"2023-02-10T10:45:51Z"},"otp_confirmed_with":{"type":"string"}},"title":"ReceiverWalletLite"},"external_payment_id":{"type":"string","description":"Optional external payment identifier provided by the client.","example":"payment-001"},"created_at":{"type":"string","format":"date-time","example":"2023-02-03T10:45:51Z"},"updated_at":{"type":"string","format":"date-time","example":"2023-02-03T10:45:51Z"}},"title":"Payment"},"created_at":{"type":"string","format":"date-time","example":"2023-02-03T10:45:51Z"},"updated_at":{"type":"string","format":"date-time","example":"2023-02-03T10:45:51Z"}},"title":"DisbursementReceiver"}}},"title":"DisbursementReceiverPagination"}}}},"401":{"description":"Unauthorized","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"},"extras":{"type":"object","properties":{"status":{"type":"number"},"message":{"type":"string"}}}}},"example":{"error":"Not authorized","extras":{"status":401,"message":"Not authorized"}}}}},"403":{"description":"Forbidden","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"}}},"example":{"error":"Forbidden"}}}},"404":{"description":"Not Found","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"},"extras":{"type":"object","properties":{"status":{"type":"number"},"message":{"type":"string"}}}}},"example":{"error":"Not found","extras":{"status":404,"message":"Resource not found"}}}}}}}
+  responses={{"200":{"description":"A list of Disbursement Receivers","content":{"application/json":{"schema":{"type":"object","properties":{"pagination":{"type":"object","properties":{"next":{"type":"string","example":"?page=3&page_limit=2"},"prev":{"type":"string","example":"?page=1&page_limit=2"},"pages":{"type":"integer","example":8},"total":{"type":"integer","example":16}},"title":"Pagination"},"data":{"type":"array","items":{"type":"object","properties":{"id":{"type":"string","example":"ec3a57c0-5660-4b5a-af76-acadc7b09b93"},"email":{"type":"string","example":"receiver@mail.org"},"phone_number":{"type":"string","example":"+15552368475"},"external_id":{"type":"string","example":"usr129001"},"receiver_wallet":{"type":"object","properties":{"id":{"type":"string","example":"803031d4-1d04-4879-b6d9-dc5641f9988e"},"receiver":{"type":"object","properties":{"id":{"type":"string","example":"029e2ed0-feb6-4c40-8b47-0836a85741a2"}},"title":"ReceiverLite"},"wallet":{"type":"object","properties":{"id":{"type":"string","example":"5ada9ed5-455a-4782-a0ee-160767e0deb1"},"name":{"type":"string","example":"Vibrant Assist"},"homepage":{"type":"string","example":"https://vibrantapp.com"},"sep_10_client_domain":{"type":"string","example":"api-dev.vibrantapp.com"},"deep_link_schema":{"type":"string","example":"https://vibrantapp.com/sdp-dev"},"enabled":{"type":"boolean","example":true},"user_managed":{"type":"boolean","example":false}},"title":"WalletLite"},"stellar_address":{"type":"string","example":"GCXAJ3XJ3VK3JFH3QMDFOSKM2NMMZBSO3VIT6EUPQWSDW2J74M23RRSL"},"stellar_memo":{"type":"string"},"stellar_memo_type":{"type":"string"},"created_at":{"type":"string","example":"2023-02-03T10:45:51.000Z"},"updated_at":{"type":"string","example":"2023-02-03T10:45:51.000Z"},"invited_at":{"type":"string","example":"2023-02-09T10:45:51.000Z"},"last_message_sent_at":{"type":"string","description":"timestamp when the receiver last received an invitation about this wallet","example":"2023-02-10T10:45:51.000Z"},"total_payments":{"type":"string","example":"2"},"payments_received":{"type":"string","example":"2"},"failed_payments":{"type":"string","example":"0"},"remaining_payments":{"type":"string","example":"0"},"received_amounts":{"type":"array","items":{"type":"object","properties":{"asset_code":{"type":"string","example":"USDC"},"asset_issuer":{"type":"string","example":"GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"},"received_amount":{"type":"string","example":"100.00"}},"title":"Amount"}},"status":{"type":"string","enum":["DRAFT","READY","REGISTERED","FLAGGED"],"title":"ReceiversWalletStatus"},"status_history":{"type":"array","items":{"type":"object","properties":{"status":{"type":"string","enum":["DRAFT","READY","REGISTERED","FLAGGED"],"title":"ReceiversWalletStatus"},"timestamp":{"type":"string","format":"date-time","example":"2023-02-10T10:45:51Z"}},"title":"ReceiversWalletStatusHistoryEntry"}}},"title":"ReceiverWallet"},"payment":{"type":"object","properties":{"id":{"type":"string","example":"ddf22f55-3259-4822-a4e2-ce01334997f4"},"amount":{"type":"string","description":"The amount of the payment","example":"100.00"},"stellar_transaction_id":{"type":"string","description":"The ID of the transaction in the Stellar network. It can be used tio track the payment in the Stellar network using [Stellar Laboratory](https://laboratory.stellar.org), or [StellarExpert](https://stellar.expert).","example":"0b339d1c89d314186b8147c2af4c9a9ed5bbdbcd7ada8d138633907649b"},"circle_transfer_request_id":{"type":"string","description":"The Circle transfer request ID. It is only present when the payment was made using Circle.","example":"74a68b6a-3f67-424b-b8b0-e593a19d7463"},"stellar_operation_id":{"type":"string"},"status":{"type":"string","description":"The status of the payment","enum":["DRAFT","READY","PENDING","PAUSED","SUCCESS","FAILED","CANCELED"],"title":"PaymentStatus"},"status_history":{"type":"array","description":"An aggregated list of metadata objects containing the statuses and the timestamp of when these status changes occurred.","items":{"type":"object","properties":{"status":{"type":"string","description":"The status of the payment","enum":["DRAFT","READY","PENDING","PAUSED","SUCCESS","FAILED","CANCELED"],"title":"PaymentStatus"},"status_message":{"type":"string"},"timestamp":{"type":"string","format":"date-time","example":"2023-02-03T10:45:51Z"}},"title":"PaymentStatusHistoryEntry"},"title":"PaymentStatusHistory"},"type":{"type":"string","description":"The type of the payment.","enum":["DISBURSEMENT","DIRECT"]},"disbursement":{"type":"object","properties":{"id":{"type":"string","description":"The unique identifier of the disbursement","format":"uuid","example":"c51ba1d5-52d3-412f-a59c-6ef32d59ab43"},"name":{"type":"string","description":"The name of the disbursement","example":"disbursement-june-29"},"receiver_registration_message_template":{"type":"string","description":"The custom template used to send invitations to receivers. The `default` message isn't returned. In the message's content it's possible to add the following template variables: `{{.OrganizationName}}` which is the Organization Name configured and `{{.RegistrationLink}}` which is the link generated by SDP to send to the receiver (in case this is not present in the message, it's automatically appended at the end).","example":"You have a payment waiting for you from {{.OrganizationName}}. Click {{.RegistrationLink}} to register."},"registration_contact_type":{"type":"string","enum":["EMAIL","PHONE_NUMBER","EMAIL_AND_WALLET_ADDRESS","PHONE_NUMBER_AND_WALLET_ADDRESS"],"title":"RegistrationContactType"},"status":{"type":"string","enum":["DRAFT","READY","STARTED","PAUSED","COMPLETED"],"title":"DisbursementStatus"},"verification_field":{"type":"string","enum":["DATE_OF_BIRTH","YEAR_MONTH","PIN","NATIONAL_ID_NUMBER"],"title":"VerificationField"},"status_history":{"type":"array","items":{"type":"object","properties":{"user_id":{"type":"string","example":"3f351b9e-ed0f-40fa-a314-14757b42dab1"},"status":{"type":"string","enum":["DRAFT","READY","STARTED","PAUSED","COMPLETED"],"title":"DisbursementStatus"},"timestamp":{"type":"string","format":"date-time","example":"2023-02-03T10:45:51Z"}},"title":"DisbursementStatusHistoryEntry"},"title":"DisbursementStatusHistory"},"file_name":{"type":"string","example":"disbursement-feb-03-2023.csv"},"created_at":{"type":"string","description":"The creation timestamp of the disbursement","format":"date-time","example":"2023-06-30T01:22:57.831975Z"},"updated_at":{"type":"string","description":"The last update timestamp of the disbursement","format":"date-time","example":"2023-06-30T01:22:58.316511Z"}},"title":"DisbursementLite"},"asset":{"type":"object","properties":{"id":{"type":"string","example":"ffaec4b3-46b0-4db4-a4c4-6c3508057705"},"code":{"type":"string","description":"Asset code","example":"USDC"},"issuer":{"type":"string","description":"Asset issuer address","example":"GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"},"created_at":{"type":"string","format":"date-time","example":"2023-02-03T10:45:51Z"},"updated_at":{"type":"string","format":"date-time","example":"2023-02-03T10:45:51Z"},"deleted_at":{"type":"string","format":"date-time","example":"2023-06-03T10:55:51Z"}},"description":"The Stellar asset object","title":"Asset"},"receiver_wallet":{"type":"object","properties":{"id":{"type":"string","example":"803031d4-1d04-4879-b6d9-dc5641f9988e"},"receiver":{"type":"object","properties":{"id":{"type":"string","example":"029e2ed0-feb6-4c40-8b47-0836a85741a2"}},"title":"ReceiverLite"},"wallet":{"type":"object","properties":{"id":{"type":"string","example":"5ada9ed5-455a-4782-a0ee-160767e0deb1"},"name":{"type":"string","example":"Vibrant Assist"},"homepage":{"type":"string","example":"https://vibrantapp.com"},"sep_10_client_domain":{"type":"string","example":"api-dev.vibrantapp.com"},"deep_link_schema":{"type":"string","example":"https://vibrantapp.com/sdp-dev"},"enabled":{"type":"boolean","example":true},"user_managed":{"type":"boolean","example":false}},"title":"WalletLite"},"stellar_address":{"type":"string","example":"GCXAJ3XJ3VK3JFH3QMDFOSKM2NMMZBSO3VIT6EUPQWSDW2J74M23RRSL"},"stellar_memo":{"type":"string"},"stellar_memo_type":{"type":"string"},"sep24_transaction_id":{"type":"string"},"created_at":{"type":"string","example":"2023-02-03T10:45:51.000Z"},"updated_at":{"type":"string","example":"2023-02-03T10:45:51.000Z"},"invitation_sent_at":{"type":"string","example":"2023-02-09T10:45:51.000Z"},"status":{"type":"string","enum":["DRAFT","READY","REGISTERED","FLAGGED"],"title":"ReceiversWalletStatus"},"status_history":{"type":"array","items":{"type":"object","properties":{"status":{"type":"string","enum":["DRAFT","READY","REGISTERED","FLAGGED"],"title":"ReceiversWalletStatus"},"timestamp":{"type":"string","format":"date-time","example":"2023-02-10T10:45:51Z"}},"title":"ReceiversWalletStatusHistoryEntry"}},"otp_confirmed_at":{"type":"string","format":"date-time","example":"2023-02-10T10:45:51Z"},"otp_confirmed_with":{"type":"string"}},"title":"ReceiverWalletLite"},"external_payment_id":{"type":"string","description":"Optional external payment identifier provided by the client.","example":"payment-001"},"created_at":{"type":"string","format":"date-time","example":"2023-02-03T10:45:51Z"},"updated_at":{"type":"string","format":"date-time","example":"2023-02-03T10:45:51Z"}},"title":"Payment"},"created_at":{"type":"string","format":"date-time","example":"2023-02-03T10:45:51Z"},"updated_at":{"type":"string","format":"date-time","example":"2023-02-03T10:45:51Z"}},"title":"DisbursementReceiver"}}},"title":"DisbursementReceiverPagination"}}}},"401":{"description":"Unauthorized","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"},"extras":{"type":"object","properties":{"status":{"type":"number"},"message":{"type":"string"}}}}},"example":{"error":"Not authorized","extras":{"status":401,"message":"Not authorized"}}}}},"403":{"description":"Forbidden","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"}}},"example":{"error":"Forbidden"}}}},"404":{"description":"Not Found","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"},"extras":{"type":"object","properties":{"status":{"type":"number"},"message":{"type":"string"}}}}},"example":{"error":"Not found","extras":{"status":404,"message":"Resource not found"}}}}}}}
 >
   
 </StatusCodes>
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/list-all-payments.api.mdx b/docs/platforms/stellar-disbursement-platform/api-reference/list-all-payments.api.mdx
index 942e9d1630..d76cc71d9f 100644
--- a/docs/platforms/stellar-disbursement-platform/api-reference/list-all-payments.api.mdx
+++ b/docs/platforms/stellar-disbursement-platform/api-reference/list-all-payments.api.mdx
@@ -66,7 +66,7 @@ Returns all individual payments matching the request criteria. This endpoint sup
 <StatusCodes
   id={undefined}
   label={undefined}
-  responses={{"200":{"description":"A paginated list of payments","content":{"application/json":{"schema":{"type":"object","properties":{"pagination":{"type":"object","properties":{"next":{"type":"string","example":"?page=3&page_limit=2"},"prev":{"type":"string","example":"?page=1&page_limit=2"},"pages":{"type":"integer","example":8},"total":{"type":"integer","example":16}},"title":"Pagination"},"data":{"type":"array","items":{"type":"object","properties":{"id":{"type":"string","example":"ddf22f55-3259-4822-a4e2-ce01334997f4"},"amount":{"type":"string","description":"The amount of the payment","example":"100.00"},"stellar_transaction_id":{"type":"string","description":"The ID of the transaction in the Stellar network. It can be used tio track the payment in the Stellar network using [Stellar Laboratory](https://laboratory.stellar.org/), or [StellarExpert](https://stellar.expert/).","example":"0b339d1c89d314186b8147c2af4c9a9ed5bbdbcd7ada8d138633907649b"},"circle_transfer_request_id":{"type":"string","description":"The Circle transfer request ID. It is only present when the payment was made using Circle.","example":"74a68b6a-3f67-424b-b8b0-e593a19d7463"},"stellar_operation_id":{"type":"string"},"status":{"type":"string","description":"The status of the payment","enum":["DRAFT","READY","PENDING","PAUSED","SUCCESS","FAILED","CANCELED"],"title":"PaymentStatus"},"status_history":{"type":"array","description":"An aggregated list of metadata objects containing the statuses and the timestamp of when these status changes occurred.","items":{"type":"object","properties":{"status":{"type":"string","description":"The status of the payment","enum":["DRAFT","READY","PENDING","PAUSED","SUCCESS","FAILED","CANCELED"],"title":"PaymentStatus"},"status_message":{"type":"string"},"timestamp":{"type":"string","format":"date-time","example":"2023-02-03T10:45:51Z"}},"title":"PaymentStatusHistoryEntry"},"title":"PaymentStatusHistory"},"type":{"type":"string","description":"The type of the payment.","enum":["DISBURSEMENT","DIRECT"]},"disbursement":{"type":"object","properties":{"id":{"type":"string","description":"The unique identifier of the disbursement","format":"uuid","example":"c51ba1d5-52d3-412f-a59c-6ef32d59ab43"},"name":{"type":"string","description":"The name of the disbursement","example":"disbursement-june-29"},"receiver_registration_message_template":{"type":"string","description":"The custom template used to send invitations to receivers. The `default` message isn't returned. In the message's content it's possible to add the following template variables: `{{.OrganizationName}}` which is the Organization Name configured and `{{.RegistrationLink}}` which is the link generated by SDP to send to the receiver (in case this is not present in the message, it's automatically appended at the end).","example":"You have a payment waiting for you from {{.OrganizationName}}. Click {{.RegistrationLink}} to register."},"registration_contact_type":{"type":"string","enum":["EMAIL","PHONE_NUMBER","EMAIL_AND_WALLET_ADDRESS","PHONE_NUMBER_AND_WALLET_ADDRESS"],"title":"RegistrationContactType"},"status":{"type":"string","enum":["DRAFT","READY","STARTED","PAUSED","COMPLETED"],"title":"DisbursementStatus"},"verification_field":{"type":"string","enum":["DATE_OF_BIRTH","YEAR_MONTH","PIN","NATIONAL_ID_NUMBER"],"title":"VerificationField"},"status_history":{"type":"array","items":{"type":"object","properties":{"user_id":{"type":"string","example":"3f351b9e-ed0f-40fa-a314-14757b42dab1"},"status":{"type":"string","enum":["DRAFT","READY","STARTED","PAUSED","COMPLETED"],"title":"DisbursementStatus"},"timestamp":{"type":"string","format":"date-time","example":"2023-02-03T10:45:51Z"}},"title":"DisbursementStatusHistoryEntry"},"title":"DisbursementStatusHistory"},"file_name":{"type":"string","example":"disbursement-feb-03-2023.csv"},"created_at":{"type":"string","description":"The creation timestamp of the disbursement","format":"date-time","example":"2023-06-30T01:22:57.831975Z"},"updated_at":{"type":"string","description":"The last update timestamp of the disbursement","format":"date-time","example":"2023-06-30T01:22:58.316511Z"}},"title":"DisbursementLite"},"asset":{"type":"object","properties":{"id":{"type":"string","example":"ffaec4b3-46b0-4db4-a4c4-6c3508057705"},"code":{"type":"string","description":"Asset code","example":"USDC"},"issuer":{"type":"string","description":"Asset issuer address","example":"GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"},"created_at":{"type":"string","format":"date-time","example":"2023-02-03T10:45:51Z"},"updated_at":{"type":"string","format":"date-time","example":"2023-02-03T10:45:51Z"},"deleted_at":{"type":"string","format":"date-time","example":"2023-06-03T10:55:51Z"}},"description":"The Stellar asset object","title":"Asset"},"receiver_wallet":{"type":"object","properties":{"id":{"type":"string","example":"803031d4-1d04-4879-b6d9-dc5641f9988e"},"receiver":{"type":"object","properties":{"id":{"type":"string","example":"029e2ed0-feb6-4c40-8b47-0836a85741a2"}},"title":"ReceiverLite"},"wallet":{"type":"object","properties":{"id":{"type":"string","example":"5ada9ed5-455a-4782-a0ee-160767e0deb1"},"name":{"type":"string","example":"Vibrant Assist"},"homepage":{"type":"string","example":"https://vibrantapp.com"},"sep_10_client_domain":{"type":"string","example":"api-dev.vibrantapp.com"},"deep_link_schema":{"type":"string","example":"https://vibrantapp.com/sdp-dev"},"enabled":{"type":"boolean","example":true},"user_managed":{"type":"boolean","example":false}},"title":"WalletLite"},"stellar_address":{"type":"string","example":"GCXAJ3XJ3VK3JFH3QMDFOSKM2NMMZBSO3VIT6EUPQWSDW2J74M23RRSL"},"stellar_memo":{"type":"string"},"stellar_memo_type":{"type":"string"},"sep24_transaction_id":{"type":"string"},"created_at":{"type":"string","example":"2023-02-03T10:45:51.000Z"},"updated_at":{"type":"string","example":"2023-02-03T10:45:51.000Z"},"invitation_sent_at":{"type":"string","example":"2023-02-09T10:45:51.000Z"},"status":{"type":"string","enum":["DRAFT","READY","REGISTERED","FLAGGED"],"title":"ReceiversWalletStatus"},"status_history":{"type":"array","items":{"type":"object","properties":{"status":{"type":"string","enum":["DRAFT","READY","REGISTERED","FLAGGED"],"title":"ReceiversWalletStatus"},"timestamp":{"type":"string","format":"date-time","example":"2023-02-10T10:45:51Z"}},"title":"ReceiversWalletStatusHistoryEntry"}},"otp_confirmed_at":{"type":"string","format":"date-time","example":"2023-02-10T10:45:51Z"},"otp_confirmed_with":{"type":"string"}},"title":"ReceiverWalletLite"},"external_payment_id":{"type":"string","description":"Optional external payment identifier provided by the client.","example":"payment-001"},"created_at":{"type":"string","format":"date-time","example":"2023-02-03T10:45:51Z"},"updated_at":{"type":"string","format":"date-time","example":"2023-02-03T10:45:51Z"}},"title":"Payment"}}},"title":"PaymentPagination"}}}},"401":{"description":"Unauthorized","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"},"extras":{"type":"object","properties":{"status":{"type":"number"},"message":{"type":"string"}}}},"example":{"error":"Not authorized","extras":{"status":401,"message":"Not authorized"}}},"example":{"error":"Not authorized","extras":{"status":401,"message":"Not authorized"}}}}},"403":{"description":"Forbidden","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"}},"example":{"error":"Forbidden"}},"example":{"error":"Forbidden"}}}}}}
+  responses={{"200":{"description":"A paginated list of payments","content":{"application/json":{"schema":{"type":"object","properties":{"pagination":{"type":"object","properties":{"next":{"type":"string","example":"?page=3&page_limit=2"},"prev":{"type":"string","example":"?page=1&page_limit=2"},"pages":{"type":"integer","example":8},"total":{"type":"integer","example":16}},"title":"Pagination"},"data":{"type":"array","items":{"type":"object","properties":{"id":{"type":"string","example":"ddf22f55-3259-4822-a4e2-ce01334997f4"},"amount":{"type":"string","description":"The amount of the payment","example":"100.00"},"stellar_transaction_id":{"type":"string","description":"The ID of the transaction in the Stellar network. It can be used tio track the payment in the Stellar network using [Stellar Laboratory](https://laboratory.stellar.org), or [StellarExpert](https://stellar.expert).","example":"0b339d1c89d314186b8147c2af4c9a9ed5bbdbcd7ada8d138633907649b"},"circle_transfer_request_id":{"type":"string","description":"The Circle transfer request ID. It is only present when the payment was made using Circle.","example":"74a68b6a-3f67-424b-b8b0-e593a19d7463"},"stellar_operation_id":{"type":"string"},"status":{"type":"string","description":"The status of the payment","enum":["DRAFT","READY","PENDING","PAUSED","SUCCESS","FAILED","CANCELED"],"title":"PaymentStatus"},"status_history":{"type":"array","description":"An aggregated list of metadata objects containing the statuses and the timestamp of when these status changes occurred.","items":{"type":"object","properties":{"status":{"type":"string","description":"The status of the payment","enum":["DRAFT","READY","PENDING","PAUSED","SUCCESS","FAILED","CANCELED"],"title":"PaymentStatus"},"status_message":{"type":"string"},"timestamp":{"type":"string","format":"date-time","example":"2023-02-03T10:45:51Z"}},"title":"PaymentStatusHistoryEntry"},"title":"PaymentStatusHistory"},"type":{"type":"string","description":"The type of the payment.","enum":["DISBURSEMENT","DIRECT"]},"disbursement":{"type":"object","properties":{"id":{"type":"string","description":"The unique identifier of the disbursement","format":"uuid","example":"c51ba1d5-52d3-412f-a59c-6ef32d59ab43"},"name":{"type":"string","description":"The name of the disbursement","example":"disbursement-june-29"},"receiver_registration_message_template":{"type":"string","description":"The custom template used to send invitations to receivers. The `default` message isn't returned. In the message's content it's possible to add the following template variables: `{{.OrganizationName}}` which is the Organization Name configured and `{{.RegistrationLink}}` which is the link generated by SDP to send to the receiver (in case this is not present in the message, it's automatically appended at the end).","example":"You have a payment waiting for you from {{.OrganizationName}}. Click {{.RegistrationLink}} to register."},"registration_contact_type":{"type":"string","enum":["EMAIL","PHONE_NUMBER","EMAIL_AND_WALLET_ADDRESS","PHONE_NUMBER_AND_WALLET_ADDRESS"],"title":"RegistrationContactType"},"status":{"type":"string","enum":["DRAFT","READY","STARTED","PAUSED","COMPLETED"],"title":"DisbursementStatus"},"verification_field":{"type":"string","enum":["DATE_OF_BIRTH","YEAR_MONTH","PIN","NATIONAL_ID_NUMBER"],"title":"VerificationField"},"status_history":{"type":"array","items":{"type":"object","properties":{"user_id":{"type":"string","example":"3f351b9e-ed0f-40fa-a314-14757b42dab1"},"status":{"type":"string","enum":["DRAFT","READY","STARTED","PAUSED","COMPLETED"],"title":"DisbursementStatus"},"timestamp":{"type":"string","format":"date-time","example":"2023-02-03T10:45:51Z"}},"title":"DisbursementStatusHistoryEntry"},"title":"DisbursementStatusHistory"},"file_name":{"type":"string","example":"disbursement-feb-03-2023.csv"},"created_at":{"type":"string","description":"The creation timestamp of the disbursement","format":"date-time","example":"2023-06-30T01:22:57.831975Z"},"updated_at":{"type":"string","description":"The last update timestamp of the disbursement","format":"date-time","example":"2023-06-30T01:22:58.316511Z"}},"title":"DisbursementLite"},"asset":{"type":"object","properties":{"id":{"type":"string","example":"ffaec4b3-46b0-4db4-a4c4-6c3508057705"},"code":{"type":"string","description":"Asset code","example":"USDC"},"issuer":{"type":"string","description":"Asset issuer address","example":"GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"},"created_at":{"type":"string","format":"date-time","example":"2023-02-03T10:45:51Z"},"updated_at":{"type":"string","format":"date-time","example":"2023-02-03T10:45:51Z"},"deleted_at":{"type":"string","format":"date-time","example":"2023-06-03T10:55:51Z"}},"description":"The Stellar asset object","title":"Asset"},"receiver_wallet":{"type":"object","properties":{"id":{"type":"string","example":"803031d4-1d04-4879-b6d9-dc5641f9988e"},"receiver":{"type":"object","properties":{"id":{"type":"string","example":"029e2ed0-feb6-4c40-8b47-0836a85741a2"}},"title":"ReceiverLite"},"wallet":{"type":"object","properties":{"id":{"type":"string","example":"5ada9ed5-455a-4782-a0ee-160767e0deb1"},"name":{"type":"string","example":"Vibrant Assist"},"homepage":{"type":"string","example":"https://vibrantapp.com"},"sep_10_client_domain":{"type":"string","example":"api-dev.vibrantapp.com"},"deep_link_schema":{"type":"string","example":"https://vibrantapp.com/sdp-dev"},"enabled":{"type":"boolean","example":true},"user_managed":{"type":"boolean","example":false}},"title":"WalletLite"},"stellar_address":{"type":"string","example":"GCXAJ3XJ3VK3JFH3QMDFOSKM2NMMZBSO3VIT6EUPQWSDW2J74M23RRSL"},"stellar_memo":{"type":"string"},"stellar_memo_type":{"type":"string"},"sep24_transaction_id":{"type":"string"},"created_at":{"type":"string","example":"2023-02-03T10:45:51.000Z"},"updated_at":{"type":"string","example":"2023-02-03T10:45:51.000Z"},"invitation_sent_at":{"type":"string","example":"2023-02-09T10:45:51.000Z"},"status":{"type":"string","enum":["DRAFT","READY","REGISTERED","FLAGGED"],"title":"ReceiversWalletStatus"},"status_history":{"type":"array","items":{"type":"object","properties":{"status":{"type":"string","enum":["DRAFT","READY","REGISTERED","FLAGGED"],"title":"ReceiversWalletStatus"},"timestamp":{"type":"string","format":"date-time","example":"2023-02-10T10:45:51Z"}},"title":"ReceiversWalletStatusHistoryEntry"}},"otp_confirmed_at":{"type":"string","format":"date-time","example":"2023-02-10T10:45:51Z"},"otp_confirmed_with":{"type":"string"}},"title":"ReceiverWalletLite"},"external_payment_id":{"type":"string","description":"Optional external payment identifier provided by the client.","example":"payment-001"},"created_at":{"type":"string","format":"date-time","example":"2023-02-03T10:45:51Z"},"updated_at":{"type":"string","format":"date-time","example":"2023-02-03T10:45:51Z"}},"title":"Payment"}}},"title":"PaymentPagination"}}}},"401":{"description":"Unauthorized","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"},"extras":{"type":"object","properties":{"status":{"type":"number"},"message":{"type":"string"}}}},"example":{"error":"Not authorized","extras":{"status":401,"message":"Not authorized"}}},"example":{"error":"Not authorized","extras":{"status":401,"message":"Not authorized"}}}}},"403":{"description":"Forbidden","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"}},"example":{"error":"Forbidden"}},"example":{"error":"Forbidden"}}}}}}
 >
   
 </StatusCodes>
diff --git a/docs/platforms/stellar-disbursement-platform/api-reference/retrieve-a-payment.api.mdx b/docs/platforms/stellar-disbursement-platform/api-reference/retrieve-a-payment.api.mdx
index 2a699c6120..877aac469d 100644
--- a/docs/platforms/stellar-disbursement-platform/api-reference/retrieve-a-payment.api.mdx
+++ b/docs/platforms/stellar-disbursement-platform/api-reference/retrieve-a-payment.api.mdx
@@ -66,7 +66,7 @@ Fetches detailed information on a specific payment by  `id `.
 <StatusCodes
   id={undefined}
   label={undefined}
-  responses={{"200":{"description":"Payment details","content":{"application/json":{"schema":{"type":"object","properties":{"id":{"type":"string","example":"ddf22f55-3259-4822-a4e2-ce01334997f4"},"amount":{"type":"string","description":"The amount of the payment","example":"100.00"},"stellar_transaction_id":{"type":"string","description":"The ID of the transaction in the Stellar network. It can be used tio track the payment in the Stellar network using [Stellar Laboratory](https://laboratory.stellar.org/), or [StellarExpert](https://stellar.expert/).","example":"0b339d1c89d314186b8147c2af4c9a9ed5bbdbcd7ada8d138633907649b"},"circle_transfer_request_id":{"type":"string","description":"The Circle transfer request ID. It is only present when the payment was made using Circle.","example":"74a68b6a-3f67-424b-b8b0-e593a19d7463"},"stellar_operation_id":{"type":"string"},"status":{"type":"string","description":"The status of the payment","enum":["DRAFT","READY","PENDING","PAUSED","SUCCESS","FAILED","CANCELED"],"title":"PaymentStatus"},"status_history":{"type":"array","description":"An aggregated list of metadata objects containing the statuses and the timestamp of when these status changes occurred.","items":{"type":"object","properties":{"status":{"type":"string","description":"The status of the payment","enum":["DRAFT","READY","PENDING","PAUSED","SUCCESS","FAILED","CANCELED"],"title":"PaymentStatus"},"status_message":{"type":"string"},"timestamp":{"type":"string","format":"date-time","example":"2023-02-03T10:45:51Z"}},"title":"PaymentStatusHistoryEntry"},"title":"PaymentStatusHistory"},"type":{"type":"string","description":"The type of the payment.","enum":["DISBURSEMENT","DIRECT"]},"disbursement":{"type":"object","properties":{"id":{"type":"string","description":"The unique identifier of the disbursement","format":"uuid","example":"c51ba1d5-52d3-412f-a59c-6ef32d59ab43"},"name":{"type":"string","description":"The name of the disbursement","example":"disbursement-june-29"},"receiver_registration_message_template":{"type":"string","description":"The custom template used to send invitations to receivers. The `default` message isn't returned. In the message's content it's possible to add the following template variables: `{{.OrganizationName}}` which is the Organization Name configured and `{{.RegistrationLink}}` which is the link generated by SDP to send to the receiver (in case this is not present in the message, it's automatically appended at the end).","example":"You have a payment waiting for you from {{.OrganizationName}}. Click {{.RegistrationLink}} to register."},"registration_contact_type":{"type":"string","enum":["EMAIL","PHONE_NUMBER","EMAIL_AND_WALLET_ADDRESS","PHONE_NUMBER_AND_WALLET_ADDRESS"],"title":"RegistrationContactType"},"status":{"type":"string","enum":["DRAFT","READY","STARTED","PAUSED","COMPLETED"],"title":"DisbursementStatus"},"verification_field":{"type":"string","enum":["DATE_OF_BIRTH","YEAR_MONTH","PIN","NATIONAL_ID_NUMBER"],"title":"VerificationField"},"status_history":{"type":"array","items":{"type":"object","properties":{"user_id":{"type":"string","example":"3f351b9e-ed0f-40fa-a314-14757b42dab1"},"status":{"type":"string","enum":["DRAFT","READY","STARTED","PAUSED","COMPLETED"],"title":"DisbursementStatus"},"timestamp":{"type":"string","format":"date-time","example":"2023-02-03T10:45:51Z"}},"title":"DisbursementStatusHistoryEntry"},"title":"DisbursementStatusHistory"},"file_name":{"type":"string","example":"disbursement-feb-03-2023.csv"},"created_at":{"type":"string","description":"The creation timestamp of the disbursement","format":"date-time","example":"2023-06-30T01:22:57.831975Z"},"updated_at":{"type":"string","description":"The last update timestamp of the disbursement","format":"date-time","example":"2023-06-30T01:22:58.316511Z"}},"title":"DisbursementLite"},"asset":{"type":"object","properties":{"id":{"type":"string","example":"ffaec4b3-46b0-4db4-a4c4-6c3508057705"},"code":{"type":"string","description":"Asset code","example":"USDC"},"issuer":{"type":"string","description":"Asset issuer address","example":"GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"},"created_at":{"type":"string","format":"date-time","example":"2023-02-03T10:45:51Z"},"updated_at":{"type":"string","format":"date-time","example":"2023-02-03T10:45:51Z"},"deleted_at":{"type":"string","format":"date-time","example":"2023-06-03T10:55:51Z"}},"description":"The Stellar asset object","title":"Asset"},"receiver_wallet":{"type":"object","properties":{"id":{"type":"string","example":"803031d4-1d04-4879-b6d9-dc5641f9988e"},"receiver":{"type":"object","properties":{"id":{"type":"string","example":"029e2ed0-feb6-4c40-8b47-0836a85741a2"}},"title":"ReceiverLite"},"wallet":{"type":"object","properties":{"id":{"type":"string","example":"5ada9ed5-455a-4782-a0ee-160767e0deb1"},"name":{"type":"string","example":"Vibrant Assist"},"homepage":{"type":"string","example":"https://vibrantapp.com"},"sep_10_client_domain":{"type":"string","example":"api-dev.vibrantapp.com"},"deep_link_schema":{"type":"string","example":"https://vibrantapp.com/sdp-dev"},"enabled":{"type":"boolean","example":true},"user_managed":{"type":"boolean","example":false}},"title":"WalletLite"},"stellar_address":{"type":"string","example":"GCXAJ3XJ3VK3JFH3QMDFOSKM2NMMZBSO3VIT6EUPQWSDW2J74M23RRSL"},"stellar_memo":{"type":"string"},"stellar_memo_type":{"type":"string"},"sep24_transaction_id":{"type":"string"},"created_at":{"type":"string","example":"2023-02-03T10:45:51.000Z"},"updated_at":{"type":"string","example":"2023-02-03T10:45:51.000Z"},"invitation_sent_at":{"type":"string","example":"2023-02-09T10:45:51.000Z"},"status":{"type":"string","enum":["DRAFT","READY","REGISTERED","FLAGGED"],"title":"ReceiversWalletStatus"},"status_history":{"type":"array","items":{"type":"object","properties":{"status":{"type":"string","enum":["DRAFT","READY","REGISTERED","FLAGGED"],"title":"ReceiversWalletStatus"},"timestamp":{"type":"string","format":"date-time","example":"2023-02-10T10:45:51Z"}},"title":"ReceiversWalletStatusHistoryEntry"}},"otp_confirmed_at":{"type":"string","format":"date-time","example":"2023-02-10T10:45:51Z"},"otp_confirmed_with":{"type":"string"}},"title":"ReceiverWalletLite"},"external_payment_id":{"type":"string","description":"Optional external payment identifier provided by the client.","example":"payment-001"},"created_at":{"type":"string","format":"date-time","example":"2023-02-03T10:45:51Z"},"updated_at":{"type":"string","format":"date-time","example":"2023-02-03T10:45:51Z"}},"title":"Payment"}}}},"401":{"description":"Unauthorized","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"},"extras":{"type":"object","properties":{"status":{"type":"number"},"message":{"type":"string"}}}},"example":{"error":"Not authorized","extras":{"status":401,"message":"Not authorized"}}},"example":{"error":"Not authorized","extras":{"status":401,"message":"Not authorized"}}}}},"403":{"description":"Forbidden","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"}},"example":{"error":"Forbidden"}},"example":{"error":"Forbidden"}}}},"404":{"description":"Not Found","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"},"extras":{"type":"object","properties":{"status":{"type":"number"},"message":{"type":"string"}}}},"example":{"error":"Not found","extras":{"status":404,"message":"Payment not found"}}},"example":{"error":"Not found","extras":{"status":404,"message":"Payment not found"}}}}}}}
+  responses={{"200":{"description":"Payment details","content":{"application/json":{"schema":{"type":"object","properties":{"id":{"type":"string","example":"ddf22f55-3259-4822-a4e2-ce01334997f4"},"amount":{"type":"string","description":"The amount of the payment","example":"100.00"},"stellar_transaction_id":{"type":"string","description":"The ID of the transaction in the Stellar network. It can be used tio track the payment in the Stellar network using [Stellar Laboratory](https://laboratory.stellar.org), or [StellarExpert](https://stellar.expert).","example":"0b339d1c89d314186b8147c2af4c9a9ed5bbdbcd7ada8d138633907649b"},"circle_transfer_request_id":{"type":"string","description":"The Circle transfer request ID. It is only present when the payment was made using Circle.","example":"74a68b6a-3f67-424b-b8b0-e593a19d7463"},"stellar_operation_id":{"type":"string"},"status":{"type":"string","description":"The status of the payment","enum":["DRAFT","READY","PENDING","PAUSED","SUCCESS","FAILED","CANCELED"],"title":"PaymentStatus"},"status_history":{"type":"array","description":"An aggregated list of metadata objects containing the statuses and the timestamp of when these status changes occurred.","items":{"type":"object","properties":{"status":{"type":"string","description":"The status of the payment","enum":["DRAFT","READY","PENDING","PAUSED","SUCCESS","FAILED","CANCELED"],"title":"PaymentStatus"},"status_message":{"type":"string"},"timestamp":{"type":"string","format":"date-time","example":"2023-02-03T10:45:51Z"}},"title":"PaymentStatusHistoryEntry"},"title":"PaymentStatusHistory"},"type":{"type":"string","description":"The type of the payment.","enum":["DISBURSEMENT","DIRECT"]},"disbursement":{"type":"object","properties":{"id":{"type":"string","description":"The unique identifier of the disbursement","format":"uuid","example":"c51ba1d5-52d3-412f-a59c-6ef32d59ab43"},"name":{"type":"string","description":"The name of the disbursement","example":"disbursement-june-29"},"receiver_registration_message_template":{"type":"string","description":"The custom template used to send invitations to receivers. The `default` message isn't returned. In the message's content it's possible to add the following template variables: `{{.OrganizationName}}` which is the Organization Name configured and `{{.RegistrationLink}}` which is the link generated by SDP to send to the receiver (in case this is not present in the message, it's automatically appended at the end).","example":"You have a payment waiting for you from {{.OrganizationName}}. Click {{.RegistrationLink}} to register."},"registration_contact_type":{"type":"string","enum":["EMAIL","PHONE_NUMBER","EMAIL_AND_WALLET_ADDRESS","PHONE_NUMBER_AND_WALLET_ADDRESS"],"title":"RegistrationContactType"},"status":{"type":"string","enum":["DRAFT","READY","STARTED","PAUSED","COMPLETED"],"title":"DisbursementStatus"},"verification_field":{"type":"string","enum":["DATE_OF_BIRTH","YEAR_MONTH","PIN","NATIONAL_ID_NUMBER"],"title":"VerificationField"},"status_history":{"type":"array","items":{"type":"object","properties":{"user_id":{"type":"string","example":"3f351b9e-ed0f-40fa-a314-14757b42dab1"},"status":{"type":"string","enum":["DRAFT","READY","STARTED","PAUSED","COMPLETED"],"title":"DisbursementStatus"},"timestamp":{"type":"string","format":"date-time","example":"2023-02-03T10:45:51Z"}},"title":"DisbursementStatusHistoryEntry"},"title":"DisbursementStatusHistory"},"file_name":{"type":"string","example":"disbursement-feb-03-2023.csv"},"created_at":{"type":"string","description":"The creation timestamp of the disbursement","format":"date-time","example":"2023-06-30T01:22:57.831975Z"},"updated_at":{"type":"string","description":"The last update timestamp of the disbursement","format":"date-time","example":"2023-06-30T01:22:58.316511Z"}},"title":"DisbursementLite"},"asset":{"type":"object","properties":{"id":{"type":"string","example":"ffaec4b3-46b0-4db4-a4c4-6c3508057705"},"code":{"type":"string","description":"Asset code","example":"USDC"},"issuer":{"type":"string","description":"Asset issuer address","example":"GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"},"created_at":{"type":"string","format":"date-time","example":"2023-02-03T10:45:51Z"},"updated_at":{"type":"string","format":"date-time","example":"2023-02-03T10:45:51Z"},"deleted_at":{"type":"string","format":"date-time","example":"2023-06-03T10:55:51Z"}},"description":"The Stellar asset object","title":"Asset"},"receiver_wallet":{"type":"object","properties":{"id":{"type":"string","example":"803031d4-1d04-4879-b6d9-dc5641f9988e"},"receiver":{"type":"object","properties":{"id":{"type":"string","example":"029e2ed0-feb6-4c40-8b47-0836a85741a2"}},"title":"ReceiverLite"},"wallet":{"type":"object","properties":{"id":{"type":"string","example":"5ada9ed5-455a-4782-a0ee-160767e0deb1"},"name":{"type":"string","example":"Vibrant Assist"},"homepage":{"type":"string","example":"https://vibrantapp.com"},"sep_10_client_domain":{"type":"string","example":"api-dev.vibrantapp.com"},"deep_link_schema":{"type":"string","example":"https://vibrantapp.com/sdp-dev"},"enabled":{"type":"boolean","example":true},"user_managed":{"type":"boolean","example":false}},"title":"WalletLite"},"stellar_address":{"type":"string","example":"GCXAJ3XJ3VK3JFH3QMDFOSKM2NMMZBSO3VIT6EUPQWSDW2J74M23RRSL"},"stellar_memo":{"type":"string"},"stellar_memo_type":{"type":"string"},"sep24_transaction_id":{"type":"string"},"created_at":{"type":"string","example":"2023-02-03T10:45:51.000Z"},"updated_at":{"type":"string","example":"2023-02-03T10:45:51.000Z"},"invitation_sent_at":{"type":"string","example":"2023-02-09T10:45:51.000Z"},"status":{"type":"string","enum":["DRAFT","READY","REGISTERED","FLAGGED"],"title":"ReceiversWalletStatus"},"status_history":{"type":"array","items":{"type":"object","properties":{"status":{"type":"string","enum":["DRAFT","READY","REGISTERED","FLAGGED"],"title":"ReceiversWalletStatus"},"timestamp":{"type":"string","format":"date-time","example":"2023-02-10T10:45:51Z"}},"title":"ReceiversWalletStatusHistoryEntry"}},"otp_confirmed_at":{"type":"string","format":"date-time","example":"2023-02-10T10:45:51Z"},"otp_confirmed_with":{"type":"string"}},"title":"ReceiverWalletLite"},"external_payment_id":{"type":"string","description":"Optional external payment identifier provided by the client.","example":"payment-001"},"created_at":{"type":"string","format":"date-time","example":"2023-02-03T10:45:51Z"},"updated_at":{"type":"string","format":"date-time","example":"2023-02-03T10:45:51Z"}},"title":"Payment"}}}},"401":{"description":"Unauthorized","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"},"extras":{"type":"object","properties":{"status":{"type":"number"},"message":{"type":"string"}}}},"example":{"error":"Not authorized","extras":{"status":401,"message":"Not authorized"}}},"example":{"error":"Not authorized","extras":{"status":401,"message":"Not authorized"}}}}},"403":{"description":"Forbidden","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"}},"example":{"error":"Forbidden"}},"example":{"error":"Forbidden"}}}},"404":{"description":"Not Found","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"},"extras":{"type":"object","properties":{"status":{"type":"number"},"message":{"type":"string"}}}},"example":{"error":"Not found","extras":{"status":404,"message":"Payment not found"}}},"example":{"error":"Not found","extras":{"status":404,"message":"Payment not found"}}}}}}}
 >
   
 </StatusCodes>
diff --git a/docs/tokens/README.mdx b/docs/tokens/README.mdx
index e5ee26ead1..523b489a7b 100644
--- a/docs/tokens/README.mdx
+++ b/docs/tokens/README.mdx
@@ -35,7 +35,7 @@ Stellar’s transactions are fast and cost-effective, making the network great f
 Stellar assets:
 
 - Are compatible with Stellar ecosystem products (such as Stellar wallets) and other ecosystem products (such as exchanges).
-- Benefit from [anchors](../learn/fundamentals/anchors.mdx), the bridges between the Stellar network and traditional financial systems. Explore the global [Stellar anchor directory](https://anchors.stellar.org/) for further details.
+- Benefit from [anchors](../learn/fundamentals/anchors.mdx), the bridges between the Stellar network and traditional financial systems. Explore the global [Stellar anchor directory](https://anchors.stellar.org) for further details.
 - Give the issuer granular control over asset management with features that allow the issuer to [name the asset](./control-asset-access.mdx#naming-an-asset), [determine access control](./control-asset-access.mdx#controlling-access-to-an-asset-with-flags), [limit asset supply](./control-asset-access.mdx#limiting-the-supply-of-an-asset), [publish asset information](./publishing-asset-info.mdx), and [ensure compliance](./anatomy-of-an-asset.mdx#compliance).
 
 :::note
diff --git a/docs/tokens/anatomy-of-an-asset.mdx b/docs/tokens/anatomy-of-an-asset.mdx
index 6555dd8a0e..a2af8171bf 100644
--- a/docs/tokens/anatomy-of-an-asset.mdx
+++ b/docs/tokens/anatomy-of-an-asset.mdx
@@ -57,7 +57,7 @@ All assets issued by Stellar accounts (G…` addresses) are **Stellar Assets**.
 - Has the benefits of Stellar assets (low cost, less computationally expensive), making these great for remittances and micropayments.
 - Can be used in Stellar smart contracts via SAC with a [SEP-41][sep-41] interface.
 - Maintains issuer controls and trustline semantics even when used from contracts.
-- Wide ecosystem wallet and indexer support. Assets issued by `G...` accounts are compatible with Stellar ecosystem products (such as Stellar wallets) and other ecosystem products (such as exchanges). For example, benefit from [anchors](../learn/fundamentals/anchors.mdx), the bridges between the Stellar network and traditional financial systems. Explore the global [Stellar anchor directory](https://anchors.stellar.org/) for further details.
+- Wide ecosystem wallet and indexer support. Assets issued by `G...` accounts are compatible with Stellar ecosystem products (such as Stellar wallets) and other ecosystem products (such as exchanges). For example, benefit from [anchors](../learn/fundamentals/anchors.mdx), the bridges between the Stellar network and traditional financial systems. Explore the global [Stellar anchor directory](https://anchors.stellar.org) for further details.
 - Give the issuer granular control over asset management with features that allow the issuer to [name the asset](./control-asset-access.mdx#naming-an-asset), [determine access control](./control-asset-access.mdx#controlling-access-to-an-asset-with-flags), [limit asset supply](./control-asset-access.mdx#limiting-the-supply-of-an-asset), [publish asset information](./publishing-asset-info.mdx), and [ensure compliance](./anatomy-of-an-asset.mdx#compliance). Stellar assets provide built-in issuer control mechanisms by default. In contrast, contract tokens offer flexibility but require all control and compliance features to be explicitly designed and implemented in the contract.
 - Native operations on Stellar Assets emit standardized events through the Stellar Asset Contract, allowing off-chain systems and indexers to observe asset activity in a uniform way. Event semantics are defined at the protocol level according to [CAP-0067](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0067.md).
 - Operations on Stellar Assets emit the same standardized events defined by SEP-41, because the Stellar Asset Contract implements the SEP-41 token interface, Payment operations on Stellar Assets surface identical transfer events, allowing off-chain systems and indexers to observe asset activity through a uniform way.
diff --git a/docs/tokens/publishing-asset-info.mdx b/docs/tokens/publishing-asset-info.mdx
index 9eab91a7a8..22b738c321 100644
--- a/docs/tokens/publishing-asset-info.mdx
+++ b/docs/tokens/publishing-asset-info.mdx
@@ -38,7 +38,7 @@ Required field for all asset issuers:
 
 - `ACCOUNTS`: A list of public keys for all the Stellar accounts associated with your asset.
 
-Listing your public keys lets users confirm that you own them. For example, when [google.com](https://google.com/) hosts a `stellar.toml` file, users can be sure that only the accounts listed on it belong to Google. If someone then says, "You need to pay your Google bill this month, send payment to address GIAMGOOGLEIPROMISE", but that key is not listed on Google's `stellar.toml`, then users know not to trust it.
+Listing your public keys lets users confirm that you own them. For example, when [google.com](https://google.com) hosts a `stellar.toml` file, users can be sure that only the accounts listed on it belong to Google. If someone then says, "You need to pay your Google bill this month, send payment to address GIAMGOOGLEIPROMISE", but that key is not listed on Google's `stellar.toml`, then users know not to trust it.
 
 There are several fields where you list information about your Stellar integration to aid in discoverability. If you are an anchor service, and you have set up infrastructure to interoperate with wallets and allow for in-app deposit and withdrawal of assets, make sure to include the locations of your servers on your `stellar.toml` file so those wallets know where to find relevant endpoints to query. In particular, list these:
 
diff --git a/docs/tools/developer-tools/analytics-platforms.mdx b/docs/tools/developer-tools/analytics-platforms.mdx
index db7633b35a..502c48eff6 100644
--- a/docs/tools/developer-tools/analytics-platforms.mdx
+++ b/docs/tools/developer-tools/analytics-platforms.mdx
@@ -13,7 +13,7 @@ There's a wide range of analytics platforms that make exploring Stellar network
 
 Artemis allows you to evaluate, compare and analyze trending chains and dApps across various metrics in one terminal. They offer pre-built dashboards and the ability to create your own
 
-### [Dune](https://dune.com/)
+### [Dune](https://dune.com)
 
 Dune is a web-based platform that allows you to query Stellar network data and aggregate it into beautiful dashboards.
 
diff --git a/docs/tools/developer-tools/anchor-tools.mdx b/docs/tools/developer-tools/anchor-tools.mdx
index 533c3f4175..ce08fca464 100644
--- a/docs/tools/developer-tools/anchor-tools.mdx
+++ b/docs/tools/developer-tools/anchor-tools.mdx
@@ -11,10 +11,10 @@ sidebar_position: 20
 
 View all anchors on Stellar, their currencies, and where they operate.
 
-### [Demo Wallet](https://demo-wallet.stellar.org/)
+### [Demo Wallet](https://demo-wallet.stellar.org)
 
 An application for interactively testing anchor services. Lets financial application developers test their integrations and learn how Stellar ecosystem protocols (SEPs) work; use the demo wallet to test Regulated Assets (SEP-8), Hosted Deposit and Withdrawal (SEP-24), and Cross-Border Payments (SEP-31) with any home domain that has a Stellar Info File (also known as SEP-1, or a stellar.toml file).
 
-### [Anchor Test Suite](https://anchor-tests.stellar.org/)
+### [Anchor Test Suite](https://anchor-tests.stellar.org)
 
 A test suite for validating SEP6, SEP24, SEP31 transfer servers.
diff --git a/docs/tools/developer-tools/block-explorers.mdx b/docs/tools/developer-tools/block-explorers.mdx
index a266145231..3b4f25ffc7 100644
--- a/docs/tools/developer-tools/block-explorers.mdx
+++ b/docs/tools/developer-tools/block-explorers.mdx
@@ -13,10 +13,10 @@ Block explorers exist to publicly display blockchain data in an easily digestibl
 
 Explore transactions and network activity with StellarExpert. Check stats specific to an asset code, transaction hash, account address, or ledger sequence number. Not available for Futurenet.
 
-### [StellarChain](https://stellarchain.io/)
+### [StellarChain](https://stellarchain.io)
 
 Explore transactions and network activity for Stellar’s networks, including Futurenet.
 
-### [Stellar Explorer](https://steexp.com/)
+### [Stellar Explorer](https://steexp.com)
 
 Check data related to payments, accounts, deployed contracts, and more for Stellar’s Futurenet, Testnet, and Mainnet.
diff --git a/docs/tools/developer-tools/network-insights.mdx b/docs/tools/developer-tools/network-insights.mdx
index 51a2edc5e6..e0ab69c28c 100644
--- a/docs/tools/developer-tools/network-insights.mdx
+++ b/docs/tools/developer-tools/network-insights.mdx
@@ -7,6 +7,6 @@ sidebar_position: 85
 
 # Network Insights
 
-### [StellarFee](https://stellarfee.expert/)
+### [StellarFee](https://stellarfee.expert)
 
 A GUI tool which is a useful fee estimator, transaction simulator to find the resources consumed and the expected fees for a transaction.
diff --git a/docs/tools/developer-tools/network-status.mdx b/docs/tools/developer-tools/network-status.mdx
index e2bc57b7b4..0ad0562865 100644
--- a/docs/tools/developer-tools/network-status.mdx
+++ b/docs/tools/developer-tools/network-status.mdx
@@ -7,14 +7,14 @@ sidebar_position: 90
 
 # Network Status
 
-### [Dashboard](https://dashboard.stellar.org/)
+### [Dashboard](https://dashboard.stellar.org)
 
 Displays the current status of the Testnet and Mainnet. Monitor fee stats, recent operations, lumen supply, and more.
 
-### [Stellarbeat](https://stellarbeat.io/)
+### [Stellarbeat](https://stellarbeat.io)
 
 View Stellar network nodes and visualize consensus.
 
-### [Status Page](https://status.stellar.org/)
+### [Status Page](https://status.stellar.org)
 
 Tracks network incidents and scheduled maintenance for the Testnet and Mainnet. Subscribe to updates to be notified about important events, including protocol upgrades and Testnet resets.
diff --git a/docs/tools/developer-tools/online-ide.mdx b/docs/tools/developer-tools/online-ide.mdx
index e163ef7480..891f1c4c63 100644
--- a/docs/tools/developer-tools/online-ide.mdx
+++ b/docs/tools/developer-tools/online-ide.mdx
@@ -7,6 +7,6 @@ sidebar_position: 72
 
 # Online IDE
 
-### [Soropg](https://soropg.com/)
+### [Soropg](https://soropg.com)
 
 Soropg is an online IDE specifically designed for Stellar smart contract development. It provides a browser-based environment where developers can write, compile, and test Stellar smart contracts without needing to set up a local development environment.
diff --git a/docs/tools/developer-tools/security-tools.mdx b/docs/tools/developer-tools/security-tools.mdx
index 9c2429e231..13ae7c3117 100644
--- a/docs/tools/developer-tools/security-tools.mdx
+++ b/docs/tools/developer-tools/security-tools.mdx
@@ -7,11 +7,11 @@ sidebar_position: 115
 
 # Security Tools
 
-### [Scout: Bug Fighter](https://www.coinfabrik.com/products/scout/)
+### [Scout: Bug Fighter](https://www.coinfabrik.com/products/scout)
 
 A static code analysis tool built to assist Soroban developers and auditors in identifying potential security threats and applying best practices.
 
-### [Almanax](https://www.almanax.ai/)
+### [Almanax](https://www.almanax.ai)
 
 Almanax is an AI security engineer designed to help teams prevent hacks.
 
diff --git a/docs/tools/developer-tools/wallets.mdx b/docs/tools/developer-tools/wallets.mdx
index b7862ea565..82629013ca 100644
--- a/docs/tools/developer-tools/wallets.mdx
+++ b/docs/tools/developer-tools/wallets.mdx
@@ -7,9 +7,9 @@ sidebar_position: 130
 
 # Wallet Integration
 
-### [Stellar Wallet Kit](https://github.com/Creit-Tech/Stellar-Wallets-Kit/)
+### [Stellar Wallet Kit](https://github.com/Creit-Tech/Stellar-Wallets-Kit)
 
-A simple-to-use wallet kit to manage integration to multiple Stellar ecosystem wallet. Learn more about how to integrate this library from [the Stellar Wallets Kit Docs](https://stellarwalletskit.dev/).
+A simple-to-use wallet kit to manage integration to multiple Stellar ecosystem wallet. Learn more about how to integrate this library from [the Stellar Wallets Kit Docs](https://stellarwalletskit.dev).
 
 ![Stellar Wallets Kit](/assets/dev-tools/stellar-wallet-kit.gif)
 
@@ -26,11 +26,11 @@ The Stellar Wallets Kit supports many wallets including:
 - xBull
 - HOT Wallet
 
-### [Account Viewer](https://accountviewer.stellar.org/)
+### [Account Viewer](https://accountviewer.stellar.org)
 
 A stripped-down wallet where you can check an account’s XLM balance and send simple payments on Testnet and Mainnet. Account Viewer's [source code](https://github.com/stellar/account-viewer-v2) is also useful and instructive for developers building wallet-related features into their applications.
 
-### [Freighter Wallet](https://www.freighter.app/)
+### [Freighter Wallet](https://www.freighter.app)
 
 SDF’s flagship non-custodial wallet extension that allows users to sign Stellar transactions via their browser. Freighter wallet's codebase is open sourced here: https://github.com/stellar/freighter.
 
@@ -45,9 +45,9 @@ Read the [docs](https://docs.near.org/chain-abstraction/intents/overview).
 Estimates the XLM requirements for wallets looking to use sponsored reserves and fee-bump transactions to cover account creation, transaction fees, trustlines, and more.
 
 - [Simplified spreadsheet](https://docs.google.com/spreadsheets/d/1Vhk__s-ZrJLEgEs3N2oGEsI35RKPixD5w-qQ6uGYnO0/edit?gid=270060868#gid=270060868)
-- [Tutorial article and video](https://cheesecakelabs.com/blog/stellar-lumens-xlm-cost-estimator/)
+- [Tutorial article and video](https://cheesecakelabs.com/blog/stellar-lumens-xlm-cost-estimator)
 
-### [Dfns](https://www.dfns.co/)
+### [Dfns](https://www.dfns.co)
 
 A wallet-as-a-service platform that streamlines digital asset operations, offering full wallet feature support, including automatic detection of asset and NFT balances (when applicable), on-chain transfer history, asset transfers, transaction broadcasting, and signature generation.
 
diff --git a/docs/tools/infra-tools/cross-chain.mdx b/docs/tools/infra-tools/cross-chain.mdx
index e34c707931..92b4e6faad 100644
--- a/docs/tools/infra-tools/cross-chain.mdx
+++ b/docs/tools/infra-tools/cross-chain.mdx
@@ -6,7 +6,7 @@ sidebar_position: 10
 
 Bridges and messaging layers that connect different blockchains.
 
-## [Axelar](https://www.axelar.network/)
+## [Axelar](https://www.axelar.network)
 
 Axelar Network is the universal interoperability network that securely connects all blockchain ecosystems, applications, assets, and users.
 
@@ -20,7 +20,7 @@ General Message Passing (GMP) is a cross-chain communication protocol that allow
 - Receive and process messages from contracts on other chains.
 - Execute cross-chain operations securely and efficiently.
 
-[Dive into Stellar GMP documentation →](https://docs.axelar.dev/dev/general-message-passing/stellar-gmp/intro/)
+[Dive into Stellar GMP documentation →](https://docs.axelar.dev/dev/general-message-passing/stellar-gmp/intro)
 
 ### Learn about the Stellar Interchain Token Service (ITS)
 
@@ -30,4 +30,4 @@ The Interchain Token Service (ITS) enables tokens to scale across multiple chain
 - Connecting existing Stellar tokens to other blockchain ecosystems.
 - Secure transfers of tokens between Stellar and other chains.
 
-[Learn how to use Axelar's ITS with Stellar →](https://docs.axelar.dev/dev/send-tokens/stellar/intro/)
+[Learn how to use Axelar's ITS with Stellar →](https://docs.axelar.dev/dev/send-tokens/stellar/intro)
diff --git a/docs/tools/lab/quickstart-with-lab.mdx b/docs/tools/lab/quickstart-with-lab.mdx
index 9f4815a085..c0c35b5e3a 100644
--- a/docs/tools/lab/quickstart-with-lab.mdx
+++ b/docs/tools/lab/quickstart-with-lab.mdx
@@ -7,7 +7,7 @@
 ## Prerequisites
 
 - [Stellar CLI](../cli/install-cli.mdx)
-- [Docker](https://www.docker.com/)
+- [Docker](https://www.docker.com)
 
 ## Start Quickstart
 
diff --git a/docs/tools/lab/smart-contracts/upload-deploy-contract.mdx b/docs/tools/lab/smart-contracts/upload-deploy-contract.mdx
index 175b05ebb4..6079110b56 100644
--- a/docs/tools/lab/smart-contracts/upload-deploy-contract.mdx
+++ b/docs/tools/lab/smart-contracts/upload-deploy-contract.mdx
@@ -34,6 +34,6 @@ If the requested `WASM` bytecode is already uploaded on the network, the Lab ski
 
 ## Deploy Phase
 
-During the "Deploy phase", the Lab checks whether the `WASM` contract metadata has a constructor and what arguments it requires. Once all the required fields are filled, it creates a deployment transaction. After the transaction is signed and successfully submitted, you can check your contract on blockchain explorers like [Stellar.Expert](https://stellar.expert/explorer/) or [Stellar Lab's contract explorer](https://lab.stellar.org/smart-contracts/contract-explorer) right away.
+During the "Deploy phase", the Lab checks whether the `WASM` contract metadata has a constructor and what arguments it requires. Once all the required fields are filled, it creates a deployment transaction. After the transaction is signed and successfully submitted, you can check your contract on blockchain explorers like [Stellar.Expert](https://stellar.expert/explorer) or [Stellar Lab's contract explorer](https://lab.stellar.org/smart-contracts/contract-explorer) right away.
 
 ![Lab: Upload and Deploy Contract - deploying contract](/assets/lab/lab-deploy-contract.gif)
diff --git a/docs/tools/openzeppelin-contracts.mdx b/docs/tools/openzeppelin-contracts.mdx
index 9b7a9d9b0b..5fe9a9fa69 100644
--- a/docs/tools/openzeppelin-contracts.mdx
+++ b/docs/tools/openzeppelin-contracts.mdx
@@ -11,7 +11,7 @@ sidebar_position: 44
 
 OpenZeppelin is bringing its trusted [smart contracts libraries](https://github.com/OpenZeppelin/stellar-contracts) and developer workflows to Stellar, a Rust-based blockchain. Developers can build payments, stablecoins, and DeFi apps on Stellar using familiar, audited building blocks. To see more, go to: https://www.openzeppelin.com/networks/stellar.
 
-For latest OpenZeppelin developer docs, please visit: [https://docs.openzeppelin.com/stellar-contracts](https://docs.openzeppelin.com/stellar-contracts/).
+For latest OpenZeppelin developer docs, please visit: [https://docs.openzeppelin.com/stellar-contracts](https://docs.openzeppelin.com/stellar-contracts).
 
 ::::
 
@@ -124,7 +124,7 @@ To provide feedback on these contracts and utilties, please open issues at: [htt
 
 - [Relayer](https://github.com/OpenZeppelin/openzeppelin-relayer): Infrastructure for relaying transactions on Stellar.
 - [Monitor](https://github.com/OpenZeppelin/openzeppelin-monitor): Infrastructure tool for monitoring blockchain events and transactions.
-- [UI Builder](https://builder.openzeppelin.com/): Open source tool for creating UI forms for contracts.
-- [MCP Server](https://mcp.openzeppelin.com/): Generate secure Stellar smart contracts based on OpenZeppelin templates.
+- [UI Builder](https://builder.openzeppelin.com): Open source tool for creating UI forms for contracts.
+- [MCP Server](https://mcp.openzeppelin.com): Generate secure Stellar smart contracts based on OpenZeppelin templates.
 - [Role Manager](https://github.com/OpenZeppelin/role-manager): Access control management interface for smart contracts. Visualize roles, permissions, and execute administrative actions.
 - [Soroban Security Detector SDK](https://github.com/OpenZeppelin/soroban-security-detectors-sdk): Spot issues in contracts before they reach mainnet. This SDK enables developers to build custom static-analysis scanners and comes with prebuilt checks to catch common pitfalls early.
diff --git a/docs/tools/quickstart/advanced-usage/container.mdx b/docs/tools/quickstart/advanced-usage/container.mdx
index f4547b8d99..db440c94ee 100644
--- a/docs/tools/quickstart/advanced-usage/container.mdx
+++ b/docs/tools/quickstart/advanced-usage/container.mdx
@@ -16,6 +16,6 @@ The Quickstart [docker image](https://hub.docker.com/r/stellar/quickstart) uses
 - [horizon](https://github.com/stellar/stellar-horizon)
 - [friendbot](https://github.com/stellar/friendbot)
 - [stellar-rpc](https://github.com/stellar/stellar-rpc/tree/main/cmd/stellar-rpc)
-- [supervisord](http://supervisord.org/)
+- [supervisord](http://supervisord.org)
 
 The Stellar CLI has commands for starting and stopping a Quickstart container, and also a command to get logs from a running container. See Stellar CLI [documentation](../../cli/stellar-cli.mdx#stellar-container) for more information.
diff --git a/docs/tools/quickstart/getting-started/README.mdx b/docs/tools/quickstart/getting-started/README.mdx
index ed2376516c..9f27cc97bf 100644
--- a/docs/tools/quickstart/getting-started/README.mdx
+++ b/docs/tools/quickstart/getting-started/README.mdx
@@ -14,7 +14,7 @@ In this guide, you will set up Quickstart using the Stellar CLI. Quickstart will
 Before following the steps in this guide, the following must be installed and setup on your local system:
 
 - [Stellar CLI](../../../build/smart-contracts/getting-started/setup.mdx#install-the-stellar-cli)
-- [Docker](https://docs.docker.com/get-started/get-docker/)
+- [Docker](https://docs.docker.com/get-started/get-docker)
 
 ## Start Quickstart
 
diff --git a/docs/tools/ramps/README.mdx b/docs/tools/ramps/README.mdx
index dbf590aabc..c43c52ebb5 100644
--- a/docs/tools/ramps/README.mdx
+++ b/docs/tools/ramps/README.mdx
@@ -7,7 +7,7 @@ import DocCardList from "@theme/DocCardList";
 
 On and off-ramps (called [anchors](../../learn/fundamentals/anchors.mdx) in the Stellar universe) that connect the Stellar network to traditional financial rails.
 
-Stellar has anchor services operating worldwide. View the [Anchor Directory](https://anchors.stellar.org/) for information on Stellar anchors.
+Stellar has anchor services operating worldwide. View the [Anchor Directory](https://anchors.stellar.org) for information on Stellar anchors.
 
 Anchors can issue their own assets on the Stellar network, or they can honor assets that already exist.
 
diff --git a/docs/tools/scaffold-stellar.mdx b/docs/tools/scaffold-stellar.mdx
index e896e32258..468549eb37 100644
--- a/docs/tools/scaffold-stellar.mdx
+++ b/docs/tools/scaffold-stellar.mdx
@@ -18,9 +18,9 @@ Before you begin, make sure you have the following installed:
 | Tool | Description | Install Link |
 | --- | --- | --- |
 | [Rust & Cargo](https://www.rust-lang.org/tools/install) | For writing and compiling smart contracts | `curl https://sh.rustup.rs -sSf \| sh` |
-| [Node.js & npm](https://nodejs.org/) | For frontend development | Download from official site |
+| [Node.js & npm](https://nodejs.org) | For frontend development | Download from official site |
 | [Stellar CLI](https://github.com/stellar/stellar-cli) | For building, deploying, and interacting with smart contracts | [`Link for the repo`](https://github.com/stellar/stellar-cli) |
-| [Docker](https://www.docker.com/get-started/) | For running a local Stellar network via the `stellar/quickstart` image | [Download Docker Desktop](https://www.docker.com/products/docker-desktop/) |
+| [Docker](https://www.docker.com/get-started) | For running a local Stellar network via the `stellar/quickstart` image | [Download Docker Desktop](https://www.docker.com/products/docker-desktop) |
 
 ## Getting Started
 
diff --git a/docs/tools/sdks/client-sdks.mdx b/docs/tools/sdks/client-sdks.mdx
index 0079226147..e7445a1382 100644
--- a/docs/tools/sdks/client-sdks.mdx
+++ b/docs/tools/sdks/client-sdks.mdx
@@ -21,7 +21,7 @@ Each SDK has its own source code and documentation. Learn how to use a specific
 
 ## JavaScript SDK
 
-[JavaScript SDK](https://github.com/stellar/js-stellar-sdk) | [Docs](https://stellar.github.io/js-stellar-sdk/) | [NPM](https://www.npmjs.com/package/@stellar/stellar-sdk)
+[JavaScript SDK](https://github.com/stellar/js-stellar-sdk) | [Docs](https://stellar.github.io/js-stellar-sdk) | [NPM](https://www.npmjs.com/package/@stellar/stellar-sdk)
 
 **The JavaScript SDK is maintained by SDF.**
 
@@ -34,7 +34,7 @@ It provides:
 
 ## Python SDK
 
-[Python SDK](https://github.com/StellarCN/py-stellar-base) | [Docs](https://stellar-sdk.readthedocs.io/en/latest/) | [Examples](https://github.com/StellarCN/py-stellar-base/tree/master/examples)
+[Python SDK](https://github.com/StellarCN/py-stellar-base) | [Docs](https://stellar-sdk.readthedocs.io/en/latest) | [Examples](https://github.com/StellarCN/py-stellar-base/tree/master/examples)
 
 **The Python SDK is maintained by dedicated community developers.**
 
@@ -63,7 +63,7 @@ Functionality for interacting with Stellar data can be found in the following Ru
 [XDR-JSON]: ../../learn/fundamentals/data-format/xdr-json.mdx
 [SEP-23]: https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0023.md
 
-- `soroban-client` - [Code](https://github.com/rahul-soshte/rs-soroban-client) | [Docs](https://docs.rs/soroban-client/latest/soroban_client/)
+- `soroban-client` - [Code](https://github.com/rahul-soshte/rs-soroban-client) | [Docs](https://docs.rs/soroban-client/latest/soroban_client)
 
   A Rust library for interacting with the Soroban smart contract environment. It provides APIs to build and submit transactions, communicate with Stellar RPC servers, and supports all classic Stellar operations. **Maintained by a dedicated community developer.**
 
@@ -103,7 +103,7 @@ The PHP Stellar SDK is maintained by dedicated community developer, Soneso.
 
 ## Java SDK
 
-[Java SDK](https://github.com/lightsail-network/java-stellar-sdk) | [Docs](https://lightsail-network.github.io/java-stellar-sdk/)
+[Java SDK](https://github.com/lightsail-network/java-stellar-sdk) | [Docs](https://lightsail-network.github.io/java-stellar-sdk)
 
 **Maintained by a dedicated community developer.**
 
@@ -122,6 +122,6 @@ This SDK is split up into separate packages, all of which you can find in the [G
 
 ## C# .NET
 
-[C# .NET SDK](https://github.com/Beans-BV/dotnet-stellar-sdk) | [Docs](https://elucidsoft.github.io/dotnet-stellar-sdk/)
+[C# .NET SDK](https://github.com/Beans-BV/dotnet-stellar-sdk) | [Docs](https://elucidsoft.github.io/dotnet-stellar-sdk)
 
 **This SDK is maintained by dedicated community developers.**
diff --git a/docs/tools/sdks/contract-sdks.mdx b/docs/tools/sdks/contract-sdks.mdx
index 5400b827ba..1e5f610a55 100644
--- a/docs/tools/sdks/contract-sdks.mdx
+++ b/docs/tools/sdks/contract-sdks.mdx
@@ -42,7 +42,7 @@ soroban-sdk = { version = $VERSION, features = ["testutils"] }
 
 ## Solidity SDK
 
-[Hyperledger Solang compiler](https://github.com/hyperledger-solang/solang) | [Docs](https://solang.readthedocs.io/en/v0.3.4/)
+[Hyperledger Solang compiler](https://github.com/hyperledger-solang/solang) | [Docs](https://solang.readthedocs.io/en/v0.3.4)
 
 **The Solang compiler is maintained by the Hyperledger community.**
 
@@ -52,7 +52,7 @@ The supported Solidity examples can be found within the [Solang repository](http
 
 You can report issues and add requests for features to the Solang repository [here](https://github.com/hyperledger-solang/solang/issues/new/choose).
 
-Solang compiler also provides a Web IDE that you can use to compile, deploy and interact with Solidity contracts on Soroban. You can access the Web IDE [here](https://solang.io/).
+Solang compiler also provides a Web IDE that you can use to compile, deploy and interact with Solidity contracts on Soroban. You can access the Web IDE [here](https://solang.io).
 
 ## AssemblyScript SDK
 
diff --git a/docs/validators/admin-guide/monitoring.mdx b/docs/validators/admin-guide/monitoring.mdx
index 1855ee5674..fec1f48405 100644
--- a/docs/validators/admin-guide/monitoring.mdx
+++ b/docs/validators/admin-guide/monitoring.mdx
@@ -181,7 +181,7 @@ During the reporting phase, the surveyor sends `TimeSlicedSurveyRequestMessage`s
 
 ### Overlay Survey Script
 
-To simplify running an overlay survey, stellar-core ships with a script [`OverlaySurvey.py`](https://github.com/stellar/stellar-core/blob/master/scripts/OverlaySurvey.py) in the [`scripts` directory](https://github.com/stellar/stellar-core/tree/master/scripts). This script walks the network using the overlay survey HTTP endpoints to build a graph containing the topology of the overlay network. The script outputs this graph both in JSON format, as well as GraphML. You can analyze the GraphML file using a GraphML viewer such as [Gephi](https://gephi.org/).
+To simplify running an overlay survey, stellar-core ships with a script [`OverlaySurvey.py`](https://github.com/stellar/stellar-core/blob/master/scripts/OverlaySurvey.py) in the [`scripts` directory](https://github.com/stellar/stellar-core/tree/master/scripts). This script walks the network using the overlay survey HTTP endpoints to build a graph containing the topology of the overlay network. The script outputs this graph both in JSON format, as well as GraphML. You can analyze the GraphML file using a GraphML viewer such as [Gephi](https://gephi.org).
 
 An example usage of the survey script to run an overlay survey is as follows:
 
@@ -612,7 +612,7 @@ Rules are documented in-line,and we strongly recommend that you review and verif
 
 ### Configure Notifications Using Alertmanager
 
-Alertmanager is responsible for sending notifications. Installing and configuring an Alertmanager server is out of scope of this document, however it is a fairly simple process. Official documentation is [here](https://github.com/prometheus/alertmanager/).
+Alertmanager is responsible for sending notifications. Installing and configuring an Alertmanager server is out of scope of this document, however it is a fairly simple process. Official documentation is [here](https://github.com/prometheus/alertmanager).
 
 All recommended alerting rules have "severity" label:
 
@@ -656,7 +656,7 @@ In the above examples alerts with severity "critical" are sent to pagerduty and
 
 You may find the below exporters useful for monitoring your infrastructure as they provide incredible insight into your operating system and database metrics. Installing and configuring these exporters is out of the scope of this document but should be relatively straightforward.
 
-- [node_exporter](https://prometheus.io/docs/guides/node-exporter/) can be used to track all operating system metrics.
+- [node_exporter](https://prometheus.io/docs/guides/node-exporter) can be used to track all operating system metrics.
 - [postgresql_exporter](https://github.com/wrouesnel/postgres_exporter) can be used to monitor the local stellar-core database.
 
 ### Visualize Metrics Using Grafana
diff --git a/docs/validators/admin-guide/prerequisites.mdx b/docs/validators/admin-guide/prerequisites.mdx
index f49918ea85..b4ade4da21 100644
--- a/docs/validators/admin-guide/prerequisites.mdx
+++ b/docs/validators/admin-guide/prerequisites.mdx
@@ -13,7 +13,7 @@ CPU, RAM, Disk and network depends on network activity. If you decide to colloca
 
 :::
 
-At the time of writing (April 2024), Stellar Core with PostgreSQL running on the same machine worked well on a [c5d.2xlarge](https://aws.amazon.com/ec2/instance-types/c5/) instance in AWS (8x Intel Xeon vCPUs at 3.4 GHz; 16 GB RAM; 100 GB NVMe SSD (10,000 iops)).
+At the time of writing (April 2024), Stellar Core with PostgreSQL running on the same machine worked well on a [c5d.2xlarge](https://aws.amazon.com/ec2/instance-types/c5) instance in AWS (8x Intel Xeon vCPUs at 3.4 GHz; 16 GB RAM; 100 GB NVMe SSD (10,000 iops)).
 
 Stellar Core is designed to run on relatively modest hardware so that a whole range of individuals and organizations can participate in the network, and basic nodes should be able to function pretty well without tremendous overhead. That said, the more you ask of your node, the greater the requirements.
 
@@ -33,7 +33,7 @@ A Stellar Core node needs to allow all IPs to connect to its `PEER_PORT` over TC
 
 ### Outbound
 
-A Stellar Core node needs to connect to other nodes on the internet via their `PEER_PORT` over TCP. You can find information about other nodes' `PEER_PORT`s on a network explorer like [Stellarbeat](https://stellarbeat.io/), but most use the default port for this as well, which is (again) **11625**.
+A Stellar Core node needs to connect to other nodes on the internet via their `PEER_PORT` over TCP. You can find information about other nodes' `PEER_PORT`s on a network explorer like [Stellarbeat](https://stellarbeat.io), but most use the default port for this as well, which is (again) **11625**.
 
 ## Internal System Access
 
diff --git a/static/llms.txt b/static/llms.txt
index 7add0a196d..4611d1da5e 100644
--- a/static/llms.txt
+++ b/static/llms.txt
@@ -129,8 +129,8 @@ SDF Platforms
 
 [English](https://developers.stellar.org/#)
 
-- [English](https://developers.stellar.org/)
-- [Español](https://developers.stellar.org/es/)
+- [English](https://developers.stellar.org)
+- [Español](https://developers.stellar.org/es)
 
 [GitHub](https://github.com/stellar/stellar-docs)
 
@@ -249,7 +249,7 @@ Get the latest news and insights about building on Stellar.
 
 A question and answer site for Stellar developers; if you can’t find what you’re looking for in the docs, try searching the Stack Exchange to see if your question has been addressed. If it hasn't, feel free to ask!
 
-[Explore](https://stellar.stackexchange.com/)
+[Explore](https://stellar.stackexchange.com)
 
 ### Stellar Developers Google Group
 
@@ -261,17 +261,17 @@ Discuss Core Advancement Proposals (CAPs) and Stellar Ecosystem Proposals (SEPs)
 Resources
 
 - [Developer Blog](https://www.stellar.org/developers-blog)
-- [Stellar Quest](https://quest.stellar.org/)
+- [Stellar Quest](https://quest.stellar.org)
 - [Soroban Quest](https://fastcheapandoutofcontrol.com/tutorial)
 - [YouTube](https://www.youtube.com/@StellarDevelopmentFoundation)
 - [Twitch](https://m.twitch.tv/stellarorg/home)
 
 Tools
 
-- [Explorer](https://stellar.expert/)
-- [Lab](https://lab.stellar.org/)
-- [Status](https://status.stellar.org/)
-- [Dashboard](https://dashboard.stellar.org/)
+- [Explorer](https://stellar.expert)
+- [Lab](https://lab.stellar.org)
+- [Status](https://status.stellar.org)
+- [Dashboard](https://dashboard.stellar.org)
 - [All Tools](https://developers.stellar.org/docs/tools)
 
 Community
@@ -280,8 +280,8 @@ Community
 - [Developer Discord](https://discord.gg/stellardev)
 - [Developer Meetings](https://developers.stellar.org/meetings)
 - [Developer Google Group](https://groups.google.com/g/stellar-dev)
-- [Stack Exchange](https://stellar.stackexchange.com/)
-- [Stellar Community Fund](https://communityfund.stellar.org/)
+- [Stack Exchange](https://stellar.stackexchange.com)
+- [Stellar Community Fund](https://communityfund.stellar.org)
 
 About
 

From a869e84024944e5a87dc56bddf99337373f4a6ff Mon Sep 17 00:00:00 2001
From: "john.xlm" <60260750+JFWooten4@users.noreply.github.com>
Date: Sun, 26 Apr 2026 19:07:57 -0400
Subject: [PATCH 2/2] conform API src specs etc

---
 CROWDIN.md                                              | 6 +++---
 docs/platforms/stellar-disbursement-platform/README.mdx | 2 +-
 meeting-notes/2024-02-29.mdx                            | 2 +-
 meeting-notes/2024-04-18.mdx                            | 2 +-
 meeting-notes/2024-05-09.mdx                            | 2 +-
 meeting-notes/2024-08-01.mdx                            | 4 ++--
 openapi/stellar-disbursement-platform/bundled.yaml      | 2 +-
 openapi/stellar-disbursement-platform/main.yaml         | 2 +-
 8 files changed, 11 insertions(+), 11 deletions(-)

diff --git a/CROWDIN.md b/CROWDIN.md
index d04679d467..10c1814d96 100644
--- a/CROWDIN.md
+++ b/CROWDIN.md
@@ -1,6 +1,6 @@
 # Crowdin Translator How-To
 
-Stellar Developer Docs use [Crowdin](https://crowdin.com/) for localization. This document provides steps and resources for managing Stellar Docusaurus Crowdin translations as a Crowdin user with a Translator role.
+Stellar Developer Docs use [Crowdin](https://crowdin.com) for localization. This document provides steps and resources for managing Stellar Docusaurus Crowdin translations as a Crowdin user with a Translator role.
 
 ---
 
@@ -33,7 +33,7 @@ For more details on working within the editor, see the following documentation:
 [Working in the Editor](https://support.crowdin.com/for-translators/#working-in-the-editor) 
 
 For a more in-depth look, see: 
-[Online Editor Guide](https://support.crowdin.com/online-editor/)
+[Online Editor Guide](https://support.crowdin.com/online-editor)
 
 ---
 
@@ -46,7 +46,7 @@ Examples include:
 - Words or phrases that should not be translated at all. 
 
 For more information, see the following documentation: 
-[Glossary](https://support.crowdin.com/glossary/)
+[Glossary](https://support.crowdin.com/glossary)
 
 ---
 
diff --git a/docs/platforms/stellar-disbursement-platform/README.mdx b/docs/platforms/stellar-disbursement-platform/README.mdx
index 6269a748de..674e31881d 100644
--- a/docs/platforms/stellar-disbursement-platform/README.mdx
+++ b/docs/platforms/stellar-disbursement-platform/README.mdx
@@ -16,4 +16,4 @@ This is an open-source project that is built on top of the Stellar network, and
 - [stellar/stellar-disbursement-platform-frontend](https://github.com/stellar/stellar-disbursement-platform-frontend): This repository contains the web frontend code for the Stellar Disbursement Platform.
 - [stellar/helm-charts](https://github.com/stellar/helm-charts/tree/main/charts/stellar-disbursement-platform): This repository contains the Helm chart for deploying the Stellar Disbursement Platform using kubernetes.
 
-In this section, you'll find an [Admin Guide](./stellar-disbursement-platform/admin-guide/) that will teach you how to run the Stellar Disbursement Platform as well as an [API Reference](./api-reference/admin.tag.mdx).
+In this section, you'll find an [Admin Guide](./stellar-disbursement-platform/admin-guide) that will teach you how to run the Stellar Disbursement Platform as well as an [API Reference](./api-reference/admin.tag.mdx).
diff --git a/meeting-notes/2024-02-29.mdx b/meeting-notes/2024-02-29.mdx
index be09cdc8a0..e378db3d2d 100644
--- a/meeting-notes/2024-02-29.mdx
+++ b/meeting-notes/2024-02-29.mdx
@@ -15,5 +15,5 @@ tags: [protocol]
 
 1. Tommaso (@tdep) proposed a core change to allow for extending instance and code TTL with separate values on the host environment to allow for more cost-efficient designs a. Proposal and discussion are captured in github discussions [stellar-core#1447](https://github.com/stellar/stellar-protocol/discussions/1447)
 2. Tommaso received feedback on the proposal as well as implementation. Since it didn't require a metering change, core devs thought it to be a quick change.
-3. The ecosystem voted in favor of the proposal by upvoting the post on Github Discussions. 13 votes were [recorded](https://github.com/stellar/stellar-protocol/discussions/).
+3. The ecosystem voted in favor of the proposal by upvoting the post on Github Discussions. 13 votes were [recorded](https://github.com/stellar/stellar-protocol/discussions).
 4. As next steps, a CAP will be authored to capture the proposal and put forth for approval from CAP Core Team.
diff --git a/meeting-notes/2024-04-18.mdx b/meeting-notes/2024-04-18.mdx
index 83f671c5dc..29a755acf3 100644
--- a/meeting-notes/2024-04-18.mdx
+++ b/meeting-notes/2024-04-18.mdx
@@ -13,7 +13,7 @@ tags: [developer]
 
 [Discord agenda thread](https://discord.com/channels/897514728459468821/911254664576643122/1215404506964172890)
 
-1. Justin from [ortege.ai](https://www.ortege.ai/) demo'd Ortege, a data analytics platform for Stellar and Soroban.
+1. Justin from [ortege.ai](https://www.ortege.ai) demo'd Ortege, a data analytics platform for Stellar and Soroban.
 2. Ortege lets anyone in the Stellar ecosystem create dashboards to track any and all desired metrics. Ortege's queries, widgets, and dashboards are shareable making it the perfect platform to surface
 3. Justin will be releasing an AI soon and enable querying and insights via natural language.
 4. All are invited to create a free account and track the success metrics for their dashboard.
diff --git a/meeting-notes/2024-05-09.mdx b/meeting-notes/2024-05-09.mdx
index 12556769d8..4e08504b53 100644
--- a/meeting-notes/2024-05-09.mdx
+++ b/meeting-notes/2024-05-09.mdx
@@ -14,5 +14,5 @@ tags: [developer]
 1. Tyler built a voting application using passkeys to sign the transaction, which is an implementation of the secp256r1 verification function.
 2. He showed a cross-platform implementation (web and mobile) and demonstrated that passkeys are the perfect interface between web3 contracts and web2 authentication mechanisms that most end users are accostomed to.
 3. Ecosystem members discussed the use of smart wallets that would use passkeys as a signer. Challenges were identified around fees requires for smart wallets, the need for a common implementation for a smart wallet, as well as how might it interface with existing password managers.
-4. The voting application can be tried out at [passkey.sorobanbyexample.org/](https://passkey.sorobanbyexample.org/)
+4. The voting application can be tried out at [passkey.sorobanbyexample.org](https://passkey.sorobanbyexample.org)
 5. Code for the demo is here [github.com/kalepail/soroban-passkey](https://github.com/kalepail/soroban-passkey)
diff --git a/meeting-notes/2024-08-01.mdx b/meeting-notes/2024-08-01.mdx
index 0c2f914ca0..902768e626 100644
--- a/meeting-notes/2024-08-01.mdx
+++ b/meeting-notes/2024-08-01.mdx
@@ -11,7 +11,7 @@ tags: [developer]
   allow="autoplay"
 ></iframe>
 
-1. Piyal demonstrated that Freighter's swap functionality is now served by [Soroswap](https://soroswap.finance/). It was previously served by Stellar Dex.
+1. Piyal demonstrated that Freighter's swap functionality is now served by [Soroswap](https://soroswap.finance). It was previously served by Stellar Dex.
 2. Freighter has made integration instructions available [here](https://github.com/stellar/freighter/blob/d248f2ad0aa03da72ea6eeaf7907ac0454fdcc72/extension/INTEGRATING_SOROSWAP.MD?plain=1#L2).
-3. Esteban shared that [Palta Labs](https://paltalabs.io/) has created a DEX aggregator and made it available to all via the [Router SDK](https://docs.soroswap.finance/03-technical-reference/07-optimal-route/01-soroswap-router-sdk).
+3. Esteban shared that [Palta Labs](https://paltalabs.io) has created a DEX aggregator and made it available to all via the [Router SDK](https://docs.soroswap.finance/03-technical-reference/07-optimal-route/01-soroswap-router-sdk).
 4. The Router SDK finds the optimal path for the swap in terms of swap cost across all dexes on Soroban.
diff --git a/openapi/stellar-disbursement-platform/bundled.yaml b/openapi/stellar-disbursement-platform/bundled.yaml
index 6c1705c040..6c65ae11b2 100644
--- a/openapi/stellar-disbursement-platform/bundled.yaml
+++ b/openapi/stellar-disbursement-platform/bundled.yaml
@@ -5067,7 +5067,7 @@ components:
           example: '100.00'
         stellar_transaction_id:
           type: string
-          description: The ID of the transaction in the Stellar network. It can be used tio track the payment in the Stellar network using [Stellar Laboratory](https://laboratory.stellar.org/), or [StellarExpert](https://stellar.expert/).
+          description: The ID of the transaction in the Stellar network. It can be used tio track the payment in the Stellar network using [Stellar Laboratory](https://laboratory.stellar.org), or [StellarExpert](https://stellar.expert).
           example: 0b339d1c89d314186b8147c2af4c9a9ed5bbdbcd7ada8d138633907649b
         circle_transfer_request_id:
           type: string
diff --git a/openapi/stellar-disbursement-platform/main.yaml b/openapi/stellar-disbursement-platform/main.yaml
index 535647fa42..6b5b1ba08b 100644
--- a/openapi/stellar-disbursement-platform/main.yaml
+++ b/openapi/stellar-disbursement-platform/main.yaml
@@ -5098,7 +5098,7 @@ components:
           example: "100.00"
         stellar_transaction_id:
           type: string
-          description: "The ID of the transaction in the Stellar network. It can be used tio track the payment in the Stellar network using [Stellar Laboratory](https://laboratory.stellar.org/), or [StellarExpert](https://stellar.expert/)."
+          description: "The ID of the transaction in the Stellar network. It can be used tio track the payment in the Stellar network using [Stellar Laboratory](https://laboratory.stellar.org), or [StellarExpert](https://stellar.expert)."
           example: 0b339d1c89d314186b8147c2af4c9a9ed5bbdbcd7ada8d138633907649b
         circle_transfer_request_id:
           type: string