3PCD DT blog update - Clarify matching against the list (#7842)

Author: rowan-m

site/en/blog/third-party-cookie-deprecation-trial/index.md

@@ -57,7 +57,7 @@ Chrome will initially work with [Disconnect.me](https://disconnect.me/), an indu
 
 We will apply the following process for registration requests:
 
-* If the third-party origin matches a known advertising domain, including if the origin matches an entry on the Disconnect [advertising list](https://github.com/disconnectme/disconnect-tracking-protection/blob/master/services.json#L1535C11-L1535C11), then the **registration request will be rejected**. In general, if a domain is considered an advertising domain, subdomains of that domain will also be considered advertising list entries scoped to a particular pathname, however, they will have the pathname removed and matched to the exact origin in the entry.
+* If the third-party origin matches a known advertising domain, including if the origin matches an entry on the Disconnect [advertising list](https://github.com/disconnectme/disconnect-tracking-protection/blob/master/services.json#L1535C11-L1535C11), then the **registration request will be rejected**. In general, entries on the list will match all subdomains below the specified origin.  Some entries, however, include a path element.  These more specific entries will match the given origin, but not subdomains.
 * Steps to reproduce a broken user-facing experience must be provided. In particular, this should be an experience for the user operating the device where the cookie is stored, and not a user performing later analysis of data. If we cannot validate a broken user experience then the **registration request will be rejected**.
 * Otherwise the **registration request will be approved**.
 
@@ -218,4 +218,4 @@ Trial deactivation does not take subdomain matching into account. To deactivate
     * Response times may vary; you are encouraged to begin the registration process as soon as possible to ensure you will be ready ahead of 1% third-party cookie deprecation in early Q1. If you have not received any response within 1-2 weeks of submitting your registration, please contact [3pc-deprecationtrial@google.com](mailto:3pc-deprecationtrial@google.com).
     * Bug thread for open conversation, decision status and rationale.
 7. Our deprecation trial registration has been approved, and we've deployed a trial token as recommended. However, the deprecation trial isn't working as expected. What should we do?
-    * [Troubleshoot Chrome origin trials](https://goo.gle/ot-ts) provides a checklist for troubleshooting origin trials. In particular, for this deprecation trial, make sure you have registered for the correct origin, opted for a third-party token if necessary, and correctly provided the token via an HTTP header, meta tag or (for a third-party token) using JavaScript. You can learn more about third-party origin trials at [Third-party origin trials](https://goo.gle/ot-3p), and there is a deprecation trial demo at [Chrome origin trial demo: Token injected by third-party script](https://ot-3p.glitch.me). If you continue to experience problems, contact [origin-trials-support@google.com](mailto:origin-trials-support@google.com).
+    * [Troubleshoot Chrome origin trials](https://goo.gle/ot-ts) provides a checklist for troubleshooting origin trials. In particular, for this deprecation trial, make sure you have registered for the correct origin, opted for a third-party token if necessary, and correctly provided the token via an HTTP header, meta tag or (for a third-party token) using JavaScript. You can learn more about third-party origin trials at [Third-party origin trials](https://goo.gle/ot-3p), and there is a deprecation trial demo at [Chrome origin trial demo: Token injected by third-party script](https://ot-3p.glitch.me). If you continue to experience problems, contact [origin-trials-support@google.com](mailto:origin-trials-support@google.com).