📝 Restructure ledger entry overview

Co-authored-by: Codex <noreply@openai.com>

Author: JFWooten4

docs/learn/fundamentals/stellar-data-structures/ledgers/entries.mdx

@@ -6,76 +6,82 @@ description: "Ledger entries are the durable data structures that make up the St
 ---
 
 
-Data is stored on the ledger as ledger entries, akin to key-value stores. Each key is a `LedgerKey` instance defined in [protocol XDR](https://github.com/stellar/stellar-xdr/blob/v27.0/Stellar-ledger-entries.x#L588). Keys state which object we reference, pointing to `LedgerEntry` values defined in [protocol XDR](https://github.com/stellar/stellar-xdr/blob/v27.0/Stellar-ledger-entries.x#L548). Thus entry instances contain the data stored at that key.
+Data is stored on the ledger as ledger entries, akin to key-value stores. Each key is a `LedgerKey` instance. Keys state which object we reference, pointing to `LedgerEntry` values. Thus entry instances contain the data stored at that key.
+
+:::note Internal Design
 
 Each `LedgerKey` contains only the fields needed to identify its entry. Those identifying fields also appear in the full entry. For example, an `OfferKey` [contains](https://github.com/stellar/stellar-xdr/blob/v27.0/Stellar-ledger-entries.x#L603-L608) its `sellerID` and `offerID`, while the corresponding `OfferEntry` [contains](https://github.com/stellar/stellar-xdr/blob/v27.0/Stellar-ledger-entries.x#L326-L349) those fields along with the full record of ledger data: `amount`, `price`, [assets](https://github.com/stellar/stellar-xdr/blob/v27.0/Stellar-ledger-entries.x#L55-L67), and more.
 
-## 10 Ledger Key Cases
+:::
+
+## Entry Types
+
+The descriptions below summarize the linked conceptual documentation. The protocol XDR definitions of [`LedgerKey`](https://github.com/stellar/stellar-xdr/blob/v27.0/Stellar-ledger-entries.x#L588-L651) and [`LedgerEntry`](https://github.com/stellar/stellar-xdr/blob/v27.0/Stellar-ledger-entries.x#L548-L586) are the source of truth for the exact fields and types.
 
-### Account
+### 1. Account {#account}
 
 The `AccountEntry` holistically defines a Stellar account, including its balance, sequence number, thresholds, signers, and flags. Learn more in the [Accounts section](../accounts.mdx).
 
 - **Key:** Identified by `AccountID`
 - **Entry:** Full account record including balance, sequence number, thresholds, flags, home domain, and list of signers. Tracks [subentries](../accounts.mdx#subentries) that drive the minimum balance requirement.
 
-### Trustline
+### 2. Trustline {#trustline}
 
 The `TrustLineEntry` defines a balance line to a non-native asset issued on the network. It is  created and updated via [`changeTrustOp`](../../transactions/list-of-operations.mdx#change-trust). Learn more in the [Trustlines section](../accounts.mdx#trustlines).
 
 - **Key:** `(AccountID, asset)`
 - **Entry:** Trustline state for a non-native asset. Stores the asset balance, limit, authorization flags, and trading liability counters.
 
-### Offer
+### 3. Offer {#offer}
 
 The `OfferEntry` represents an offer made on the SDEX order book. Learn more in the [orderbooks DEX section](../../liquidity-on-stellar-sdex-liquidity-pools.mdx#orderbook).
 
 - **Key:** `(sellerID, offerID)`
 - **Entry:** A single offer on the DEX. Contains the selling and buying assets, amount, price, and [passive](../../liquidity-on-stellar-sdex-liquidity-pools.mdx#passive-offer) flags.
 
-### Account Data
+### 4. Account Data {#account-data}
 
 A `DataEntry` stores key-value data entries attached to an account. It is used through the [`manageDataOp`](../../transactions/list-of-operations.mdx#manage-data).
 
 - **Key:** `(accountID, dataName)`
 - **Entry:** Arbitrary key-value pair (`DataValue`) attached to an account.
 
-### Claimable Balance
+### 5. Claimable Balance {#claimable-balance}
 
 The `ClaimableBalanceEntry` tracks a balance that may or may not actively be claimable. Learn more in the [Claimable Balances section](../../../../build/guides/transactions/claimable-balances.mdx).
 
 - **Key:** `balanceID`
 - **Entry:** Tracks the asset, amount, claimants, [predicates](../../../../build/guides/transactions/claimable-balances.mdx#other-parameters), and optional flags.
 
-### Liquidity Pool
+### 6. Liquidity Pool {#liquidity-pool}
 
 The `LiquidityPoolEntry` defines the configuration of a constant-product liquidity pool between two assets. Learn more in the [liquidity pools section](../../liquidity-on-stellar-sdex-liquidity-pools.mdx#liquidity-pools).
 
 - **Key:** `liquidityPoolID`
 - **Entry:** Holds pool parameters (two assets, fee rate), reserves, total pool shares, and a pool's trustline count (to prevent entry scanning).
 
-### Contract Data
+### 7. Contract Data {#contract-data}
 
 `ContractDataEntry` stores a piece of data under a contract-defined key. Learn more in the [Persisting Contract Data section](../../contract-development/storage/persisting-data.mdx#ledger-entries).
 
 - **Key:** `(contract, key, durability)`
 - **Entry:** Stores the `SCVal` value associated with that key under the contract. Used for Soroban data storage alongside keys.
 
-### Contract Code
+### 8. Contract Code {#contract-code}
 
 The `ContractCodeEntry` contains the Wasm bytecode of a Soroban contract. Learn more in the [Smart Contracts Overview section](../../../../build/smart-contracts/overview.mdx).
 
 - **Key:** `hash` of the Wasm module.
 - **Entry:** Contains the Wasm bytecode and associated cost inputs to deploy or invoke contracts. [Fee metadata](../../fees-resource-limits-metering.mdx#resource-fee) takes into account component factors like number of instructions, functions, and variables.
 
-### Config Setting
+### 9. Config Setting {#config-setting}
 
 The `ConfigSettingEntry` holds governed network configuration values for over a dozen rules. Learn more in the [Soroban Settings section](../../../../validators/admin-guide/soroban-settings.mdx).
 
 - **Key:** `configSettingID` (index of setting [in list](https://github.com/stellar/stellar-xdr/blob/v27.0/Stellar-contract-config-setting.x#L373-L396))
 - **Entry:** Active value of a network-level parameter (e.g., protocol limits, compute fees, state archival). The whole validator quorum set has to agree on these values.
 
-### TTL
+### 10. TTL {#ttl}
 
 The `TTLEntry` defines the time-to-live of an associated contract data or code entry. Learn more in the [State archival section](../../contract-development/storage/state-archival.mdx#ttl).