Rename transitional debug reporting to cookie-based debug reporting (#1528)

Author: linnan-github

AGGREGATE.md

@@ -12,7 +12,7 @@
   - [Attribution trigger registration](#attribution-trigger-registration)
   - [Aggregatable reports](#aggregatable-reports)
     - [Encrypted payload](#encrypted-payload)
-  - [Optional: transitional debugging reports](#optional-transitional-debugging-reports)
+  - [Optional: Cookie-based debugging reports](#optional-cookie-based-debugging-reports)
     - [Attribution-success debugging reports](#attribution-success-debugging-reports)
     - [Verbose debugging reports](#verbose-debugging-reports)
   - [Contribution bounding and budgeting](#contribution-bounding-and-budgeting)
@@ -378,7 +378,7 @@ future versions of the API), the endpoint URL should also change.
 **Note:** The browser may need some mechanism to ensure that the same set of
 keys are delivered to different users.
 
-### Optional: transitional debugging reports
+### Optional: Cookie-based debugging reports
 
 #### Attribution-success debugging reports
 

EVENT.md

@@ -36,7 +36,7 @@ extension on top of this.
     - [Lookback window](#lookback-window)
   - [Optional: Varying frequency and number of reports](#optional-varying-frequency-and-number-of-reports)
     - [Example](#example)
-  - [Optional: transitional debugging reports](#optional-transitional-debugging-reports)
+  - [Optional: Cookie-based debugging reports](#optional-cookie-based-debugging-reports)
     - [Attribution-success debugging reports](#attribution-success-debugging-reports)
     - [Verbose debugging reports](#verbose-debugging-reports)
       - [Reporting endpoints](#reporting-endpoints)
@@ -715,11 +715,11 @@ This example configuration supports optimizing for receiving reports at earlier
 }
 ```
 
-### Optional: transitional debugging reports
+### Optional: Cookie-based debugging reports
 
 The Attribution Reporting API is a new and fairly complex way to do attribution
 measurement without third-party cookies. As such, we are open to introducing a
-transitional mechanism to learn more information about attribution reports
+mechanism to learn more information about attribution reports
 _while third-party cookies are available_. This ensures that the API can be
 fully understood during roll-out and help flush out any bugs (either in browser
 or caller code), and more easily compare the performance to cookie-based

aggregate_debug_reporting.md

@@ -29,13 +29,13 @@
 
 ## Introduction
 
-The [transitional debugging reports](https://github.com/WICG/attribution-reporting-api/blob/main/EVENT.md#optional-transitional-debugging-reports),
+The [cookie-based debugging reports](https://github.com/WICG/attribution-reporting-api/blob/main/EVENT.md#optional-cookie-based-debugging-reports),
 which are currently supported by the Attribution Reporting API to facilitate
-testing, will be deprecated alongside third-party cookie deprecation.
+testing, are only permitted while third-party cookies are available.
 
 Here we propose the aggregate debug reporting framework to allow developers to
-measure the performance of the Attribution Reporting API post third-party
-cookie deprecation. The aggregate debug reporting utilizes the mechanism
+measure the performance of the Attribution Reporting API while third-party
+cookies are unavailable. The aggregate debug reporting utilizes the mechanism
 introduced in the [Aggregate Attribution Reporting](https://github.com/WICG/attribution-reporting-api/blob/main/AGGREGATE.md)
 to report debug data in aggregate. To prevent leakage, the cross-site data in
 the aggregatable reports would be encrypted to ensure it can only be processed

verbose_debugging_reports.md

@@ -292,7 +292,7 @@ The trigger was rejected due to an internal error.
 [attribution source registrations]: https://github.com/WICG/attribution-reporting-api/blob/main/EVENT.md#registering-attribution-sources
 [attribution trigger registrations]: https://github.com/WICG/attribution-reporting-api/blob/main/EVENT.md#triggering-attribution
 [channel-capacity limit]: https://wicg.github.io/attribution-reporting-api/#max-event-level-channel-capacity-per-source
-[cookie-based debugging]: https://github.com/WICG/attribution-reporting-api/blob/main/EVENT.md#optional-transitional-debugging-reports
+[cookie-based debugging]: https://github.com/WICG/attribution-reporting-api/blob/main/EVENT.md#optional-cookie-based-debugging-reports
 [destination limit]: https://github.com/WICG/attribution-reporting-api/blob/main/EVENT.md#limiting-the-number-of-unique-destinations-covered-by-unexpired-sources
 [destinations per source and reporting site per day rate limit]: https://github.com/WICG/attribution-reporting-api/blob/main/EVENT.md#limiting-the-number-of-unique-destinations-covered-by-unexpired-sources
 [destinations per source and reporting site rate limit]: https://github.com/WICG/attribution-reporting-api/blob/main/EVENT.md#limiting-the-number-of-unique-destinations-per-source-site