diff --git a/docs/verus_migration/player_joining.md b/docs/verus_migration/player_joining.md
index 51073d86..809df90f 100644
--- a/docs/verus_migration/player_joining.md
+++ b/docs/verus_migration/player_joining.md
@@ -93,7 +93,7 @@ There are couple of ways using which players can find the tables registered on t
 ------------------------
 Off all the ID's we have table ID is the very complex ID and this is where all the game info goes into. The complete map of contents that goes into the table is not yet fully identified and as the development of the game progresses I'll update the details of table ID contentmultimap here. 
 
-Since the table ID is the only place where all the game information is held, its natural that all the entities involved in the game must make updates to this ID. So players, dealers, and cashiers/bvv make updates to the table ID during the game on their turn. The crucial actions in the game like deck shuffling, game play and game settlement are done based on the information held by table ID. Every action that takes place during the game requires different kind of data, so due to which we grouped the information under table ID contentmultimap using the following keys:
+Since the table ID is the only place where all the game information is held, its natural that all the entities involved in the game must make updates to this ID. So players, dealers, and cashiers/bvv make updates to the table ID during the game on their turn. The crucial actions in the game like deck shuffling, game play and game settlement are done based on the information held by table ID. Every action that takes place during the game requires different kind of data, so due to which we grouped the information under table ID contentmultimap using the following keys and in detailed information about the below table keys are mentioned in [All about ID's and Keys](./ids_keys_data.md#table-id)
 ```
 - T_GAME_ID_KEY "chips.vrsc::poker.t_game_ids"
 - T_TABLE_INFO_KEY "chips.vrsc::poker.t_table_info"