MicrosoftDocs · learn-build-service-prod · Aug 12, 2024 · Jul 29, 2024 · Jul 29, 2024 · Jul 29, 2024
diff --git a/docs/azure/how-to-sign-in-with-azure-subscription.md b/docs/azure/how-to-sign-in-with-azure-subscription.md
@@ -23,7 +23,7 @@ Visual Studio also gives you the opportunity to [create a new, free Azure accoun
 Visual Studio allows you to sign in with multiple accounts and it let's you work with Azure resources across multiple Azure subscriptions so no need to sign-out of one in order to sign-in with another!
 
 > [!NOTE]
-> For Azure CLI users, be aware that the sign-in from Azure CLI is separate from the sign-in used in Visual Studio, so even if you're signed in to Azure by using `az login` on the same machine where you're running Visual Studio, you still need to provide credentials within Visual Studio.
+> When using Azure CLI, be aware that the sign-in from the Azure CLI is separate from the sign-in used in Visual Studio, so even if you're signed in to Azure by using `az login` on the same machine where you're running Visual Studio, you still need to provide credentials within Visual Studio.
 
 ## To sign in to Azure from a dialog or wizard screen
 

diff --git a/docs/azure/overview.md b/docs/azure/overview.md
@@ -60,11 +60,11 @@ If you need help configuring CI/CD for a GitHub repo for the first time, Visual
 
 You can use Visual Studio debug your application while it's running in Azure, so that you can identify and reproduce problems in an environment that is as close as possible to a production environment. For web apps hosted in Azure App Service, see [Remote debug ASP.NET Core on Azure App Service](../debugger/remote-debugging-azure-app-service.md). For Azure Functions, see [Develop Azure Functions with Visual Studio - Remote debugging](/azure/azure-functions/functions-develop-vs#remote-debugging?tabs=isolated-process).
 
-If you're using a virtual machine (VM) to host an ASP.NET Core web app, see [Remote debug ASP.NET Core on IIS using an Azure VM from Visual Studio](../debugger/remote-debugging-azure.md).
+If you're using a virtual machine (VM) to host an ASP.NET Core web app, see [Remote debug ASP.NET Core on Internet Information Services (IIS) using an Azure VM from Visual Studio](../debugger/remote-debugging-azure.md).
 
 ## Use integrated Azure features
 
-When running in the Azure cloud, apps can benefit from Azure's standards for high availability, [scaling up](/azure/app-service/manage-scale-up) and [scaling out](/azure/app-service/manage-automatic-scaling?tabs=azure-portal) capabilities, [monitoring](/azure/azure-monitor/app/asp-net), [load testing](/azure/load-testing/overview-what-is-azure-load-testing), and other benefits. Visual Studio comes integrated with Azure functionality like [Remote debugging](../debugger/remote-debugging.md), viewing logs, and more.
+When running in the Azure cloud, apps can benefit from the Azure standards for high availability, [scaling up](/azure/app-service/manage-scale-up) and [scaling out](/azure/app-service/manage-automatic-scaling?tabs=azure-portal) capabilities, [monitoring](/azure/azure-monitor/app/asp-net), [load testing](/azure/load-testing/overview-what-is-azure-load-testing), and other benefits. Visual Studio comes integrated with Azure functionality like [Remote debugging](../debugger/remote-debugging.md), viewing logs, and more.
 
 ## Save money with local emulation support
 

diff --git a/docs/azure/vs-active-directory-add-connected-service.md b/docs/azure/vs-active-directory-add-connected-service.md
@@ -69,7 +69,7 @@ You can also see the Active Directory domain on the [Azure portal](https://go.mi
 :::moniker range="<=vs-2019"
 1. In Visual Studio, create or open an ASP.NET MVC project, or an ASP.NET Web API project.
 
-1. Select the **Project**, **Manage Connected Services** menu command, or right-click the **Connected Services** node found under the project in Solution Explorer, and choose **Manage Connected Services**, then click the link **Add a service dependency** and choose **Microsoft Identity platform**.
+1. Select the **Project**, **Manage Connected Services** menu command, or right-click the **Connected Services** node found under the project in Solution Explorer, and choose **Manage Connected Services**, and then select the link **Add a service dependency** and choose **Microsoft Identity platform**.
 
    ![Screenshot showing the Microsoft Identity platform option.](./media/vs-azure-active-directory/vs-2019/add-dependency-microsoft-identity-platform.png)
 

diff --git a/docs/code-quality/working-with-code-metrics-data.md b/docs/code-quality/working-with-code-metrics-data.md
@@ -59,7 +59,7 @@ You can add or remove results columns from the **Code Metrics Results** window.
 
 ### Add or remove a column
 
-1. Click the **Add/Remove Columns** button, or right-click any column heading and then click **Add/Remove Columns**.
+1. Click the **Add/Remove Columns** button, or right-click any column heading, and then select **Add/Remove Columns**.
 
 1. In the **Add/Remove Columns** dialog box, select, or clear the checkbox for the column that you want to add or remove, and then choose **OK**.
 
@@ -85,7 +85,7 @@ For more information about Azure Boards work items, see [Work items](/azure/devo
 
 1. Right-click the result.
 
-2. Point to **Create Work Item**, and then click the type of work item you want to create (**Bug**, **Task**, and so forth).
+2. Point to **Create Work Item**, and then select the type of work item you want to create (**Bug**, **Task**, and so forth).
 
 3. Complete the work item form by filling in all required fields.
 

diff --git a/docs/containers/container-msbuild-properties.md b/docs/containers/container-msbuild-properties.md
@@ -48,7 +48,7 @@ The following table shows the MSBuild properties available for Dockerfile projec
 | ContainerDevelopmentMode | Controls whether "build-on-host" optimization ("Fast Mode" debugging) is enabled. Allowed values are **Fast** and **Regular**. | Fast |1.0.1872750 or newer|
 | ContainerVsDbgPath | The path for VSDBG debugger. | `%USERPROFILE%\vsdbg\vs2017u5` |1.0.1985401 or newer|
 | DockerDebuggeeArguments | When debugging, the debugger is instructed to pass these arguments to the launched executable. | Not applicable to ASP.NET .NET Framework projects |1.7.8 or newer|
-| DockerDebuggeeProgram | When debugging, the debugger is instructed to launch this executable. | For .NET Core and .NET 5 and later projects: dotnet, ASP.NET .NET Framework projects: Not applicable (IIS is always used) |1.7.8 or newer|
+| DockerDebuggeeProgram | When debugging, the debugger is instructed to launch this executable. | For .NET Core and .NET 5 and later projects: dotnet, ASP.NET .NET Framework projects: Not applicable (Internet Information Services (IIS) is always used) |1.7.8 or newer|
 | DockerDebuggeeKillProgram | This command is used to kill the running process in a container. | Not applicable to ASP.NET .NET Framework projects |1.7.8 or newer|
 | DockerDebuggeeWorkingDirectory | When debugging, the debugger is instructed to use this path as the working directory. | C:\app (Windows) or /app (Linux) |1.7.8 or newer|
 | DockerDefaultTargetOS | The default target operating system used when building the Docker image. | Set by Visual Studio. |1.0.1985401 or newer|

diff --git a/docs/containers/overview.md b/docs/containers/overview.md
@@ -131,7 +131,7 @@ ENTRYPOINT ["dotnet", "WebApplication-Docker.dll"]
 
 When you add or enable Docker support to a .NET 7 or later project, Visual Studio shows the **Container Scaffolding Options** dialog box, which gives you the choice of operating system (Linux or Windows), but also the ability to choose the container build type, either **Dockerfile** or **.NET SDK**. This dialog box does not appear in .NET Framework projects or Azure Functions projects.
 
-In 17.11 and later, you can also specify the **Container Image Distro** and the **Docker Build Context**. 
+In 17.11 and later, you can also specify the **Container Image Distro** and the **Docker Build Context**.
 
 ![Screenshot showing the Container Scaffolding Options dialog for adding Docker support.](./media/overview/vs-2022/container-scaffolding-options.png)
 

diff --git a/docs/ide/media/vs-2022/all-in-one-search-member-filter.png b/docs/ide/media/vs-2022/all-in-one-search-member-filter.png
diff --git a/docs/ide/media/vs-2022/all-one-search-from-menu-bar.png b/docs/ide/media/vs-2022/all-one-search-from-menu-bar.png
diff --git a/docs/ide/media/vs-2022/search-code-scope.png b/docs/ide/media/vs-2022/search-code-scope.png
diff --git a/docs/ide/visual-studio-search.md b/docs/ide/visual-studio-search.md
@@ -32,7 +32,7 @@ If you're using Visual Studio 2022 [version 17.6](/visualstudio/releases/2022/re
 
 With **All-In-One Search**, not only can you search for features, but you can also search your code elements, such as files and symbols.
 
-:::image type="content" source="media/vs-2022/all-one-search.png" alt-text="Screenshot of the All-In-One Search experience in Visual Studio 2022 version 17.6 or later."::: 
+:::image type="content" source="media/vs-2022/all-in-one-search-member-filter.png" alt-text="Screenshot of the All-In-One Search experience in Visual Studio 2022 version 17.6 or later."::: 
 
 The new search experience appears as an option next to the menu bar. 
 
@@ -53,10 +53,14 @@ To quickly get a filtered experience, you can type the corresponding prefixes be
 |members  |`m:`     | **Alt**+**\\**                 |
 |text     |`x:`     | **Shift**+**Alt**+**F**        |
 
+In Visual Studio 17.11 and later, you can set the scope of code search to the current document, current project, the entire solution, or external files that are referenced in your solution, such as header files or files open from locations outside your solution. You can set different scopes for different filters. For example, the default experience can be set to look through *Entire solution* and `members` can be set to look through only the current document. Your selections will be remembered the next time you use code search.
+
+:::image type="content" alt-text="Screenshot of code search scope options." source="./media/vs-2022/search-code-scope.png" :::
+
 > [!TIP]
 > To learn more about the new search experience, see both the [Better search in Visual Studio](https://devblogs.microsoft.com/visualstudio/new-better-search-in-visual-studio/) and [All-In-One Search available in 17.6](https://devblogs.microsoft.com/visualstudio/all-in-one-search-available-in-17-6/) blog posts.
 
-The text filter (**Shift**+**Alt**+**F**) in Code Search is available in preview as of 17.9 Preview 2. See [17.9 Preview 3 brings exciting changes to Code Search
+The text filter (**Shift**+**Alt**+**F**) in Code Search is available in preview in Visual Studio 17.9 and later. See [17.9 Preview 3 brings exciting changes to Code Search
 ](https://devblogs.microsoft.com/visualstudio/17-9-preview-3-brings-exciting-changes-to-code-search/). Search for a text string, with options to match the case, match whole words, or use a regular expression. The regular expression format is described at [Regular expressions](/dotnet/standard/base-types/regular-expression-language-quick-reference).
 
 :::image type="content" alt-text="Screenshot of text search with various options." source="./media/vs-2022/search-text-search-text-options-highlighted.png" :::