Remove padding and 'd' suffix from XLS numbers in preambles and directory/file names

Copilot · mvadari · Copilot · commit a18540cc7120 · 2025-08-20T16:27:00.000Z
Co-authored-by: mvadari &lt;8029314+mvadari@users.noreply.github.com&gt;
diff --git a/XLS-12-secret-numbers/README.md b/XLS-12-secret-numbers/README.md
@@ -1,5 +1,5 @@
 <pre>
-xls: 0012
+xls: 12
 title: Secret Numbers
 description: Derive XRPL account keypairs based on 8x 6 digits for user-friendly, language-agnostic account secrets
 author: Wietse Wind <w@xrpl-labs.com>
diff --git a/XLS-2-destination-information/README.md b/XLS-2-destination-information/README.md
@@ -1,5 +1,5 @@
 <pre>
-xls: 0002d
+xls: 2
 title: XRPL destination information
 description: A standard for encoding destination information with backwards compatibility for web browsers
 author: Community Contributors
diff --git a/XLS-2-destination-information/xls-2-reference.js b/XLS-2-destination-information/xls-2-reference.js
diff --git a/XLS-20-non-fungible-tokens/README.md b/XLS-20-non-fungible-tokens/README.md
@@ -1,5 +1,5 @@
 <pre>
-xls: 0020
+xls: 20
 title: Non-Fungible Token Support
 description: Extensions to the XRP Ledger that support a native non-fungible token type with operations to enumerate, purchase, sell and hold such tokens
 author: David J. Schwartz, Ripple <david@ripple.com>, Aanchal Malhotra, Ripple <amalhotra@ripple.com>, Nikolaos D. Bougalis <nikb@bougalis.net>
diff --git a/XLS-23-lite-accounts/README.md b/XLS-23-lite-accounts/README.md
@@ -1,5 +1,5 @@
 <pre>
-xls: 0023
+xls: 23
 title: Lite Accounts (lower reserve, less features)
 description: A proposal for lite accounts with reduced account reserves but limited features
 author: Wietse Wind (WietseWind), Richard Holland
diff --git a/XLS-26-iou-token-metadata/README.md b/XLS-26-iou-token-metadata/README.md
@@ -1,5 +1,5 @@
 <pre>
-xls: 0026
+xls: 26
 title: IOU Token Metadata via xrp-ledger.toml
 description: A unified solution for IOU token metadata by adding optional fields to the existing xrp-ledger.toml standard
 author: Marc-Emanuel Otto (@Mwni), Ripple Contributors
diff --git a/XLS-26-iou-token-metadata/schematic-diagram.svg b/XLS-26-iou-token-metadata/schematic-diagram.svg
diff --git a/XLS-3-deeplink-signed-transactions/README.md b/XLS-3-deeplink-signed-transactions/README.md
@@ -1,5 +1,5 @@
 <pre>
-xls: 0003
+xls: 3
 title: Sharing and deeplinking signed transactions
 description: A standard for encoding HEX signed transactions for air-gapped submissions with deep link support
 author: Community Contributors
diff --git a/XLS-30-automated-market-maker/README.md b/XLS-30-automated-market-maker/README.md
@@ -1,5 +1,5 @@
 <pre>
-xls: 0030
+xls: 30
 title: Automated Market Maker on XRPL
 description: Non-custodial automated market maker as a native feature to the XRPL DEX with unique auction mechanism for trading advantages
 author: Aanchal Malhotra, Ripple <amalhotra@ripple.com>, David J. Schwartz, Ripple <david@ripple.com>
diff --git a/XLS-33-multi-purpose-tokens/README.md b/XLS-33-multi-purpose-tokens/README.md
@@ -1,5 +1,5 @@
 <pre>
-xls: 0033
+xls: 33
 title: Multi-Purpose Tokens (MPTs)
 description: Extensions to the XRP Ledger to support a more multi-purpose token type as an alternative to trust lines
 author: David Fuelling, Ripple <fuelling@ripple.com>, Nikolaos Bougalis <nikb@bougalis.net>, Greg Weisbrod, Ripple <gweisbrod@ripple.com>
diff --git a/XLS-34-paychan-escrow-for-tokens/README.md b/XLS-34-paychan-escrow-for-tokens/README.md
@@ -1,5 +1,5 @@
 <pre>
-xls: 0034d
+xls: 34
 title: Token-Enabled Escrows and Payment Channels
 description: Amendment to enable Escrows and PayChannels to use Trustline balances in addition to XRP
 author: Richard Holland, Xaman (@RichardAH), Denis Angell, Transia (@dangell7)
diff --git a/XLS-37-concise-transaction-identifier-ctid/README.md b/XLS-37-concise-transaction-identifier-ctid/README.md
@@ -1,5 +1,5 @@
 <pre>
-xls: 0037
+xls: 37
 title: Concise Transaction Identifier (CTID)
 description: A way to locate validated transactions using ledger sequence number, transaction index, and network ID rather than transaction hash
 author: Richard Holland, Xaman (@RichardAH), Ryan Molley, Crossmark (@interc0der)
diff --git a/XLS-38-cross-chain-bridge/README.md b/XLS-38-cross-chain-bridge/README.md
@@ -1,5 +1,5 @@
 <pre>
-xls: 0038
+xls: 38
 title: Cross-Chain Bridge
 description: Enabling transfer of value between sidechains through locking and issuing mechanisms
 author: Mayukha Vadari, Ripple <mvadari@ripple.com>, Scott Determan, Ripple <scott.determan@ripple.com>
diff --git a/XLS-39-clawback/README.md b/XLS-39-clawback/README.md
@@ -1,5 +1,5 @@
 <pre>
-xls: 0039
+xls: 39
 title: Clawback Support
 description: Enabling clawback for IOUs to meet regulatory requirements
 author: Nikolaos D. Bougalis <nikb@bougalis.net>, Shawn Xie, Ripple <shawnxie@ripple.com>
diff --git a/XLS-4-trustline-uri/README.md b/XLS-4-trustline-uri/README.md
@@ -1,5 +1,5 @@
 <pre>
-xls: 0004d
+xls: 4
 title: Standard URI instructing a wallet to add a trustline
 description: A URI standard for instructing wallets to add trustlines following the design of XLS-2d
 author: Community Contributors
diff --git a/XLS-40-decentralized-identity/README.md b/XLS-40-decentralized-identity/README.md
@@ -1,5 +1,5 @@
 <pre>
-xls: 0040
+xls: 40
 title: Decentralized Identity on XRP Ledger
 description: Implementation of native support for W3C Decentralized Identifiers (DIDs) on XRP Ledger
 author: Aanchal Malhotra, Ripple <amalhotra@ripple.com>
diff --git a/XLS-42-plugins/README.md b/XLS-42-plugins/README.md
@@ -1,5 +1,5 @@
 <pre>
-xls: 0042d
+xls: 42
 title: XRPL Plugins
 description: A plugin transactor API to make it easier for developers to modify rippled for sidechains without needing C++ knowledge
 author: Mayukha Vadari, Ripple <mvadari@ripple.com>
diff --git a/XLS-45-prepublish-validator-lists/README.md b/XLS-45-prepublish-validator-lists/README.md
@@ -1,5 +1,5 @@
 <pre>
-xls: 0045
+xls: 45
 title: Prepublish Validator Lists
 description: Future activation date and improved expiration handling of UNLs
 author: Ed Hennis, Ripple <ed@ripple.com>
diff --git a/XLS-46-dynamic-non-fungible-tokens/README.md b/XLS-46-dynamic-non-fungible-tokens/README.md
@@ -1,5 +1,5 @@
 <pre>
-xls: 0046
+xls: 46
 title: Dynamic Non Fungible Tokens (dNFTs)
 description: Support for XLS-20 NFTs to modify and upgrade token properties as mutable NFTs
 author: Vet, Mayukha Vadari, TeQu
diff --git a/XLS-47-PriceOracles/README.md b/XLS-47-PriceOracles/README.md
@@ -1,5 +1,5 @@
 <pre>
-xls: 0047
+xls: 47
 title: Price Oracles on XRP Ledger
 description: On-chain PriceOracle object to bridge blockchain and external world data for decentralized applications
 author: Gregory Tsipenyuk, Ripple <gtsipenyuk@ripple.com>
diff --git a/XLS-47-PriceOracles/README.pdf b/XLS-47-PriceOracles/README.pdf
diff --git a/XLS-5-tagged-addresses/README.md b/XLS-5-tagged-addresses/README.md
@@ -1,5 +1,5 @@
 <pre>
-xls: 0005
+xls: 5
 title: Tagged Addresses
 description: A standard for addresses that contain both the target wallet and destination tag as a single unit
 author: Nikolaos D. Bougalis, Ripple <nikb@bougalis.net>
diff --git a/XLS-52-NFTokenMintOffer/README.md b/XLS-52-NFTokenMintOffer/README.md
@@ -1,5 +1,5 @@
 <pre>
-xls: 0052
+xls: 52
 title: NFTokenMintOffer
 description: Extension to NFTokenMint transaction to allow NFToken Sell Offer creation at the same time as minting
 author: tequ
diff --git a/XLS-56-batch/README.md b/XLS-56-batch/README.md
@@ -1,5 +1,5 @@
 <pre>
-xls: 0056
+xls: 56
 title: Atomic/Batch Transactions
 description: A design to allow multiple transactions to be packaged together and executed as a single atomic unit
 author: Mayukha Vadari, Ripple <mvadari@ripple.com>
@@ -535,6 +535,6 @@ That is not supported. This also allows fee escalation to be calculated on the t
 
 Yes, as long as you use the master key of that account. Setting a regular key/signer list in the middle of the `Batch` won't work, since that key isn't valid at the time of processing the outer transaction (when the signatures are checked).
 
-### A.14: How will [transaction simulation](https://github.com/XRPLF/XRPL-Standards/tree/master/XLS-0069d-simulate) work with Batch?
+### A.14: How will [transaction simulation](https://github.com/XRPLF/XRPL-Standards/tree/master/XLS-69-simulate) work with Batch?
 
 Some extra processing will be needed for that. As a result, Batch transactions likely won't be able to be simulated at first.
diff --git a/XLS-65-single-asset-vault/README.md b/XLS-65-single-asset-vault/README.md
@@ -1,5 +1,5 @@
 <pre>
-xls: 0065d
+xls: 65
 title: Single Asset Tokenized Vault
 description: On-chain primitive for aggregating assets from depositors using Multi-Purpose-Tokens for ownership shares
 author: Vytautas Vito Tumas, Ripple <vtumas@ripple.com>, Aanchal Malhotra, Ripple <amalhotra@ripple.com>
@@ -13,7 +13,7 @@ created: 2021-01-01
 
 ## _Abstract_
 
-A Single Asset Vault is a new on-chain primitive for aggregating assets from one or more depositors, and making the assets available for other on-chain protocols. The Single Asset Vault uses [Multi-Purpose-Token](https://github.com/XRPLF/XRPL-Standards/tree/master/XLS-0033-multi-purpose-tokens) to represent ownership shares of the Vault. The Vault serves diverse purposes, such as lending markets, aggregators, yield-bearing tokens, asset management, etc. The Single Asset Vault decouples the liquidity provision functionality from the specific protocol logic.
+A Single Asset Vault is a new on-chain primitive for aggregating assets from one or more depositors, and making the assets available for other on-chain protocols. The Single Asset Vault uses [Multi-Purpose-Token](https://github.com/XRPLF/XRPL-Standards/tree/master/XLS-33-multi-purpose-tokens) to represent ownership shares of the Vault. The Vault serves diverse purposes, such as lending markets, aggregators, yield-bearing tokens, asset management, etc. The Single Asset Vault decouples the liquidity provision functionality from the specific protocol logic.
 
 ## Index
 
@@ -75,17 +75,17 @@ A Single Asset Vault is owned and managed by an account called the **Vault Owner
 
 #### 1.1.2 Access Control
 
-A Single Asset Vault can be either public or private. Any depositor can deposit and redeem liquidity from a public vault, provided they own sufficient shares. In contrast, access to private shares is controlled via [Permissioned Domains](https://github.com/XRPLF/XRPL-Standards/discussions/228), which use on-chain [Credentials](https://github.com/XRPLF/XRPL-Standards/tree/master/XLS-0070d-credentials) to manage access to the vault. Only depositors with the necessary credentials can deposit assets to a private vault. To prevent Vault Owner from locking away depositor funds, any shareholder can withdraw funds. Furthermore, the Vault Owner has an implicit permission to deposit and withdraw assets to and from the Vault. I.e. they do not have to have credentials in the Permissioned Domain.
+A Single Asset Vault can be either public or private. Any depositor can deposit and redeem liquidity from a public vault, provided they own sufficient shares. In contrast, access to private shares is controlled via [Permissioned Domains](https://github.com/XRPLF/XRPL-Standards/discussions/228), which use on-chain [Credentials](https://github.com/XRPLF/XRPL-Standards/tree/master/XLS-70-credentials) to manage access to the vault. Only depositors with the necessary credentials can deposit assets to a private vault. To prevent Vault Owner from locking away depositor funds, any shareholder can withdraw funds. Furthermore, the Vault Owner has an implicit permission to deposit and withdraw assets to and from the Vault. I.e. they do not have to have credentials in the Permissioned Domain.
 
 #### 1.1.3 Yield Bearing Shares
 
-Shares represent the ownership of a portion of the vault's assets. On-chain shares are represented by a [Multi-Purpose Token](https://github.com/XRPLF/XRPL-Standards/tree/master/XLS-0033-multi-purpose-tokens). When creating the vault, the Vault Owner can configure the shares to be non-transferable. Non-transferable shares cannot be transferred to any other account -- they can only be redeemed. If the vault is private, shares can be transferred and used in other DeFi protocols as long as the receiving account is authorized to hold the shares. The vault's shares may be yield-bearing, depending on the protocol connected to the vault, meaning that a holder may be able to withdraw more (or less) liquidity than they initially deposited.
+Shares represent the ownership of a portion of the vault's assets. On-chain shares are represented by a [Multi-Purpose Token](https://github.com/XRPLF/XRPL-Standards/tree/master/XLS-33-multi-purpose-tokens). When creating the vault, the Vault Owner can configure the shares to be non-transferable. Non-transferable shares cannot be transferred to any other account -- they can only be redeemed. If the vault is private, shares can be transferred and used in other DeFi protocols as long as the receiving account is authorized to hold the shares. The vault's shares may be yield-bearing, depending on the protocol connected to the vault, meaning that a holder may be able to withdraw more (or less) liquidity than they initially deposited.
 
 ### 1.2 Terminology
 
 - **Vault**: A ledger entry for aggregating liquidity and providing this liquidity to one or more accessors.
-- **Asset**: The currency of a vault. It is either XRP, a [Fungible Token](https://xrpl.org/docs/concepts/tokens/fungible-tokens/) or a [Multi-Purpose Token](https://github.com/XRPLF/XRPL-Standards/tree/master/XLS-0033-multi-purpose-tokens).
-- **Share**: Shares represent the depositors' portion of the vault's assets. Shares are a [Multi-Purpose Token](https://github.com/XRPLF/XRPL-Standards/tree/master/XLS-0033-multi-purpose-tokens) created by the _pseudo-account_ of the vault.
+- **Asset**: The currency of a vault. It is either XRP, a [Fungible Token](https://xrpl.org/docs/concepts/tokens/fungible-tokens/) or a [Multi-Purpose Token](https://github.com/XRPLF/XRPL-Standards/tree/master/XLS-33-multi-purpose-tokens).
+- **Share**: Shares represent the depositors' portion of the vault's assets. Shares are a [Multi-Purpose Token](https://github.com/XRPLF/XRPL-Standards/tree/master/XLS-33-multi-purpose-tokens) created by the _pseudo-account_ of the vault.
 
 ### 1.3 Actors
 
@@ -161,7 +161,7 @@ The `Vault` object costs one reserve fee per object created:
 
 #### 2.1.6 Vault Shares
 
-Shares represent the portion of the Vault assets a depositor owns. Vault Owners set the currency code of the share and whether the token is transferable during the vault's creation. These two values are immutable. The share is represented by a [Multi-Purpose Token](https://github.com/XRPLF/XRPL-Standards/tree/master/XLS-0033-multi-purpose-tokens). The MPT is issued by the vault's pseudo-account.
+Shares represent the portion of the Vault assets a depositor owns. Vault Owners set the currency code of the share and whether the token is transferable during the vault's creation. These two values are immutable. The share is represented by a [Multi-Purpose Token](https://github.com/XRPLF/XRPL-Standards/tree/master/XLS-33-multi-purpose-tokens). The MPT is issued by the vault's pseudo-account.
 
 ##### 2.1.6.1 `MPTokenIssuance`
 
@@ -193,7 +193,7 @@ The `MPToken` object represents the amount of shares held by a depositor. It is
 
 ###### 2.1.6.2.1 `MPToken` Values
 
-The `MPToken` values should be set as per the `MPT` [specification](https://github.com/XRPLF/XRPL-Standards/tree/master/XLS-0033-multi-purpose-tokens#2112-fields).
+The `MPToken` values should be set as per the `MPT` [specification](https://github.com/XRPLF/XRPL-Standards/tree/master/XLS-33-multi-purpose-tokens#2112-fields).
 
 | **Condition**     | **Transferable**   | **Non-Transferable** |
 | ----------------- | ------------------ | -------------------- |
@@ -291,7 +291,7 @@ The First Come, First Serve strategy treats all requests equally, allowing a dep
 
 #### 2.1.8 Frozen Assets
 
-The issuer of the Vaults asset may enact a freeze either through a [Global Freeze](https://xrpl.org/docs/concepts/tokens/fungible-tokens/freezes/#global-freeze) for IOUs or [locking MPT](https://github.com/XRPLF/XRPL-Standards/tree/master/XLS-0033-multi-purpose-tokens#21122-flags). When the vaults asset is frozen, it can only be withdrawn by specifying the `Destination` account as the `Issuer` of the asset. Similarly, a frozen asset _may not_ be deposited into a vault. Furthermore, when the asset of a vault is frozen, the shares corresponding to the asset may not be transferred.
+The issuer of the Vaults asset may enact a freeze either through a [Global Freeze](https://xrpl.org/docs/concepts/tokens/fungible-tokens/freezes/#global-freeze) for IOUs or [locking MPT](https://github.com/XRPLF/XRPL-Standards/tree/master/XLS-33-multi-purpose-tokens#21122-flags). When the vaults asset is frozen, it can only be withdrawn by specifying the `Destination` account as the `Issuer` of the asset. Similarly, a frozen asset _may not_ be deposited into a vault. Furthermore, when the asset of a vault is frozen, the shares corresponding to the asset may not be transferred.
 
 #### 2.1.9 Transfer Fees
 
diff --git a/XLS-69-simulate/README.md b/XLS-69-simulate/README.md
@@ -1,5 +1,5 @@
 <pre>
-xls: 0069
+xls: 69
 title: Simulating Transaction Execution
 description: A new API method for executing dry runs of transactions without submitting them to the network
 author: Mayukha Vadari, Ripple <mvadari@ripple.com>, Elliot Lee, Ripple <xrpl-standards-draft@ripple.com>
diff --git a/XLS-7-deletable-accounts/README.md b/XLS-7-deletable-accounts/README.md
@@ -1,5 +1,5 @@
 <pre>
-xls: 0007
+xls: 7
 title: Deletable Accounts on the XRP Ledger
 description: A feature for completely removing accounts from the ledger and recovering the reserve from those accounts
 author: Scott Schurr, Ripple <scott@ripple.com>, Nik Bougalis <nikb@bougalis.net>
diff --git a/XLS-70-credentials/README.md b/XLS-70-credentials/README.md
@@ -1,5 +1,5 @@
 <pre>
-xls: 0070
+xls: 70
 title: On-Chain Credentials
 description: Issuance, storage, and verification of credentials directly on the XRP Ledger while supporting privacy needs
 author: Mayukha Vadari, Ripple <mvadari@ripple.com>
@@ -13,7 +13,7 @@ created: 2021-01-01
 
 ## Abstract
 
-The XRPL DID (Digital Identifier) amendment ([XLS-40](https://github.com/XRPLF/XRPL-Standards/tree/master/XLS-0040d-decentralized-identity)) empowers users to manage their digital identities on the XRP Ledger. While this amendment adds support for on-chain identity management and simplifies off-chain credential usage, maximizing blockchain technology's full potential for credential handling requires on-chain solutions.
+The XRPL DID (Digital Identifier) amendment ([XLS-40](https://github.com/XRPLF/XRPL-Standards/tree/master/XLS-40-decentralized-identity)) empowers users to manage their digital identities on the XRP Ledger. While this amendment adds support for on-chain identity management and simplifies off-chain credential usage, maximizing blockchain technology's full potential for credential handling requires on-chain solutions.
 
 This document proposes a design to bridge this gap. It outlines the issuance, storage, and verification of credentials directly on the XRP Ledger, while still supporting the privacy needs of users.
 
diff --git a/XLS-73-amm-clawback/README.md b/XLS-73-amm-clawback/README.md
@@ -1,5 +1,5 @@
 <pre>
-xls: 0073
+xls: 73
 title: AMMClawback
 description: Amendment to enable token issuers to claw back tokens from AMM pools for regulatory compliance
 author: Shawn Xie, Ripple <shawnxie@ripple.com>, Yinyi Qian, Ripple <yqian@ripple.com>
diff --git a/XLS-74-account-permissions/README.md b/XLS-74-account-permissions/README.md
@@ -1,5 +1,5 @@
 <pre>
-xls: 0074
+xls: 74
 title: Account Permissions
 description: Formalization of different types of transaction-based account permissions for subset capabilities
 author: Mayukha Vadari, Ripple <mvadari@ripple.com>
diff --git a/XLS-75-permission-delegation/README.md b/XLS-75-permission-delegation/README.md
@@ -1,5 +1,5 @@
 <pre>
-xls: 0075
+xls: 75
 title: Permission Delegation
 description: Authorization delegation mechanism to enhance flexibility and usability of XRPL accounts
 author: Mayukha Vadari, Ripple <mvadari@ripple.com>, Yinyi Qian, Ripple <yqian@ripple.com>, Ed Hennis, Ripple <ed@ripple.com>
diff --git a/XLS-77-deep-freeze/README.md b/XLS-77-deep-freeze/README.md
@@ -1,5 +1,5 @@
 <pre>
-xls: 0077
+xls: 77
 title: Deep-freeze
 description: Enhancement to prevent token misuse by frozen account holders and improve regulatory compliance
 author: Shawn Xie, Ripple <shawnxie@ripple.com>
diff --git a/XLS-78-subscriptions/README.md b/XLS-78-subscriptions/README.md
@@ -1,5 +1,5 @@
 <pre>
-xls: 0078d
+xls: 78
 title: XLS-78d Subscriptions
 description: A subscription mechanism for recurring payments on the XRP Ledger
 author: Chris Dangerfield <xrpl365@gmail.com>, Denis Angell <dangell@transia.co>
diff --git a/XLS-80-permissioned-domains/README.md b/XLS-80-permissioned-domains/README.md
@@ -1,5 +1,5 @@
 <pre>
-xls: 0080
+xls: 80
 title: Permissioned Domains
 description: Creation of controlled environments with specific rules and restrictions to bridge decentralized blockchain and regulatory requirements
 author: Mayukha Vadari, Ripple <mvadari@ripple.com>
diff --git a/XLS-81-permissioned-dex/README.md b/XLS-81-permissioned-dex/README.md
@@ -1,5 +1,5 @@
 <pre>
-xls: 0081
+xls: 81
 title: Permissioned DEXes
 description: A permissioned DEX system for the XRPL to enable regulated financial institutions to participate while adhering to compliance requirements
 author: Mayukha Vadari, Ripple <mvadari@ripple.com>, Shawn Xie, Ripple <shawnxie@ripple.com>
@@ -20,7 +20,7 @@ This proposal introduces a permissioned DEX system for the XRPL. By integrating
 
 ## 1. Overview
 
-This proposal builds on top of [XLS-80d, Permissioned Domains](https://github.com/XRPLF/XRPL-Standards/tree/master/XLS-0080d-permissioned-domains), as Permissioned Domains are needed to handle the permissioning aspect.
+This proposal builds on top of [XLS-80, Permissioned Domains](https://github.com/XRPLF/XRPL-Standards/tree/master/XLS-80-permissioned-domains), as Permissioned Domains are needed to handle the permissioning aspect.
 
 We propose:
 
@@ -591,7 +591,7 @@ No open offer will be filled by a permissioned offer.
 
 ## 13. Security
 
-The trust assumptions are the same as with [permissioned domains](https://github.com/XRPLF/XRPL-Standards/tree/master/XLS-0080-permissioned-domains#7-security).
+The trust assumptions are the same as with [permissioned domains](https://github.com/XRPLF/XRPL-Standards/tree/master/XLS-80-permissioned-domains#7-security).
 
 # Appendix
 
diff --git a/XLS-85-token-escrow/README.md b/XLS-85-token-escrow/README.md
@@ -1,5 +1,5 @@
 <pre>
-xls: 0085
+xls: 85
 title: Token-Enabled Escrows
 description: Enhancement to existing Escrow functionality to support both Trustline-based tokens (IOUs) and Multi-Purpose Tokens (MPTs)
 author: Denis Angell, XRPL-Labs (@dangell7)
diff --git a/XLS-89-multi-purpose-token-metadata-schema/README.md b/XLS-89-multi-purpose-token-metadata-schema/README.md
