update

neps/nep-0568.md

@@ -157,14 +157,13 @@ Once a node stops tracking all children and descendants of a shard, the entry fo
 This mapping strategy enables efficient shard management during resharding events,
 supporting smooth transitions without altering storage structures directly.
 
-#### Integration with Cold Storage
+#### Integration with cold storage (archival nodes)
 Cold storage uses the same mapping strategy to manage shard state during resharding:
-
 * When state data is migrated from hot to cold storage, it retains the parent shard’s `ShardUId` prefix, ensuring consistency with the mapping strategy.
-* During the final block of the epoch where resharding occurs, the `DBCol::StateShardUIdMapping` column is copied into cold storage. This ensures that mappings are updated alongside the shard state data.
+* While copying data for the final block of the epoch where resharding occured, the `DBCol::StateShardUIdMapping` column is copied into cold storage. This ensures that mappings are updated alongside the shard state data.
 * These mappings are permanent in cold storage, aligning with its role in preserving historical state.
 
-This approach minimizes complexity while maintaining consistency across hot and cold storage during and after resharding.
+This approach minimizes complexity while maintaining consistency across hot and cold storage.
 
 ### Stateless Validation