Clarify source debug data types that are not reported implicitly for …

…verbose debug reports (WICG#1325)

Co-authored-by: Andrew Paseltiner <[email protected]>

index.bs

@@ -3056,9 +3056,12 @@ To <dfn>process an attribution source</dfn> given an [=attribution source=] |sou
 Note: Because a fake report does not have a "real" effective destination, we need to subtract from the
 privacy budget of all possible destinations.
 
-Note: The limits that are not reported as <code>[=source debug data type/source-success=]</code> should be
-checked before any limits that are reported implicitly as <code>[=source debug data type/source-success=]</code>
-to prevent side-channel leakage of cross-origin data. Furthermore, the [=verbose debug data=]
+Note: The limits that are not reported as <code>[=source debug data type/source-success=]</code>
+in [=verbose debug reports=] should be checked before any limits that are reported implicitly as
+<code>[=source debug data type/source-success=]</code> (
+<code>[=source debug data type/source-destination-global-rate-limit=]</code> and
+<code>[=source debug data type/source-reporting-origin-limit=]</code>) to
+prevent side-channel leakage of cross-origin data. Furthermore, the [=verbose debug data=]
 should be fully determined regardless of the result of checks on implicitly reported limits.
 
 # Triggering Algorithms # {#trigger-algorithms}