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

jessiemongeon1 · web-flow · commit 7fd871b729c3 · 2026-03-09T12:19:07.000-05:00
## 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:
diff --git a/docs/content/standards/display-v2-migration.mdx b/docs/content/standards/display-v2-migration.mdx
@@ -61,4 +61,4 @@ The capability can be claimed in either of two ways:
 
 - **Legacy Display** using `claim`: Use this if you hold the V1 `Display<T>` object. Pass it in; it is consumed and you receive the `DisplayCap<T>`.
 
-Once claimed, the holder of `DisplayCap<T>` can update the display fields (`set`, `unset`, `clear`). `delete_legacy` is permissionless as long as the V2 cap has been claimed. Anyone who holds a V1 `Display<T>` can call `delete_legacy(display, legacy)` to burn their legacy object, no need to be the cap holder.
+Once claimed, the holder of `DisplayCap<T>` can update the display fields (`set`, `unset`, `clear`). Anyone who holds a V1 `Display<T>` can call `delete_legacy(display, legacy)` to burn their legacy object.

Original file line number	Diff line number	Diff line change
`@@ -61,4 +61,4 @@ The capability can be claimed in either of two ways:`
`61`	`61`
`62`	`62`	- Legacy Display using `claim`: Use this if you hold the V1 `Display<T>` object. Pass it in; it is consumed and you receive the `DisplayCap<T>`.
`63`	`63`
`64`		-Once claimed, the holder of `DisplayCap<T>` can update the display fields (`set`, `unset`, `clear`). `delete_legacy` is permissionless as long as the V2 cap has been claimed. Anyone who holds a V1 `Display<T>` can call `delete_legacy(display, legacy)` to burn their legacy object, no need to be the cap holder.
	`64`	+Once claimed, the holder of `DisplayCap<T>` can update the display fields (`set`, `unset`, `clear`). Anyone who holds a V1 `Display<T>` can call `delete_legacy(display, legacy)` to burn their legacy object.