[Related Website Sets] Delete RWS guide

Add links to official Chrome document, where appropriate.

Author: bershanskiy

files/en-us/_redirects.txt

@@ -10421,6 +10421,7 @@
 /en-US/docs/Web/API/StorageQuota/queryInfo	/en-US/docs/Web/API/StorageManager
 /en-US/docs/Web/API/StorageQuota/requestPersistentQuota	/en-US/docs/Web/API/StorageManager
 /en-US/docs/Web/API/StorageQuota/supportedTypes	/en-US/docs/Web/API/StorageManager
+/en-US/docs/Web/API/Storage_Access_API/Related_website_sets	/en-US/docs/Web/API/Storage_Access_API
 /en-US/docs/Web/API/StyleSheet.disabled	/en-US/docs/Web/API/StyleSheet/disabled
 /en-US/docs/Web/API/StyleSheet.href	/en-US/docs/Web/API/StyleSheet/href
 /en-US/docs/Web/API/StyleSheet.media	/en-US/docs/Web/API/StyleSheet/media

files/en-us/mdn/writing_guidelines/page_structures/banners_and_notices/index.md

@@ -74,4 +74,4 @@ It is important to clarify the current standardization status of such features t
 - Adding a "Standards positions" section to the same page as the above banner, as a sub-section of the standard "Specifications" section.
 
 > [!NOTE]
-> See [Related Website Sets](/en-US/docs/Web/API/Storage_Access_API/Related_website_sets) for an example of the "Standards positions" section and what it should contain, as well as the landing page banner.
+> See [Shared Storage API](/en-US/docs/Web/API/Shared_Storage_API) for an example of the "Standards positions" section and what it should contain, as well as the landing page banner.

files/en-us/web/api/document/index.md

@@ -281,7 +281,7 @@ _This interface also inherits from the {{DOMxRef("Node")}} and {{DOMxRef("EventT
 - {{DOMxRef("Document.requestStorageAccess()")}}
   - : Allows a document loaded in a third-party context (i.e., embedded in an {{htmlelement("iframe")}}) to request access to unpartitioned cookies, in cases where user agents by default block access to unpartitioned cookies by sites loaded in a third-party context to improve privacy.
 - {{DOMxRef("Document.requestStorageAccessFor()")}} {{deprecated_inline}} {{non-standard_inline}}
-  - : Allows top-level sites to request third-party cookie access on behalf of embedded content originating from another site in the same [related website set](/en-US/docs/Web/API/Storage_Access_API/Related_website_sets).
+  - : Allows top-level sites to request third-party cookie access on behalf of embedded content originating from another site in the same [related website set](https://privacysandbox.google.com/cookies/related-website-sets-integration).
 - {{domxref("Document.startViewTransition()")}}
   - : Starts a new {{domxref("View Transition API", "view transition", "", "nocode")}} and returns a {{domxref("ViewTransition")}} object to represent it.
 

files/en-us/web/api/document/requeststorageaccessfor/index.md

@@ -11,7 +11,7 @@ browser-compat: api.Document.requestStorageAccessFor
 
 {{APIRef("Storage Access API")}}{{deprecated_header}}{{non-standard_header}}
 
-The **`requestStorageAccessFor()`** method of the {{domxref("Document")}} interface allows top-level sites to request third-party cookie access on behalf of embedded content originating from another site in the same [related website set](/en-US/docs/Web/API/Storage_Access_API/Related_website_sets). It returns a {{jsxref("Promise")}} that resolves if the access was granted, and rejects if access was denied.
+The **`requestStorageAccessFor()`** method of the {{domxref("Document")}} interface allows top-level sites to request third-party cookie access on behalf of embedded content originating from another site in the same [related website set](https://privacysandbox.google.com/cookies/related-website-sets-integration). It returns a {{jsxref("Promise")}} that resolves if the access was granted, and rejects if access was denied.
 
 ## Syntax
 
@@ -43,7 +43,7 @@ A {{jsxref("Promise")}} that fulfills with `undefined` if the access to third-pa
     - The document is not the top-level document.
     - The document has a `null` origin.
     - The supplied `requestedOrigin` is [opaque](https://html.spec.whatwg.org/multipage/browsers.html#concept-origin-opaque).
-    - The top-level and embedded sites are not in the same [related website set](/en-US/docs/Web/API/Storage_Access_API/Related_website_sets).
+    - The top-level and embedded sites are not in the same [related website set](https://privacysandbox.google.com/cookies/related-website-sets-integration).
     - The embedding {{htmlelement("iframe")}} is sandboxed, and the `allow-storage-access-by-user-activation` token is not set.
     - Usage is blocked by a {{httpheader("Permissions-Policy/storage-access", "storage-access")}} [Permissions Policy](/en-US/docs/Web/HTTP/Guides/Permissions_Policy).
     - Usage is denied by the user agent's permission request to use the API.

files/en-us/web/api/storage_access_api/index.md

@@ -67,7 +67,7 @@ Third party content embedded in an {{htmlelement("iframe")}} that needs to acces
    - Safari shows prompts for all embedded content that has not previously received storage access.
    - Firefox only prompts users after an origin has requested storage access on more than a threshold number of sites.
    - Chrome shows prompts for all embedded content that has not previously received storage access.
-     It will however automatically grant access and skip prompts if the embedded content and embedding site are part of the same [related website set](/en-US/docs/Web/API/Storage_Access_API/Related_website_sets).
+     It will however automatically grant access and skip prompts if the embedded content and embedding site are part of the same [related website set](https://privacysandbox.google.com/cookies/related-website-sets-integration).
 
 3. Permission is granted or denied based on whether the content meets all the security requirements — see [Security considerations](#security_considerations) for general requirements, and [Browser-specific variations](#browser-specific_variations) for some browser-specific security requirements.
    The {{jsxref("Promise")}}-based nature of `requestStorageAccess()` allows you to run code to handle success and failure cases.
@@ -311,8 +311,8 @@ Documentation for Firefox's new storage access policy for blocking tracking cook
   - : New name for {{domxref("Document.hasStorageAccess()")}}.
 - {{domxref("Document.requestStorageAccess()")}}
   - : Allows content loaded in a third-party context (i.e., embedded in an {{htmlelement("iframe")}}) to request access to third-party cookies and unpartitioned state; returns a {{jsxref("Promise")}} that resolves if the access was granted, and rejects if access was denied.
-- {{domxref("Document.requestStorageAccessFor()")}} {{experimental_inline}}
-  - : A proposed extension to the Storage Access API that allows top-level sites to request third-party cookie access on behalf of embedded content originating from another site in the same [related website set](/en-US/docs/Web/API/Storage_Access_API/Related_website_sets). Returns a {{jsxref("Promise")}} that resolves if the access was granted, and rejects if access was denied.
+- {{domxref("Document.requestStorageAccessFor()")}} {{deprecated_inline}}
+  - : A non-standard deprecated extension to the Storage Access API that allows top-level sites to request third-party cookie access on behalf of embedded content originating from another site in the same [related website set](https://privacysandbox.google.com/cookies/related-website-sets-integration). Returns a {{jsxref("Promise")}} that resolves if the access was granted, and rejects if access was denied.
 
 > [!NOTE]
 > User interaction propagates to the promise returned by these methods, allowing the callers to take actions requiring user interaction without requiring a second click. For example, a caller could open a pop-up window from the resolved promise without triggering Firefox's pop-up blocker.

files/en-us/web/api/storage_access_api/related_website_sets/index.md

@@ -117,15 +117,15 @@ async function handleCookieAccess() {
 
 ### Related website sets
 
-The Chrome-only [related website sets](/en-US/docs/Web/API/Storage_Access_API/Related_website_sets) feature can be considered a progressive enhancement mechanism that works alongside the Storage Access API — supporting browsers grant default third-party cookie and unpartitioned state access between websites in the same set. This means not having to go through the usual user permission prompt workflow described above, meaning a more user-friendly experience for users of sites in the set.
+The Chrome-only [related website sets](https://privacysandbox.google.com/cookies/related-website-sets-integration) feature can be considered a progressive enhancement mechanism that works alongside the Storage Access API — supporting browsers grant default third-party cookie and unpartitioned state access between websites in the same set. This means not having to go through the usual user permission prompt workflow described above, meaning a more user-friendly experience for users of sites in the set.
 
 ## Requesting storage access from the top-level site on behalf of embedded resources
 
 The Storage Access API features above allow an embedded document to request its own third-party cookie access. There is an additional experimental method available, {{domxref("Document.requestStorageAccessFor()")}}, a proposed extension to the Storage Access API that allows top-level sites to request storage access on behalf of specific related origins.
 
 The `requestStorageAccessFor()` method addresses challenges in adopting the Storage Access API on top-level sites that use cross-site images or scripts requiring cookies. It can enable third-party cookie access for cross-site resources directly embedded into the top-level site that are unable to request their own storage access, for example via {{htmlelement("img")}} or {{htmlelement("script")}} elements.
 
-For `requestStorageAccessFor()` to work, both the calling top-level page and the embedded resource it is requesting storage access for need to be part of the same [related website set](/en-US/docs/Web/API/Storage_Access_API/Related_website_sets).
+For `requestStorageAccessFor()` to work, both the calling top-level page and the embedded resource it is requesting storage access for need to be part of the same [related website set](#related_website_sets).
 
 Typical usage of `requestStorageAccessFor()` looks like this (this time written in regular promise-style rather than async/await):