new paths

Author: JFWooten4

docs/data/apis/migrate-from-horizon-to-rpc.mdx

@@ -124,7 +124,7 @@ In the interim the [`getTransactions`] method can be used to retrieve the meta X
 [`getVersionInfo`]: ./rpc/api-reference/methods/getVersionInfo.mdx
 [`getHealth`]: ./rpc/api-reference/methods/getHealth.mdx
 [`getNetwork`]: ./rpc/api-reference/methods/getNetwork.mdx
-[`getLedgers`]: ./rpc/api-reference/methods/getledgers/README.mdx
+[`getLedgers`]: ./rpc/api-reference/methods/getLedgers.mdx
 [`getTransactions`]: ./rpc/api-reference/methods/getTransactions.mdx
 [`getTransaction`]: ./rpc/api-reference/methods/getTransaction.mdx
 [`getEvents`]: ./rpc/api-reference/methods/getEvents.mdx

docs/data/apis/rpc/api-reference/methods/README.mdx

@@ -11,7 +11,7 @@ All you need to know about available RPC methods, parameters and responses, and
 
 Don't know which endpoint you need to get what you want? A lot of the returned fields are deeply-nested [XDR structures](../../../../../learn/fundamentals/data-format/xdr.mdx#more-about-xdr), so it can be hard to figure out what kind of information is available in each of these. Here's a bit of a dive into what the "workhorse" endpoints provide, in decreasing order of granularity:
 
-- [`getLedgers`](./getledgers/README.mdx) operates at the block level, providing you with the full, complete details of what occurred during application of that ledger (known as "ledger metadata", defined in the protocol by the [`LedgerCloseMeta`](https://github.com/stellar/stellar-xdr/blob/v22.0/Stellar-ledger.x#L539) union, specifically the `V1` iteration). Each of the subsequent endpoints is just a microscope into a subset of the data available provided by this endpoint. Metadata includes things like:
+- [`getLedgers`](./getLedgers.mdx) operates at the block level, providing you with the full, complete details of what occurred during application of that ledger (known as "ledger metadata", defined in the protocol by the [`LedgerCloseMeta`](https://github.com/stellar/stellar-xdr/blob/v22.0/Stellar-ledger.x#L539) union, specifically the `V1` iteration). Each of the subsequent endpoints is just a microscope into a subset of the data available provided by this endpoint. Metadata includes things like:
   - Details for recreating the blockchain's state (see [Ledger Headers](../../../../../learn/fundamentals/stellar-data-structures/ledgers/headers.mdx) for more).
   - The consensus information that led to the block closing (see [Stellar Consensus Protocol](../../../../../learn/fundamentals/stellar-consensus-protocol.mdx)).
   - The set of transactions, their respective operations, and the results of applying those transactions in this block (see [Transactions](../../../../../learn/fundamentals/transactions/operations-and-transactions.mdx)).

docs/data/apis/rpc/providers.mdx

@@ -24,7 +24,7 @@ These providers allow access to the Futurenet, Testnet and Mainnet network.
 | [Exaion](https://crypto.exaion.com) | ❌ | ❌ | ✅ | ✅ | ✅ |
 | [Alchemy](https://dashboard.alchemy.com/?utm_source=chain_partner&utm_medium=referral&utm_campaign=stellar) | ❌ | ✅ | ✅ | ✅ | ❌ |
 
-\*_RPC Archive is a new option for those looking to retrieve full ledger history. Currently only the [getLedgers](./api-reference/methods/getledgers/README.mdx) RPC method supports this feature. You can choose one of the providers above, or create your own getLedgers archive by following [these steps](./admin-guide/data-lake-integration.mdx)._
+\*_RPC Archive is a new option for those looking to retrieve full ledger history. Currently only the [getLedgers](./api-reference/methods/getLedgers.mdx) RPC method supports this feature. You can choose one of the providers above, or create your own getLedgers archive by following [these steps](./admin-guide/data-lake-integration.mdx)._
 
 _The "Dedicated Nodes" column represents providers who host full nodes as a service._
 

i18n/es/docusaurus-plugin-content-docs/current/data/apis/migrate-from-horizon-to-rpc.mdx

@@ -124,7 +124,7 @@ Mientras tanto, el método [`getTransactions`] puede usarse para recuperar el me
 [`getVersionInfo`]: ./rpc/api-reference/methods/getVersionInfo.mdx
 [`getHealth`]: ./rpc/api-reference/methods/getHealth.mdx
 [`getNetwork`]: ./rpc/api-reference/methods/getNetwork.mdx
-[`getLedgers`]: ./rpc/api-reference/methods/getledgers/README.mdx
+[`getLedgers`]: ./rpc/api-reference/methods/getLedgers.mdx
 [`getTransactions`]: ./rpc/api-reference/methods/getTransactions.mdx
 [`getTransaction`]: ./rpc/api-reference/methods/getTransaction.mdx
 [`getEvents`]: ./rpc/api-reference/methods/getEvents.mdx

i18n/es/docusaurus-plugin-content-docs/current/data/apis/rpc/api-reference/methods/README.mdx

@@ -11,7 +11,7 @@ Todo lo que necesitas saber sobre los métodos RPC disponibles, parámetros y re
 
 ¿No sabes cuál endpoint necesitas para obtener lo que quieres? Muchos de los campos devueltos son estructuras [XDR](../../../../../learn/fundamentals/data-format/xdr.mdx#more-about-xdr) profundamente anidadas, por lo que puede ser difícil saber qué tipo de información está disponible en cada una de ellas. Aquí tienes un vistazo a lo que proporcionan los endpoints "caballo de batalla", en orden decreciente de granularidad:
 
-- [`getLedgers`](./getledgers/README.mdx) opera a nivel de bloque, proporcionándote los detalles completos de lo que ocurrió durante la aplicación de ese ledger (conocido como "metadatos del ledger", definido en el protocolo por la unión [`LedgerCloseMeta`](https://github.com/stellar/stellar-xdr/blob/v22.0/Stellar-ledger.x#L539), específicamente la iteración `V1`). Cada uno de los endpoints subsiguientes es solo un microscopio a un subconjunto de los datos disponibles proporcionados por este endpoint. Los metadatos incluyen cosas como:
+- [`getLedgers`](./getLedgers.mdx) opera a nivel de bloque, proporcionándote los detalles completos de lo que ocurrió durante la aplicación de ese ledger (conocido como "metadatos del ledger", definido en el protocolo por la unión [`LedgerCloseMeta`](https://github.com/stellar/stellar-xdr/blob/v22.0/Stellar-ledger.x#L539), específicamente la iteración `V1`). Cada uno de los endpoints subsiguientes es solo un microscopio a un subconjunto de los datos disponibles proporcionados por este endpoint. Los metadatos incluyen cosas como:
   - Detalles para recrear el estado de la blockchain (consulta [Ledger Headers](../../../../../learn/fundamentals/stellar-data-structures/ledgers/headers.mdx) para más información).
   - La información del consenso que condujo al cierre del bloque (ver [Stellar Consensus Protocol](../../../../../learn/fundamentals/stellar-consensus-protocol.mdx)).
   - El conjunto de transacciones, sus respectivas operaciones y los resultados de aplicar esas transacciones en este bloque (ver [Transacciones](../../../../../learn/fundamentals/transactions/operations-and-transactions.mdx)).

i18n/es/docusaurus-plugin-content-docs/current/data/apis/rpc/providers.mdx

@@ -23,7 +23,7 @@ Estos proveedores permiten el acceso a las redes Futurenet, Testnet y Mainnet.
 | [Uniblock](https://www.uniblock.dev/)                             | ❌         | ✅       | ✅       | ❌               | ❌           |
 | [Exaion](https://crypto.exaion.com)                               | ❌         | ❌       | ✅       | ✅               |             |
 
-\*_RPC Archive es una nueva opción para quienes buscan recuperar el historial completo del ledger. Actualmente, solo el método RPC [getLedgers](./api-reference/methods/getledgers/README.mdx) soporta esta característica. Puedes elegir uno de los proveedores anteriores o crear tu propio archivo getLedgers siguiendo [estos pasos](./admin-guide/data-lake-integration.mdx).
+\*_RPC Archive es una nueva opción para quienes buscan recuperar el historial completo del ledger. Actualmente, solo el método RPC [getLedgers](./api-reference/methods/getLedgers.mdx) soporta esta característica. Puedes elegir uno de los proveedores anteriores o crear tu propio archivo getLedgers siguiendo [estos pasos](./admin-guide/data-lake-integration.mdx).
 
 _La columna "Dedicated Nodes" representa proveedores que alojan nodos completos como servicio._
 

nginx/includes/redirects.conf

@@ -152,7 +152,7 @@ rewrite ^/docs/learn/encyclopedia/fee-bump-transactions$ "/docs/learn/encycloped
 rewrite ^/docs/learn/encyclopedia/channel-accounts$ "/docs/learn/encyclopedia/transactions-specialized/channel-accounts" permanent;
 rewrite ^/docs/learn/encyclopedia/contract-development/fees-and-metering "/docs/learn/fundamentals/fees-resource-limits-metering" permanent;
 rewrite ^/docs/learn/encyclopedia/inflation$ "/docs/learn/encyclopedia/network-configuration/inflation" permanent;
-rewrite ^/docs/learn/encyclopedia/ledger-headers$ "/docs/learn/encyclopedia/network-configuration/ledger-headers" permanent;
+rewrite ^/docs/learn/encyclopedia/ledger-headers$ "/docs/learn/fundamentals/stellar-data-structures/ledgers/headers" permanent;
 rewrite ^/docs/learn/encyclopedia/liquidity-on-stellar-sdex-liquidity-pools$ "/docs/learn/fundamentals/liquidity-on-stellar-sdex-liquidity-pools" permanent;
 rewrite ^/docs/learn/encyclopedia/sdex$ "/docs/learn/fundamentals/liquidity-on-stellar-sdex-liquidity-pools" permanent;
 rewrite ^/docs/learn/encyclopedia/lumen-supply-metrics$ "/docs/learn/fundamentals/lumens#lumen-supply-metrics" permanent;

routes.txt

@@ -524,6 +524,8 @@
 /docs/learn/fundamentals/stellar-data-structures/contracts
 /docs/learn/fundamentals/stellar-data-structures/events
 /docs/learn/fundamentals/stellar-data-structures/ledgers
+/docs/learn/fundamentals/stellar-data-structures/ledgers/entries
+/docs/learn/fundamentals/stellar-data-structures/ledgers/headers
 /docs/learn/fundamentals/stellar-ecosystem-proposals
 /docs/learn/fundamentals/stellar-stack
 /docs/learn/fundamentals/transactions