diff --git a/site/en/blog/related-website-sets/index.md b/site/en/blog/related-website-sets/index.md
index 0155e24d4f8a..386508ff3cba 100644
--- a/site/en/blog/related-website-sets/index.md
+++ b/site/en/blog/related-website-sets/index.md
@@ -28,7 +28,7 @@ RWS is designed to minimize disruptions to specific user-facing features once Ch
 
 Chrome previously proposed a numeric limit of three domains for the Associated Subset (plus one primary domain), in alignment with our objective to prevent widespread tracking abuse. We have heard feedback from web standards participants that the limit was too low for different types of use cases. 
 
-We have decided to increase the associated domain limit to five domains (plus one primary domain) which best matches the most comparable implementation offered by another major browser (See [ref 4](#ref-4)). This will take effect beginning in Chrome 117.
+We have decided to increase the associated domain limit to five domains (plus one primary domain) which best matches the most comparable implementation offered by another major browser (See [ref 4](#ref-4)). This approach also aligns with user research findings that suggested users would be comfortable with lower numbers. This will take effect beginning in Chrome 117.
 
 Since RWS is not intended as an ads solution, we are not taking into consideration feedback on how to improve RWS to better serve ads use cases. For ads use cases, developers should explore using the Topics, Protected Audience, and Attribution Reporting APIs and provide feedback on them accordingly. 
 
@@ -40,7 +40,7 @@ For user-impacting experiences that are not supported by this limit, Chrome is [
 
 ## Next steps
 
-We're grateful for the ecosystem feedback that has helped shape the API so far. We have invested in RWS as a method of providing developers predictability, control, and agency in preserving the end user experience of the websites they build. We are excited to see how developers adopt and use RWS as we ramp up. The [submission process](https://github.com/GoogleChrome/first-party-sets/blob/main/FPS-Submission_Guidelines.md) is currently live, and the [RWS JSON generator tool](https://goo.gle/rws-json-generator) is a great starting point to help with submissions.
+We're grateful for the ecosystem feedback that has helped shape the API so far. We have invested in RWS as a method of providing developers predictability, control, and agency in preserving the end user experience of the websites they build. We are excited to see how developers adopt and use RWS as we ramp up. The [submission process](https://github.com/GoogleChrome/related-website-sets/blob/main/RWS-Submission_Guidelines.md) is currently live, and the [RWS JSON generator tool](https://goo.gle/rws-json-generator) is a great starting point to help with submissions.
 
 Follow the [Intent to Ship thread](https://groups.google.com/a/chromium.org/g/blink-dev/c/7_6JDIfE1as/m/wModmpcaAgAJ) to track progress, and check out [these materials](/docs/privacy-sandbox/first-party-sets-integration/) for implementation guidance.