stellar · JFWooten4 · Aug 18, 2026 · Aug 18, 2026 · Aug 18, 2026 · Aug 18, 2026
diff --git a/docs/data/analytics/hubble/analyst-guide/creating-visualizations.mdx b/docs/data/analytics/hubble/analyst-guide/creating-visualizations.mdx
@@ -13,7 +13,7 @@ As you can see, persistent contract data entries account for roughly 25% of all
 
 ## Prerequisites
 
-1. Make sure you have connected to Hubble by following the instructions in the [Connecting](../developer-guide/connecting-to-bigquery/README.mdx) page
+1. Make sure you have connected to Hubble by following the instructions in the [Connecting](../developer-guide/connecting-to-bigquery.mdx) page
 2. You have access to [Google Looker Studio](https://cloud.google.com/looker-studio?hl=en)
 3. You have read and understand the general [Best Practices](./optimizing-queries.mdx#best-practices) for querying BigQuery data
 

diff --git a/docs/data/analytics/hubble/analyst-guide/queries-for-horizon-like-data.mdx b/docs/data/analytics/hubble/analyst-guide/queries-for-horizon-like-data.mdx
@@ -497,7 +497,7 @@ where true
 
 ## Liquidity Pools
 
-[horizon/liquidity_pools](../../../apis/horizon/api-reference/resources/liquiditypools/README.mdx)
+[horizon/liquidity_pools](../../../apis/horizon/api-reference/resources/liquiditypools.mdx)
 
 Liquidity Pools provide a simple, non-interactive way to trade large amounts of capital and enable high volumes of trading.
 

diff --git a/docs/data/analytics/hubble/developer-guide/backfill/JS-UDF.mdx b/docs/data/analytics/hubble/developer-guide/backfill/JS-UDF.mdx
@@ -11,7 +11,7 @@ Use Cases:
 - Backfix for a new column added
 - Temporary extraction of fields not parsed by stellar-etl
 
-We'll take the example of extracting the `fee_account_muxed` field from a transaction envelope (`tx_meta` XDR). However, this method can be adapted to other fields as well. It is worth noting that most users will not need to standup and run their own Hubble. The Stellar Development Foundation provides public access to the data through the public datasets and tables in GCP BigQuery. Instructions on how to access this data can be found in the [Connecting](../../developer-guide/connecting-to-bigquery/README.mdx) section.
+We'll take the example of extracting the `fee_account_muxed` field from a transaction envelope (`tx_meta` XDR). However, this method can be adapted to other fields as well. It is worth noting that most users will not need to standup and run their own Hubble. The Stellar Development Foundation provides public access to the data through the public datasets and tables in GCP BigQuery. Instructions on how to access this data can be found in the [Connecting](../connecting-to-bigquery.mdx) section.
 
 We will use the [js-stellar-base](https://github.com/stellar/js-stellar-base) library to parse the XDR and employ JavaScript UDFs (User Defined Functions) in BigQuery to apply the transformation to the dataset.
 

diff --git a/docs/data/analytics/hubble/developer-guide/backfill/data-import.mdx b/docs/data/analytics/hubble/developer-guide/backfill/data-import.mdx
@@ -31,7 +31,7 @@ LOAD DATA INTO mydataset.transactions
 
 ## 2. Use BigQuery API / Console to Mirror SDF's Dataset
 
-The Stellar Development Foundation provides public access to fully transformed Stellar network data through the public datasets and tables in GCP BigQuery. Instructions on how to access this data can be found in the [Connecting](../../developer-guide/connecting-to-bigquery/README.mdx) section.
+The Stellar Development Foundation provides public access to fully transformed Stellar network data through the public datasets and tables in GCP BigQuery. Instructions on how to access this data can be found in the [Connecting](../connecting-to-bigquery.mdx) section.
 
 Use the [Create Table Copy statement](https://cloud.google.com/bigquery/docs/reference/standard-sql/data-definition-language#create_table_copy) to copy data across datasets.
 

diff --git a/...r-guide/connecting-to-bigquery/README.mdx → ...eveloper-guide/connecting-to-bigquery.mdx b/...r-guide/connecting-to-bigquery/README.mdx → ...eveloper-guide/connecting-to-bigquery.mdx
diff --git a/docs/data/analytics/hubble/developer-guide/data-curation/overview.mdx b/docs/data/analytics/hubble/developer-guide/data-curation/overview.mdx
@@ -5,7 +5,7 @@ sidebar_position: 0
 
 Data curation in Hubble is done through [stellar-dbt-public](https://github.com/stellar/stellar-dbt-public). stellar-dbt-public transforms raw Stellar network data from BigQuery datasets and tables into aggregates for more user friendly analytics.
 
-It is worth noting that most users will not need to standup and run their own stellar-dbt-public instance. The Stellar Development Foundation provides public access to fully transformed Stellar network data through the public datasets and tables in GCP BigQuery. Instructions on how to access this data can be found in the [Connecting](../../developer-guide/connecting-to-bigquery/README.mdx) section.
+It is worth noting that most users will not need to standup and run their own stellar-dbt-public instance. The Stellar Development Foundation provides public access to fully transformed Stellar network data through the public datasets and tables in GCP BigQuery. Instructions on how to access this data can be found in the [Connecting](../connecting-to-bigquery.mdx) section.
 
 ## Why Run stellar-dbt-public?
 

diff --git a/...data/analytics/hubble/developer-guide/scheduling-and-orchestration/overview.mdx b/...data/analytics/hubble/developer-guide/scheduling-and-orchestration/overview.mdx
@@ -5,7 +5,7 @@ sidebar_position: 0
 
 Hubble uses [stellar-etl-airflow](https://github.com/stellar/stellar-etl-airflow) to schedule and orchestrate all its workflows. This includes the scheduling and running of stellar-etl and stellar-dbt.
 
-It is worth noting that most users will not need to standup and run their own Hubble. The Stellar Development Foundation provides public access to the data through the public datasets and tables in GCP BigQuery. Instructions on how to access this data can be found in the [Connecting](../../developer-guide/connecting-to-bigquery/README.mdx) section.
+It is worth noting that most users will not need to standup and run their own Hubble. The Stellar Development Foundation provides public access to the data through the public datasets and tables in GCP BigQuery. Instructions on how to access this data can be found in the [Connecting](../connecting-to-bigquery.mdx) section.
 
 ## Why Run stellar-etl-ariflow?
 

diff --git a/docs/data/analytics/hubble/developer-guide/source-system-ingestion/overview.mdx b/docs/data/analytics/hubble/developer-guide/source-system-ingestion/overview.mdx
@@ -7,6 +7,6 @@ Stellar network data ingestion in Hubble is done through [stellar-etl](https://g
 
 | Use Case | Recommended Solution | Reason |
 | --- | --- | --- |
-| Need commonly required data fields and do not want to take burden of setting up entire pipeline | Use output from SDF's stellar-etl instance i.e. [Connect to Bigquery and access hubble](../../developer-guide/connecting-to-bigquery/README.mdx) | It is worth noting that most users will not need to standup and run their own stellar-etl instance. The Stellar Development Foundation provides public access to fully transformed Stellar network data through the public datasets and tables in GCP BigQuery. |
+| Need commonly required data fields and do not want to take burden of setting up entire pipeline | Use output from SDF's stellar-etl instance i.e. [Connect to Bigquery and access hubble](../connecting-to-bigquery.mdx) | It is worth noting that most users will not need to standup and run their own stellar-etl instance. The Stellar Development Foundation provides public access to fully transformed Stellar network data through the public datasets and tables in GCP BigQuery. |
 | Need custom data but do not want to take burden of setting up entire pipeline | Use [JS-UDF](../../developer-guide/backfill/JS-UDF.mdx) | Stellar-ETL does not parse every single field available in raw XDR, but it does save the raw transaction meta. JS-UDF helps to extract a field directly from XDR |
 | Need custom and operationally independent data | Run [stellar-etl](https://github.com/stellar/stellar-etl/tree/master) | Running stellar-etl within your own infrastructure provides a number of benefits. You can: <br></br> - Have full operational control without dependency on the Stellar Development Foundation for network data <br></br> - Run modified ETL/ELT pipelines that fit your individual business needs |
diff --git a/docs/data/apis/horizon/api-reference/resources/README.mdx b/docs/data/apis/horizon/api-reference/resources/README.mdx
@@ -20,6 +20,6 @@ Data on the Stellar ledger is organized according to resources. Each resource ha
 | [Claimable Balances](./claimablebalances/README.mdx) |     |
 | [Trades](./trades/README.mdx)                        |     |
 | [Assets](./assets/README.mdx)                        |     |
-| [Liquidity Pools](./liquiditypools/README.mdx)       |     |
+| [Liquidity Pools](./liquiditypools.mdx)              |     |
 
 </MethodTable>
diff --git a/docs/data/apis/horizon/api-reference/resources/liquiditypools.mdx b/docs/data/apis/horizon/api-reference/resources/liquiditypools.mdx
@@ -0,0 +1,21 @@
+---
+title: Liquidity Pools
+order: 0
+---
+
+Liquidity Pools provide a simple, non-interactive way to trade large amounts of capital and enable high volumes of trading.
+
+The [latest ledger](../structure/consistency.mdx) known to Horizon is included as an HTTP header in the response.
+
+<EndpointsTable title="Endpoints">
+
+|  |  |
+| --- | --- |
+| GET | [/liquidity_pools](../list-liquidity-pools.api.mdx) |
+| GET | [/liquidity_pools/:liquidity_pool_id](../retrieve-a-liquidity-pool.api.mdx) |
+| GET | [/liquidity_pools/:liquidity_pool_id/effects](../retrieve-related-effects.api.mdx) |
+| GET | [/liquidity_pools/:liquidity_pool_id/trades](../retrieve-related-trades.api.mdx) |
+| GET | [/liquidity_pools/:liquidity_pool_id/transactions](../lp-retrieve-related-transactions.api.mdx) |
+| GET | [/liquidity_pools/:liquidity_pool_id/operations](../lp-retrieve-related-operations.api.mdx) |
+
+</EndpointsTable>
diff --git a/docs/data/apis/horizon/api-reference/resources/liquiditypools/README.mdx b/docs/data/apis/horizon/api-reference/resources/liquiditypools/README.mdx
diff --git a/docs/platforms/anchor-platform/README.mdx b/docs/platforms/anchor-platform/README.mdx
@@ -14,14 +14,14 @@ The Anchor Platform provides a set of tools and APIs for building on and off-ram
 
 The Anchor Platform implements the following Stellar Ecosystem Proposals:
 
-- **[SEP-1](sep-guide/sep1/README.mdx)** — Stellar.toml file serving for service discovery
+- **[SEP-1](sep-guide/sep1.mdx)** — Stellar.toml file serving for service discovery
 - **[SEP-6](sep-guide/sep6/README.mdx)** — Deposit and withdrawal operations
-- **[SEP-10](sep-guide/sep10/README.mdx)** — Web authentication using challenge/response transactions
+- **[SEP-10](sep-guide/sep10.mdx)** — Web authentication using challenge/response transactions
 - **SEP-12** — Customer KYC/AML data management
 - **[SEP-24](sep-guide/sep24/README.mdx)** — Interactive deposit and withdrawal flows
 - **[SEP-31](sep-guide/sep31/integration.mdx)** — Cross-border payment processing (receive only)
 - **SEP-38** — Price quotes and exchange rate services
-- **[SEP-45](sep-guide/sep45/README.mdx)** — Web authentication using challenge/responses for contract accounts
+- **[SEP-45](sep-guide/sep45.mdx)** — Web authentication using challenge/responses for contract accounts
 
 ## Key Features
 

diff --git a/docs/platforms/anchor-platform/admin-guide/events/integration.mdx b/docs/platforms/anchor-platform/admin-guide/events/integration.mdx
@@ -158,4 +158,4 @@ This configures the event service's callback API that will be used to send event
     - `http_header`: The header in which the API key will be sent.
 
 [default-values-file]: https://github.com/stellar/java-stellar-anchor-sdk/blob/develop/platform/src/main/resources/config/anchor-config-default-values.yaml
-[clients-config]: ../../sep-guide/sep10/README.mdx#config-with-client-attribution
+[clients-config]: ../../sep-guide/sep10.mdx#config-with-client-attribution
diff --git a/...anchor-platform/sep-guide/sep1/README.mdx → ...tforms/anchor-platform/sep-guide/sep1.mdx b/...anchor-platform/sep-guide/sep1/README.mdx → ...tforms/anchor-platform/sep-guide/sep1.mdx
diff --git a/...nchor-platform/sep-guide/sep10/README.mdx → ...forms/anchor-platform/sep-guide/sep10.mdx b/...nchor-platform/sep-guide/sep10/README.mdx → ...forms/anchor-platform/sep-guide/sep10.mdx
@@ -256,7 +256,7 @@ The JWT token should be included in subsequent API requests as a Bearer token in
 
 :::tip
 
-**Testing Your Configuration**: You can test SEP-10 authentication using curl and Stellar CLI. For more information about Stellar CLI, see the [Stellar CLI documentation](../../../../tools/cli/README.mdx).
+**Testing Your Configuration**: You can test SEP-10 authentication using curl and Stellar CLI. For more information about Stellar CLI, see the [Stellar CLI documentation](../../../tools/cli/README.mdx).
 
 ```bash
 # Verify if `stellar` command line is installed
@@ -287,5 +287,5 @@ curl -X POST "http://localhost:8080/auth" \
 
 :::
 
-[sep1-ap]: ../sep1/README.mdx
+[sep1-ap]: ./sep1.mdx
 [sep-10]: https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0010.md
diff --git a/docs/platforms/anchor-platform/sep-guide/sep24/configuration.mdx b/docs/platforms/anchor-platform/sep-guide/sep24/configuration.mdx
@@ -207,5 +207,5 @@ The demo wallet should be able to find your `stellar.toml` file, authenticate us
 [flyway]: https://documentation.red-gate.com/fd/redgate-flyway-documentation-138346877.html
 [sep-24-ref-ui]: https://github.com/stellar/sep24-reference-ui
 [sep-24-ref]: https://github.com/stellar/java-stellar-anchor-sdk/tree/develop/kotlin-reference-server
-[sep1-ap]: ../sep1/README.mdx
+[sep1-ap]: ../sep1.mdx
 [json-rpc-methods]: ../../api-reference/platform/rpc/methods/README.mdx
diff --git a/docs/platforms/anchor-platform/sep-guide/sep24/faq.mdx b/docs/platforms/anchor-platform/sep-guide/sep24/faq.mdx
@@ -36,4 +36,4 @@ Utilize the `data.client_domain` attributes within the JWT token. In the presenc
 
 [sep-9]: https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0009.md
 [sep-24]: https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0024.md
-[clients]: ../sep10/README.mdx
+[clients]: ../sep10.mdx
diff --git a/docs/platforms/anchor-platform/sep-guide/sep24/getting-started.mdx b/docs/platforms/anchor-platform/sep-guide/sep24/getting-started.mdx
@@ -29,6 +29,6 @@ The customer can then use the digital asset on the Stellar network for remittanc
 
 [sep-24]: https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0024.md
 [installation-ap]: ../../admin-guide/getting-started.mdx
-[sep1-ap]: ../sep1/README.mdx
-[sep10-ap]: ../sep10/README.mdx
-[sep45-ap]: ../sep45/README.mdx
+[sep1-ap]: ../sep1.mdx
+[sep10-ap]: ../sep10.mdx
+[sep45-ap]: ../sep45.mdx
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
@@ -56,7 +56,7 @@ How you handle KYC is up to you: there are many services that provide KYC soluti
 
 Some countries require different KYC fields depending on the amount to be deposited or withdrawn. If that's the case in your jurisdiction and you need to adapt your KYC forms based on the deposit or withdrawal amount, simply add an amount field before the KYC form, and make sure that the KYC fields are updated based on that value.
 
-KYC information should be linked to the session created through [Stellar Web Authentication](../sep10/README.mdx) and, consequently, to the user, so you only need to ask the user for it once. After the first KYC flow is complete, a user shouldn't have to input the information again.
+KYC information should be linked to the session created through [Stellar Web Authentication](../sep10.mdx) and, consequently, to the user, so you only need to ask the user for it once. After the first KYC flow is complete, a user shouldn't have to input the information again.
 
 Make sure the errors and validation messages are clear and include instructions for what to do next to ensure a good user experience and increase the KYC conversion rate. You should also localize messages based on the user's language and location.
 

diff --git a/docs/platforms/anchor-platform/sep-guide/sep31/configuration.mdx b/docs/platforms/anchor-platform/sep-guide/sep31/configuration.mdx
@@ -337,7 +337,7 @@ SECRET_CALLBACK_API_AUTH_SECRET=<your jwt encryption key>
 We'll define the server that implements the endpoints defined in the Callback API in the following section.
 
 [sep31-get-info]: https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0031.md#get-info
-[sep1-ap]: ../sep1/README.mdx
+[sep1-ap]: ../sep1.mdx
 [get-rates-api]: ../../api-reference/callbacks/get-rates.api.mdx
 [sep38]: https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0038.md
 [sep38-post-quote]: https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0038.md#post-quote

diff --git a/docs/platforms/anchor-platform/sep-guide/sep31/getting-started.mdx b/docs/platforms/anchor-platform/sep-guide/sep31/getting-started.mdx
@@ -17,6 +17,6 @@ Before continuing with this section, make sure that you have already [installed]
 
 [sep-31]: https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0031.md
 [installation-ap]: ../../admin-guide/getting-started.mdx
-[sep1-ap]: ../sep1/README.mdx
-[sep10-ap]: ../sep10/README.mdx
-[sep45-ap]: ../sep45/README.mdx
+[sep1-ap]: ../sep1.mdx
+[sep10-ap]: ../sep10.mdx
+[sep45-ap]: ../sep45.mdx
diff --git a/docs/platforms/anchor-platform/sep-guide/sep31/integration.mdx b/docs/platforms/anchor-platform/sep-guide/sep31/integration.mdx
@@ -601,7 +601,7 @@ items:
 </CodeExample>
 
 [ap-api]: ../../README.mdx
-[ap-sep10]: ../sep10/README.mdx
+[ap-sep10]: ../sep10.mdx
 [sep12]: https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0012.md
 [demo-wallet]: https://demo-wallet.stellar.org
 [indicative]: https://www.investopedia.com/terms/i/indicativequote.asp

diff --git a/...nchor-platform/sep-guide/sep45/README.mdx → ...forms/anchor-platform/sep-guide/sep45.mdx b/...nchor-platform/sep-guide/sep45/README.mdx → ...forms/anchor-platform/sep-guide/sep45.mdx
@@ -136,7 +136,7 @@ These fields should match the configuration options set in the [Enable SEP-45](#
 
 :::
 
-[sep1-ap]: ../sep1/README.mdx
+[sep1-ap]: ./sep1.mdx
 [sep-45]: https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0045.md
 [sep-45-contract]: https://github.com/stellar/anchor-platform/tree/main/soroban/contracts/web-auth
 [rpc-providers]: /docs/data/apis/rpc/providers
diff --git a/docs/platforms/anchor-platform/sep-guide/sep6/configuration.mdx b/docs/platforms/anchor-platform/sep-guide/sep6/configuration.mdx
@@ -244,7 +244,7 @@ Initiate a deposit transaction by doing the following:
 The demo wallet should be able to find your `stellar.toml` file, authenticate using the Stellar keypair you just created, and initiate a transaction.
 
 [sep-6]: https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0006.md
-[sep1-ap]: ../sep1/README.mdx
+[sep1-ap]: ../sep1.mdx
 [stellar-demo-wallet]: https://demo-wallet.stellar.org/
 [get-rates-api]: ../../api-reference/callbacks/get-rates.api.mdx
 [sep38]: https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0038.md

diff --git a/docs/platforms/anchor-platform/sep-guide/sep6/getting-started.mdx b/docs/platforms/anchor-platform/sep-guide/sep6/getting-started.mdx
@@ -29,6 +29,6 @@ The customer can then use the digital asset on the Stellar network for remittanc
 
 [sep-6]: https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0006.md
 [installation-ap]: ../../admin-guide/getting-started.mdx
-[sep1-ap]: ../sep1/README.mdx
-[sep10-ap]: ../sep10/README.mdx
-[sep45-ap]: ../sep45/README.mdx
+[sep1-ap]: ../sep1.mdx
+[sep10-ap]: ../sep10.mdx
+[sep45-ap]: ../sep45.mdx