Add more prompts to 8.0 breaking change issue template. (#82184)

Author: cjcenizal

.github/ISSUE_TEMPLATE/v8_breaking_change.md

@@ -13,7 +13,7 @@ assignees: ''
 ****************************************
  
 Please add a "NeededFor:${TeamName}" label to denote the team that is
-requesting the breaking change is surfaced in the Upgrade Assistant.
+requesting the breaking change to be surfaced in the Upgrade Assistant.
  
 -->
 
@@ -27,21 +27,24 @@ requesting the breaking change is surfaced in the Upgrade Assistant.
 
 **How many users will be affected?**
 
-<!-- e.g., Based on telemetry data, roughly 75% of our users will need to make changes to x -->
-<!-- e.g., A majority of users will need to make changes to x. -->
+<!-- e.g. Based on telemetry data, roughly 75% of our users will need to make changes to x. -->
+<!-- e.g. A majority of users will need to make changes to x. -->
 
 **What can users do to address the change manually?**
 
-<!-- If applicable, describe the manual workaround -->
+<!-- If applicable, describe the manual migration steps and/or link to available docs. -->
 
 **How could we make migration easier with the Upgrade Assistant?**
 
+<!-- This can be as basic as notifying the user about the deprecation and linking to some
+  migration docs, or as advanced as a dedicated UI for fixing the problem. -->
+
 **Are there any edge cases?**
 
 ## Test Data
 
-Provide test data. We can’t build a solution without data to test it against.
+<!-- Provide test data. We can’t build a solution without data to test it against. -->
 
 ## Cross links
 
-Cross-link to relevant [Elasticsearch breaking changes](https://www.elastic.co/guide/en/elasticsearch/reference/master/breaking-changes-8.0.html).
+<!-- Provide context. Cross-link to relevant [Elasticsearch breaking changes](https://www.elastic.co/guide/en/elasticsearch/reference/master/breaking-changes-8.0.html), PRs that introduced the breaking change, or other related issues. -->