Update hip-1046.md (#1061)

Signed-off-by: SimiHunjan <simi.hunjan.k@gmail.com>

HIP/hip-1046.md

@@ -7,10 +7,11 @@ requested-by: Hedera
 type: Standards Track
 category: Core
 needs-council-approval: Yes
+discussions-to: https://github.com/hashgraph/hedera-improvement-proposal/discussions/1059
 status: Last Call
 last-call-date-time: 2024-10-29T07:00:00Z
 created: 2024-09-18
-updated: 2024-10-15
+updated: 2024-10-22
 ---
 
 ## Abstract
@@ -140,8 +141,8 @@ new NodeCreateTransaction()
 
 ## Backwards Compatibility
 
-Initially, there should be no change or impact to existing users of the SDKs and gRPC-Web nodes.
-The current set of nodes will remain available at the current addresses. After all SDKs are migrated to use dynamic lookup of the addresses via the mirror node APIs, the existing nodes are expected to remain at the current addresses for some time, but may, eventually, begin to migrate.  Clients using SDKs should adopt the new SDK versions that support dynamic address lookup within this time period.  Clients not using SDKs to access the gRPC-Web nodes should also migrate to look up the node addresses via the mirror node APIs in the same time period.
+Initially, there should be no change or impact to existing users of the browser based SDKs and gRPC-Web nodes.
+The current set of nodes will remain available at the current addresses. After all browser based SDKs are migrated to use dynamic lookup of the addresses via the mirror node APIs, the existing nodes are expected to remain at the current addresses for some time, but may, eventually, begin to migrate.  Clients using browser based SDKs should adopt the new SDK versions that support dynamic address lookup within this time period.  Clients not using SDKs to access the gRPC-Web nodes should also migrate to look up the node addresses via the mirror node APIs in the same time period.
 Any client that chooses to continue using the legacy approach of manually maintaining a fixed static list of gRPC-Web nodes may continue to do so, with the constraint that those entities may need to make more frequent updates to their static lists, but the information for those updates will be available from the mirror node.
 
 ## Security Implications
@@ -154,7 +155,7 @@ actions is extremely low.
 
 ## How to Teach This
 
-Address Book documentation will need to be updated to reflect the new field.  
+Address Book documentation will need to be updated to reflect the new field. This feature has no impact to application developers. For SDK developers who are building an SDK that needs to communicate in browser environment they can use the [mirror node address book API](https://mainnet-public.mirrornode.hedera.com/api/v1/docs/#/network/getNetworkNodes) in their solution to return the endpoints. 
 
 ## Reference Implementation