diff --git a/Fenced_Frames_Ads_Reporting.md b/Fenced_Frames_Ads_Reporting.md
index 61f1d2aff..0b3990144 100644
--- a/Fenced_Frames_Ads_Reporting.md
+++ b/Fenced_Frames_Ads_Reporting.md
@@ -129,7 +129,7 @@ In this example, the destination eTLD+1 is "adtech.example". [The Privacy Sandbo
 
 ## registerAdBeacon
 
-A similar API was initially discussed here: https://github.com/WICG/turtledove/issues/99 for reporting clicks. The idea is that the buyer and seller side worklets are able to register a URL with the browser in their reportWin and reportResult APIs. The registered URL's site (scheme, eTLD+1) is required to be attested for Protected Audience API. Please see [the Privacy Sandbox enrollment attestation model](https://github.com/privacysandbox/attestation#the-privacy-sandbox-enrollment-attestation-model). If the URL is attested for Protected Audience API, a beacon will be sent to the registered URL when events are reported by the fenced frame via reportEvent. Otherwise the beacon will not be sent. In the case of redirect, the redirected site is not checked for enrollment and attestation since the browser doesn't add any data directly to the redirect URL.  The initial reporting destination site is responsible for acting in accordance with its attestation if it decides to share any data via the redirect.
+A similar API was initially discussed here: https://github.com/WICG/turtledove/issues/99 for reporting clicks. The idea is that the buyer and seller side worklets are able to register a URL with the browser in their reportWin and reportResult APIs. The registered URL's site (scheme, eTLD+1) is required to be attested for Protected Audience API. Please see [the Privacy Sandbox enrollment attestation model](https://github.com/privacysandbox/attestation#the-privacy-sandbox-enrollment-attestation-model). If destination is attested for Protected Audience API, a beacon will be sent to the registered URL when events are reported by the fenced frame via reportEvent. Otherwise the beacon will not be sent. In the case of redirect, the redirected destination is not checked for enrollment and attestation since the browser doesn't add any data directly to the redirect URL. The initial reporting destination is responsible for acting in accordance with its attestation if it decides to share any data via the redirect.
 
 
 ### Parameters