docs: mention trying major version betas on plugins (typescript-eslint#9502)

JoshuaKGoldberg · web-flow · commit 3119e5b74846 · 2024-07-16T23:09:48.000-04:00
diff --git a/docs/maintenance/Releases.mdx b/docs/maintenance/Releases.mdx
@@ -50,9 +50,11 @@ In parallel to the general PR flow of the major version:
 
 In parallel to the shared config changes work, make sure to test out the beta version on popular community projects willing to try it out.
 
-1. Create a pinned issue offering to try out the new version's beta for consumers [example: [Try out v8 beta on various influential community repos](https://github.com/typescript-eslint/typescript-eslint/issues/9141)]
-   - Ask each community project if they'd be interested in trying out the new version, such as in their Discord or on their issue tracker.
+1. Create a pinned issue offering to try out the new version's beta for end users (example: [Try out v8 beta on various influential community repos](https://github.com/typescript-eslint/typescript-eslint/issues/9141))
+   - Ask each community repo if they'd be interested in trying out the new version, such as in their Discord or on their issue tracker.
    - Each community project that's indicated willingness to receive a PR should have one.
+1. Create a pinned issue offering to try the new version's beta for downstream plugins (example: [Try out v8 beta on various influential plugins](https://github.com/typescript-eslint/typescript-eslint/issues/9501))
+   - These PRs can be sent without asking, as a friendly courtesy.
 1. Once the proposed _Shared Config Changes_ are merged into the `v${major}` branch, send a draft PR to each project with the new beta version.
 
 #### 1c. Post Community Testing Config Touchups
