diff --git a/Getting-Started.md b/Getting-Started.md
index 28d7c3a4..f7dd68f9 100644
--- a/Getting-Started.md
+++ b/Getting-Started.md
@@ -128,7 +128,7 @@ Answer: A key component to the technical checks that run upon submission is the
### Q. What if I would like to modify or delete my RWS?
Answer:
-To modify an RWS that you own, simply submit a Pull Request that makes the changes you wish to make to your set, and ensure that the `/.well-known/related-website-set.json` endpoint for your set's primary reflects these changes, as do the `/.well-known/related-website-set.json` endpoints of any sites changed within your subsets. To remove a set entirely from the canonical RWS list, you must change the `/.well-known/related-website-set.json` endpoint for your set's primary so that it serves a `404(Not Found)` status code, then submit a pull request that removes your RWS set from the list.
+To modify an RWS that you own, simply submit a Pull Request that makes the changes you wish to make to your set, and ensure that the `/.well-known/related-website-set.json` endpoint for your set's primary reflects these changes, as do the `/.well-known/related-website-set.json` endpoints of any sites changed within your subsets. To remove a set entirely from the [canonical RWS list](https://github.com/googlechrome/first-party-sets/blob/main/related_website_sets.JSON) you must change the `/.well-known/related-website-set.json` endpoint for your set's primary so that it serves a `404 (Not Found)` status code, then submit a pull request that removes your RWS set from the list.
### Q. Can I make pull requests against files other than related_website_sets.JSON (e.g., the Submission Guidelines or the technical checks)?
diff --git a/RWS-Submission_Guidelines.md b/RWS-Submission_Guidelines.md
index 5d78fba8..f25a034d 100644
--- a/RWS-Submission_Guidelines.md
+++ b/RWS-Submission_Guidelines.md
@@ -143,7 +143,7 @@ Upon submission of a PR, a series of technical checks will run on GitHub to veri
The /.well-known/ metadata requirement demonstrates that the submitter has administrative access to the domains present in the set, since administrative access is required to modify the /.well-known/ file. This will help prevent unauthorized actors from adding domains to a set.
The primary domain must serve a JSON file at /.well-known/related-website-set.json (Note: list entries merged before September 15th 2023 may serve their well-known file at /.well-known/related-website-set.json instead; however, any changes to those entries will require that the primary and all members of the set must be served at /.well-known/related-website-set.json like any other entry). The contents of the file must be identical to the submission. Each member domain must serve a JSON file at /.well-known/related-website-set.json. The contents of the file must name the primary domain. These files must be maintained for the duration of the domain’s inclusion in the set.
Any changes to an existing RWS in the canonical RWS list must also be reflected in that set's JSON files at /.well-known/related-website-set.json.
- If an RWS owner wishes to remove a set entirely from the canonical RWS list, then that set's primary must serve a `404(Not Found)` status code at their /.well-known/related-website-set.json endpoint to demonstrate a deliberate desire to remove the set.
+ If an RWS owner wishes to remove a set entirely from the canonical RWS list, then that set's primary must serve a `404 (Not Found)` status code at their /.well-known/related-website-set.json endpoint to demonstrate a deliberate desire to remove the set.
Example for primary.com/.well-known/related-website-set.json: