docs: Update display-v2-migration.mdx (#25769)

## Description 

Describe the changes or additions included in this PR.

## Test plan 

How did you test the new or updated feature?

---

## Release notes

Check each box that your changes affect. If none of the boxes relate to
your changes, release notes aren't required.

For each box you select, include information after the relevant heading
that describes the impact of your changes that a user might notice and
any actions they must take to implement updates.

- [ ] Protocol: 
- [ ] Nodes (Validators and Full nodes): 
- [ ] gRPC:
- [ ] JSON-RPC: 
- [ ] GraphQL: 
- [ ] CLI: 
- [ ] Rust SDK:
- [ ] Indexing Framework:

Author: jessiemongeon1

docs/content/standards/display-v2-migration.mdx

@@ -8,6 +8,8 @@ keywords: [ Object Display, object, display, display properties, object properti
 
 Object Display V2 will be available in Sui v1.68. You can check the [release schedule](https://www.sui.io/networkinfo) to learn more about when v1.68 is available on Devnet, Testnet, and Mainnet. 
 
+All existing V1 displays will be migrated to V2 in a **system snapshot migration**. You don't need to do anything upfront; after the snapshot, you can claim the capability when you're ready (see [Migration and claiming](#migration-and-claiming)).
+
 :::
 
 ## V1 end of life 
@@ -47,12 +49,6 @@ In Object Display V1, you could have `N` displays per type and had to use events
 
 ## Migration and claiming
 
-:::caution 
-
-All existing V1 displays will be migrated to V2 in a **system snapshot migration**. You don't need to do anything upfront; after the snapshot, you can claim the capability when you're ready (see [Migration and claiming](#migration-and-claiming)).
-
-:::
-
 All V1 displays will be migrated to V2 in a system snapshot migration. After that, for each type the single V2 `Display<T>` exists with `cap_id: none` until the capability is claimed.
 
 The capability can be claimed in either of two ways: