Merged main into live

Author: mijacobs

docs/ide/how-to-report-a-problem-with-visual-studio.md

@@ -46,7 +46,7 @@ Here are the steps to report a problem.
     ![Take a screenshot](../ide/media/feedback-screenshot.png)
     *Only Microsoft engineers can see the screenshot*
 
-1. Record your actions to reproduce the issue.
+<a name="trace"></a>1. Record your actions to reproduce the issue.
 
    One of the best ways to help the Visual Studio engineering team solve the problem is to provide a trace and heap dump files for them to look through. You can do that by recording the steps that resulted in the bug. A screenshot will be captured every time the mouse is clicked, but keyboard entry will not record screenshots.
    1. Click **Start recording**. Wait a moment for the permissions prompt.

docs/ide/whats-new-visual-studio-2022.md

@@ -130,6 +130,9 @@ Why send feedback to the Visual Studio team? Because we take customer feedback s
 
 Review the following blog posts to learn more about the improvements we've made to Visual Studio 2022, to date:
 
+* [Visual Studio 2022 17.10 is now available](https://devblogs.microsoft.com/visualstudio/visual-studio-2022-17-10-now-available/)
+* [Visual Studio 2022 17.9 is now available](https://devblogs.microsoft.com/visualstudio/visual-studio-2022-17-9-now-available/)
+* [Visual Studio 2022 17.8 is now available](https://devblogs.microsoft.com/visualstudio/visual-studio-17-8-now-available/)
 * [Visual Studio 2022 17.7 is now available](https://devblogs.microsoft.com/visualstudio/visual-studio-2022-17-7-now-available/)
 * [Visual Studio 2022 17.6 is now available](https://devblogs.microsoft.com/visualstudio/visual-studio-2022-17-6-now-available/)
 * [Visual Studio 2022 17.5 is now available](https://devblogs.microsoft.com/visualstudio/visual-studio-2022-17-5-released/)