update triageprocess.md for .NET 8 (#44421)

* update triageprocess.md for .NET 8

* Update TriageProcess.md

1 files changed, 8 insertions, 8 deletions

diff --git a/docs/TriageProcess.md b/docs/TriageProcess.md
index 60b16ed8d5..bea53b3867 100644
--- a/docs/TriageProcess.md
+++ b/docs/TriageProcess.md
@@ -28,16 +28,16 @@ We'll try to respond quickly to such issues (within days). If a user has collect
 ### Feature requests
 
 As soon as we identify an issue represents an ask for a new feature, we will label the issue with the `enhancement` label.
-Most of the time, we will automatically move these issues into the `.NET 7 Planning` milestone for further review during one of our [sprint planning meetings](#milestone-planning).
+Most of the time, we will automatically move these issues into the `.NET 8 Planning` milestone for further review during one of our [sprint planning meetings](#milestone-planning).
 If we think the feature request is not aligned with our goals, we may choose to close it immediately.
 In some situations, however, we may choose to collect more feedback before acting on the issue. In these situations we will move the issue in the `Backlog` so that we can review it during the [release planning](#release-planning).
 
 ### Bug reports
 
-If it's immediately clear, that the issue is related to a bug in the framework, we will apply the `bug` label to the issue.
+If it's immediately clear that the issue is related to a bug in the framework, we will apply the `bug` label to the issue.
 
 At this point, we will try to make a call regarding it's impact and severity. If the issue is critical, we may choose to include it in our current milestone for immediate handling or potentially patching.
-If the bug is relatively high impact, we will move the issue into the `.NET 7 Planning` milestone to review during our [sprint planning](#milestone-planning) meeting.
+If the bug is relatively high impact, we will move the issue into the `.NET 8 Planning` milestone to review during our [sprint planning](#milestone-planning) meeting.
 If the impact is unclear or the is a very corner case scenario, we may move it to the `Backlog` milestone to further evaluate the impact by reviewing customer upvotes / comments at a later time.
 
 ### Investigations
@@ -45,18 +45,18 @@ If the impact is unclear or the is a very corner case scenario, we may move it t
 In many situations it's not immediately clear whether a specific issue reported is a bug or not. To be certain, the team will need to spend time to investigate it before making a call regarding the faith of the issue. In these situations we will apply the `investigate` label to the issue.
 In many situations, these issues turn out to be a result of some kind of misconfiguration in the user code.
 In some rare situations, however, these turn out to be caused by very impactful issues. So we will make a call during the triage whether we need to immediately investigate certain issues or not.
-If not, we will move the investigation to the `.NET 7 Planning` to review during one of the upcoming [sprint planning meetings](#milestone-planning).
+If not, we will move the investigation to the `.NET 8 Planning` to review during one of the upcoming [sprint planning meetings](#milestone-planning).
 
 ### Documentation requests
 
 Some issues turn out to indicate user confusion around how to configure different aspects of the framework.
-When we determine such issues, we will mark these with the `Docs` label and move them into the `.NET 7 Planning` milestone to handle at a later time. The goal here will be to fill in the gaps or clarify our documentation, so that customers can be successful by using the guidance provided in the documentation.
+When we determine such issues, we will mark these with the `Docs` label and move them into the `.NET 8 Planning` milestone to handle at a later time. The goal here will be to fill in the gaps or clarify our documentation, so that customers can be successful by using the guidance provided in the documentation.
 If we identify a documentation issue which too many customers are having trouble with, we may choose to address that in current milestone.
 
 ## Milestone Planning
 
 Our milestones are usually a month long.
-Before each milestone we have one or more planning meetings, where we look through all the accumulated issues in the `.NET 7 Planning` milestone and choose the most important and impactful ones to handle during the next milestone. This will be a mixture of feature requests, bug fixes, documentation issues as well as some investigations.
+Before each milestone we have one or more planning meetings, where we look through all the accumulated issues in the `.NET 8 Planning` milestone and choose the most important and impactful ones to handle during the next milestone. This will be a mixture of feature requests, bug fixes, documentation issues as well as some investigations.
 
 Note, that we will investigate only issues, which have accumulated more than certain number of upvotes and/or comments, which will indicate that there is some wider impact associated with it.
 We may not investigate issues which haven't received many votes/comments and choose to close these. The reason is that the impact is very scoped and potentially something is wrong in the user code. Consider asking these questions on StackOverflow.
@@ -65,10 +65,10 @@ For some feature requests and bug reports, depending on the user involvement, we
 
 ## Release Planning
 
-Once we approach to the end of the release cycle (.NET Core 3, .NET 5) we will look through the accumulated issues in the `Backlog` milestone. This is a long process as the amount of issues accumulated in this milestone is quite large.
+Once we approach to the end of the release cycle (such as for .NET 7) we will look through the accumulated issues in the `Backlog` milestone. This is a long process as the amount of issues accumulated in this milestone is quite large.
 
 We will try to prioritize issues with most community requests / upvotes assuming these are aligned with our goals.
-Issues, which we will think are candidates for the upcoming release, will be moved to the `.NET 7 Planning` milestone. This process is documented in more details in the [Release Planning](https://github.com/dotnet/aspnetcore/blob/main/docs/ReleasePlanning.md) document.
+Issues, which we will think are candidates for the upcoming release, will be moved to the `.NET 8 Planning` milestone. This process is documented in more details in the [Release Planning](https://github.com/dotnet/aspnetcore/blob/main/docs/ReleasePlanning.md) document.
 
 ## Cleanup
 As we go through all the issues in the Backlog milestone as part of our release planning process, we will also cleanup the milestone by closing low priority issues, which have stayed in the backlog for more than 2 releases. While some of these issues may seem reasonable, the fact that those haven't been addressed for such prolonged period of time indicate that they're not as important for the product as they may seem to be.