Update resize language (#388)

src/components/products/tokenMetadata/index.js

@@ -20,15 +20,6 @@ export const tokenMetadata = {
     {
       ...documentationSection('token-metadata'),
       navigation: [
-        {
-          title: 'Breaking Change!',
-          links: [
-            {
-              title: 'Account Size Reduction',
-              href: '/token-metadata/guides/account-size-reduction',
-            },
-          ],
-        },
         {
           title: 'Introduction',
           links: [
@@ -38,6 +29,10 @@ export const tokenMetadata = {
               href: '/token-metadata/getting-started',
             },
             { title: 'FAQ', href: '/token-metadata/faq' },
+            {
+              title: 'Account Size Reduction',
+              href: '/token-metadata/guides/account-size-reduction',
+            },
           ],
         },
         {

src/pages/token-metadata/guides/account-size-reduction.md

@@ -4,43 +4,33 @@ metaTitle: Token Metadata Account Size Reduction | Token Metadata Guides
 description: Learn about the impacts of the TM Account Size reduction.
 ---
 
-On 10th of October 2024 a Metaplex Token Metadata program change was deployed to mainnet that reduces the size of all new metadata accounts created. Subsequently on October 25th, Metaplex introduced a new Resize instruction that enables existing metadata accounts to be resized. If your product fetches any metadata from TM, this change might affect you. Make sure to read below and implement any necessary changes so things don't break!
+On 10th of October 2024, a Metaplex Token Metadata (TM) program change was deployed to mainnet that reduces the size of all new metadata accounts created. Subsequently on October 25th, Metaplex introduced a new Resize instruction that enables existing metadata accounts to be resized. If your product fetches any metadata from TM, this change might affect you.
 
 ## What does it mean to "resize" an asset?
 
 Resizing an NFT enables the release of excess SOL not previously accessible without fully closing (aka burning) the Token Metadata (TM) accounts.
 
-Resize does not impact your NFT's functionality, they are simply optimized to free up space on the Solana network. Users will receive the excess SOL from EACH NFT that they Resize.
+Resize does not impact your NFT's functionality, they are simply optimized to free up space on the Solana network.
 
 However, as stated in the Developer FAQ, programs using SDK versions dating back to August and October 2023 will need to update to handle the smaller Token Metadata accounts.
 
-## How many NFTs are eligible to be resized and how much SOL can I claim?
+## How many NFT accounts have been resized and how much SOL can I claim?
 
-There are 23.2M NFTs that are eligible to be resized (as of March 4th). 0.0023 excess SOL can be claimed per Master Edition and 0.0019 excess SOL can be claimed per Edition.
+As of August 15, 2025, all TM NFT metadata accounts have been resized.
 
-## Why should I Resize?
+Holders of TM NFTs that had not already been resized at the time of the final optimization can claim 100% of the excess SOL attributed to their NFTs’ storage accounts at [resize.metaplex.com](https://resize.metaplex.com). The claimable amounts include: 0.0023 excess SOL per Master Edition and 0.0019 excess SOL per Edition.
 
-The update reduces metadata account sizes, lowering the data storage cost, while making Solana lighter & more cost-efficient.
-
-There is ~15GB of state taken up with unused Token Metadata buffer space, which is an added tax on those who maintain and power the network. This optimization is an important step in benefitting every Solana user and the validator infrastructure the network depends on.
-
-## Where can I resize my NFT?
-
-You can use our free UI at [resize.metaplex.com](https://resize.metaplex.com) to resize your eligible assets until the resize window closes. The resize window will remain open until the DAO decides on any pending proposals for how to handle the remaining excess SOL.
+## What are the benefits of Resizing?
 
-Community builders such as [SolRip](https://solrip.io/) (free to use) and [Sol Incinerator](https://sol-incinerator.com/) (fee of 5% of the Resize amount) have created alternative tools to process the Resize instruction.
-
-## If I Resize my NFT now, can I still burn the NFT later and claim the excess SOL?
-
-Yes, Resizing the NFT now and burning the NFT later would enable NFT holders to receive the same amount of SOL as if they closed all of the Token Metadata accounts today.
+The update reduces metadata account sizes, lowering the data storage cost, while making Solana lighter & more cost-efficient.
 
-## Why does the Resize window have an end date? Why will the remaining excess SOL no longer needed for rent be transferred to the Metaplex DAO?
+The optimization saved a total of 7,380 MB of Solana network space, resulting in more efficient validator performance that benefits all Solana users and stakers.
 
-The goal of the Resize initiative is to get as many people to participate which will then improve performance of the Solana network.
+It was an important step in benefitting every Solana user and the validator infrastructure the network depends on.
 
-In order to do this, we've allowed NFT holders to optimize the network directly by adding a Resize instruction which enables the release of excess SOL not previously accessible without fully closing (aka burning) the Token Metadata accounts.
+## Where can I claim excess SOL with my NFTs?
 
-After that point any remaining SOL will be contributed to the Metaplex DAO which is responsible for stewarding the Protocol, at which point the DAO can vote to airdrop the SOL, distribute grants to ecosystem builders, or other initiatives.
+You can use our free UI at [resize.metaplex.com](https://resize.metaplex.com) to claim excess SOL attributed to your NFTs’ storage accounts. Per the Metaplex DAO’s approved MTP-004, the deadline to claim excess SOL is extended until at least Feb. 13th, 2027. This extends the total amount of time for NFT holders to claim excess SOL from the optimization to at least 28 months.
 
 ## Developer FAQ