Fix algolia crawler errors

docs/build/apps/example-application-tutorial/anchor-integration/sep1.mdx

@@ -3,7 +3,7 @@ title: "SEP-1: Stellar TOML"
 sidebar_position: 20
 ---
 
-The [stellar.toml file](https://developers.stellar.org/docs/issuing-assets/publishing-asset-info#completing-your-stellartoml) is a common place where the Internet can find information about an organization’s Stellar integration. Regardless of which type of transfer we want to use (SEP-6 or SEP-24), we'll need to start with SEP-1.
+The [`stellar.toml` file](../../../../tokens/publishing-asset-info.mdx#completing-your-stellartoml) is a common place where the Internet can find information about an organization’s Stellar integration. Regardless of which type of transfer we want to use (SEP-6 or SEP-24), we'll need to start with SEP-1.
 
 For anchors, we’re interested in the `CURRENCIES` they issue, the `TRANSFER_SERVER` and/or `TRANSFER_SERVER_SEP0024` keywords that indicate if the anchor supports SEP-6, SEP-24, or both, and the `WEB_AUTH_ENDPOINT` which allows a wallet to set up an authenticated user session.
 

docs/build/apps/ingest-sdk/overview.mdx

@@ -23,9 +23,9 @@ To build an example streaming network ingestion pipeline from live Stellar netwo
 - 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`
-- `stellar-core` must be [installed](https://developers.stellar.org/network/core-node/admin-guide/installation) on your workstation and available on your o/s PATH
+- `stellar-core` must be [installed](../../../validators/admin-guide/installation.mdx) on your workstation and available on your o/s PATH
 
-The [Stellar network data model](https://developers.stellar.org/docs/learn/fundamentals/stellar-data-structures) is defined in an IDL format expressed in [XDR encoding](https://github.com/stellar/stellar-xdr). Our example application is only interested in a small subset of the overall transaction data model related to buying and selling of assets, i.e. a payment, and defines its own data model internally:
+The [Stellar network data model](../../../learn/fundamentals/stellar-data-structures/README.mdx) is defined in an IDL format expressed in [XDR encoding](https://github.com/stellar/stellar-xdr). Our example application is only interested in a small subset of the overall transaction data model related to buying and selling of assets, i.e. a payment, and defines its own data model internally:
 
 <CodeExample>
 
@@ -41,13 +41,13 @@ The [Stellar network data model](https://developers.stellar.org/docs/learn/funda
 
 </CodeExample>
 
-The example application will run a [network ingestion pipeline](https://github.com/stellar/go/blob/master/ingest/doc.go) to derive a smaller `ApplicationPayment` model from the [Stellar network transaction data model](https://developers.stellar.org/docs/learn/fundamentals/stellar-data-structures) as 'source of origin' and thus enable the application to avoid large compute resources that would have been required for maintaining storage of the full Stellar network data model.
+The example application will run a [network ingestion pipeline](https://github.com/stellar/go/blob/master/ingest/doc.go) to derive a smaller `ApplicationPayment` model from the [Stellar network transaction data model](../../../learn/fundamentals/stellar-data-structures/README.mdx) as 'source of origin' and thus enable the application to avoid large compute resources that would have been required for maintaining storage of the full Stellar network data model.
 
 The ingestion pipeline will perform three distinct stream processor roles:
 
 ### Inbound Adapter
 
-Acts as the 'source of origin' for the pipeline. Retrieves [LedgerCloseMeta](https://github.com/stellar/go/blob/f30d11432e81c7a7cbb739a694520f729bbb31dd/xdr/xdr_generated.go#L18358) generated from a Stellar network using captive core. `LedgerCloseMeta` is the top-level aggregate in the Stellar data model of which all [Stellar network transaction data](https://developers.stellar.org/docs/learn/fundamentals/stellar-data-structures) is nested within. Publishes the `LedgerCloseMeta` onto the pipeline.
+Acts as the 'source of origin' for the pipeline. Retrieves [LedgerCloseMeta](https://github.com/stellar/go/blob/f30d11432e81c7a7cbb739a694520f729bbb31dd/xdr/xdr_generated.go#L18358) generated from a Stellar network using captive core. `LedgerCloseMeta` is the top-level aggregate in the Stellar data model of which all [Stellar network transaction data](../../../learn/fundamentals/stellar-data-structures/README.mdx) is nested within. Publishes the `LedgerCloseMeta` onto the pipeline.
 
 ### Transformer
 
@@ -59,4 +59,4 @@ Acts as the termination of the pipeline, it subscribes to receive `ApplicationPa
 
 ### Summary
 
-Refer to [Ingestion Pipeline Sample Application](ingestion-pipeline-code.mdx) for complete code demonstrating usage of the 'ingestion' SDK packages to create these adapters and transformers and run a live pipeline against the Stellar network.
+Refer to [Ingestion Pipeline Sample Application](./ingestion-pipeline-code.mdx) for complete code demonstrating usage of the 'ingestion' SDK packages to create these adapters and transformers and run a live pipeline against the Stellar network.

docs/build/apps/moneygram-access-integration-guide.mdx

@@ -528,13 +528,13 @@ onMessage: (transaction) => {
       const response = await stellar.submitTransaction(transferTransaction);
       console.log("Stellar-generated transaction ID: ", response.id);
     } catch (error) {
-      /* 
+      /*
         In case it's not a 504 (timeout) error, the application could try some
         resolution strategy based on the error kind.
-        
+
         On Stellar docs you can find a page dedicated to error handling:
         https://developers.stellar.org/docs/learn/encyclopedia/errors-and-debugging/error-handling
-        
+
         And status/result codes:
         https://developers.stellar.org/docs/data/horizon/api-reference/errors
       */
@@ -555,7 +555,7 @@ onMessage: (transaction) => {
           detail: 'The transaction failed when submitted to the stellar network.
             The `extras.result_codes` field on this response contains further details.
             Descriptions of each code can be found at:
-            https://developers.stellar.org/api/errors/http-status-codes/horizon-specific/transaction-failed/',
+            https://developers.stellar.org/docs/data/horizon/api-reference/errors/http-status-codes/horizon-specific/transaction-failed',
           extras: {
             envelope_xdr: 'AAAAAgAAAADBjF7n9gfByOwlnyaJH...k4BRagf/////////8AAAAAAAAAAA==',
             result_codes: { transaction: 'tx_bad_seq' },
@@ -767,7 +767,7 @@ print(
 
 [moneygram access]: https://stellar.org/moneygram?locale=e
 [moneygram access wallet mvp implementation]: https://github.com/stellar/moneygram-access-wallet-mvp
-[stellar wallet sdk docs]: https://developers.stellar.org/docs/category/build-a-wallet-with-the-wallet-sdk
+[stellar wallet sdk docs]: /docs/category/build-a-wallet-with-the-wallet-sdk
 [stellar wallet sdk repository]: https://github.com/stellar/typescript-wallet-sdk
 [stellar test anchor]: https://testanchor.stellar.org/.well-known/stellar.toml
 [stellar demo wallet]: https://demo-wallet.stellar.org
@@ -777,12 +777,12 @@ print(
 [stellar lab]: https://laboratory.stellar.org/
 [anchor directory]: https://resources.stellar.org/anchors?
 [lobstr]: https://lobstr.co/
-[trustline]: https://developers.stellar.org/api/resources/operations/object/change-trust/
-[sell offer]: https://developers.stellar.org/api/resources/operations/object/sell-offer/
+[trustline]: ../../data/horizon/api-reference/resources/operations/object/change-trust.mdx
+[sell offer]: ../../data/horizon/api-reference/resources/operations/object/sell-offer.mdx
 [postmessage]: https://developer.mozilla.org/en-US/docs/Web/API/Window/postMessage
-[submitting transactions and handling errors gracefully]: https://developers.stellar.org/docs/learn/encyclopedia/errors-and-debugging/error-handling/
-[path payments]: https://developers.stellar.org/api/resources/operations/object/path-payment-strict-receive/
-[claimable balances]: https://developers.stellar.org/api/resources/operations/object/create-claimable-balance/
+[submitting transactions and handling errors gracefully]: ../../learn/encyclopedia/errors-and-debugging/error-handling.mdx
+[path payments]: ../../data/horizon/api-reference/resources/operations/object/path-payment-strict-receive.mdx
+[claimable balances]: ../../data/horizon/api-reference/resources/operations/object/create-claimable-balance.mdx
 [moneygram screening questionnaire]: https://stellarquestionnaire.typeform.com/to/RD1a71wQ
 [gcdnjubqsx7ajwljacmj7i4bc3z47bqutmheiczle6mu4kqbryg5jy6b]: https://stellar.expert/explorer/testnet/asset/SRT-GCDNJUBQSX7AJWLJACMJ7I4BC3Z47BQUTMHEICZLE6MU4KQBRYG5JY6B-1
 [gbbd47if6lwk7p7mdevscwr7dpuwv3ny3dtqevfl4nat4aqh3zllfla5]: https://stellar.expert/explorer/testnet/asset/USDC-GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5-1

docs/build/smart-contracts/example-contracts/liquidity-pool.mdx

@@ -493,7 +493,7 @@ fn initialize(e: Env, token_wasm_hash: BytesN<32>, taken_a: Address, token_b: Ad
 [interacting with contracts for `token_a` and `token_b`]: #token-transfers-tofrom-the-lp-contract
 [`token` example contract]: ./tokens.mdx
 [installed]: ../getting-started/deploy-to-testnet.mdx#two-step-deployment
-[lexicographical order]: https://developers.stellar.org/docs/encyclopedia/liquidity-on-stellar-sdex-liquidity-pools#liquidity-pool-participation
+[lexicographical order]: ../../../learn/encyclopedia/sdex/liquidity-on-stellar-sdex-liquidity-pools.mdx#liquidity-pool-participation
 
 ### A "Constant Product" Liquidity Pool
 

docs/build/smart-contracts/getting-started/setup.mdx

@@ -263,7 +263,7 @@ stellar keys address alice
 
 Like the Network configs, the `--global` means that the identity gets stored in `~/.config/soroban/identity/alice.toml`. You can omit the `--global` flag to store the identity in your project's `.soroban/identity` folder instead.
 
-By default, `stellar keys generate` will fund the account using [Friendbot](https://developers.stellar.org/docs/fundamentals-and-concepts/testnet-and-pubnet#friendbot). To disable this behavior, append `--no-fund` to the command when running it.
+By default, `stellar keys generate` will fund the account using [Friendbot](../../../learn/fundamentals/networks.mdx#friendbot). To disable this behavior, append `--no-fund` to the command when running it.
 
 [rust]: https://www.rust-lang.org/
-[stellar cli]: setup.mdx#install-the-stellar-cli
+[stellar cli]: #install-the-stellar-cli

docs/build/smart-contracts/getting-started/storing-data.mdx

@@ -134,7 +134,7 @@ env.storage().instance().extend_ttl(100, 100);
 
 All contract data has a Time To Live (TTL), measured in ledgers, that must be periodically extended. If an entry's TTL is not periodically extended, the entry will eventually become "archived." You can learn more about this in the [State Archival](../../../learn/encyclopedia/storage/state-archival.mdx) document.
 
-For now, it's worth knowing that there are three kinds of storage: `Persistent`, `Temporary`, and `Instance`. This contract only uses `Instance` storage: `env.storage().instance()`. Every time the counter is incremented, this storage's TTL gets extended by 100 [ledgers](https://developers.stellar.org/docs/fundamentals-and-concepts/stellar-data-structures/ledgers), or about 500 seconds.
+For now, it's worth knowing that there are three kinds of storage: `Persistent`, `Temporary`, and `Instance`. This contract only uses `Instance` storage: `env.storage().instance()`. Every time the counter is incremented, this storage's TTL gets extended by 100 [ledgers](../../../learn/fundamentals/stellar-data-structures/ledgers.mdx), or about 500 seconds.
 
 ### Build the contract
 

docs/data/hubble/admin-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](https://developers.stellar.org/network/hubble/analyst-guide/connecting) 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](../../analyst-guide/connecting.mdx) section.
 
 ## Why Run stellar-dbt-public?
 

docs/data/hubble/admin-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](https://developers.stellar.org/network/hubble/connecting) 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](../../analyst-guide/connecting.mdx) section.
 
 ## Why Run stellar-etl-ariflow?
 

docs/data/hubble/admin-guide/source-system-ingestion/overview.mdx

@@ -5,7 +5,7 @@ sidebar_position: 0
 
 Stellar network data ingestion in Hubble is done through [stellar-etl](https://github.com/stellar/stellar-etl/tree/master). stellar-etl reads and transforms Stellar network data into OLAP friendly JSON files.
 
-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. Instructions on how to access this data can be found in the [Connecting](https://developers.stellar.org/network/hubble/analyst-guide/connecting) section.
+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. Instructions on how to access this data can be found in the [Connecting](../../analyst-guide/connecting.mdx) section.
 
 ## Why Run stellar-etl?