diff --git a/content/ADR-245-player-components.md b/content/ADR-245-player-components.md
index 7f31158b..86ad1d7a 100644
--- a/content/ADR-245-player-components.md
+++ b/content/ADR-245-player-components.md
@@ -26,7 +26,7 @@ The proposal consists of the following key points:
 - Reserving Entities: Entities numbered 32 to 256 will be reserved for storing player data components. This reservation ensures that sufficient entities are available to accommodate player data. When a player disconnects from the room, the entity MUST be deleted, and a new generation for the entity number will be used. This ensures a session of up to 14.680.064 unique players.
 - Player Data Components: A new set of player data components will be introduced, containing essential information about the player, such as position(Transform), wearables, identity, base avatar properties, and emote commands. 
 - Scene Inclusion: Every scene in SDK7 MUST receive player data components. This inclusion ensures that each scene has access to real-time player data, which is vital for smooth interactions and gameplay experiences.
-- Transform Updates: Only active and global scenes will receive real-time transform updates to optimize data updates and reduce overhead. If the Transform is not set in a Scene, it is out of the scene.
+- Transform Updates: active parcel scenes (the one where each player is) and global scenes MUST receive real-time players `Transform` updates. Non-active parcel scenes MAY have no `Transform` of the player outside of them. Exception: the primary player `Transform` MUST be present in all scenes.
 
 # Player Data Components