diff --git a/aspnetcore/blazor/debug.md b/aspnetcore/blazor/debug.md
index a8f9dc694233..8f955655deb0 100644
--- a/aspnetcore/blazor/debug.md
+++ b/aspnetcore/blazor/debug.md
@@ -222,8 +222,6 @@ Breakpoints can also be hit in the server project.
Breakpoints are **not** hit during app startup before the debug proxy is running. This includes breakpoints in the `Program` file and breakpoints in the [`OnInitialized{Async}` lifecycle methods](xref:blazor/components/lifecycle#component-initialization-oninitializedasync) of components that are loaded by the first page requested from the app.
-**Start Without Debugging** [Ctrl+F5 (Windows) or ⌘+F5 (macOS)] isn't supported. When the app is run in Debug configuration, debugging overhead always results in a small performance reduction.
-
---
:::moniker-end
@@ -254,8 +252,6 @@ Breakpoints are **not** hit during app startup before the debug proxy is running
Breakpoints are **not** hit during app startup before the debug proxy is running. This includes breakpoints in the `Program` file and breakpoints in the [`OnInitialized{Async}` lifecycle methods](xref:blazor/components/lifecycle#component-initialization-oninitializedasync) of components that are loaded by the first page requested from the app.
-**Start Without Debugging** [Ctrl+F5 (Windows) or ⌘+F5 (macOS)] isn't supported. When the app is run in Debug configuration, debugging overhead always results in a small performance reduction.
-
---
:::moniker-end
@@ -285,8 +281,6 @@ Breakpoints are **not** hit during app startup before the debug proxy is running
Breakpoints are **not** hit during app startup before the debug proxy is running. This includes breakpoints in the `Program` file and breakpoints in the [`OnInitialized{Async}` lifecycle methods](xref:blazor/components/lifecycle#component-initialization-oninitializedasync) of components that are loaded by the first page requested from the app.
-**Start Without Debugging** [Ctrl+F5 (Windows) or ⌘+F5 (macOS)] isn't supported. When the app is run in Debug configuration, debugging overhead always results in a small performance reduction.
-
---
:::moniker range="< aspnetcore-8.0"
@@ -317,8 +311,6 @@ You can also debug server code in the **:::no-loc text="Server":::** project:
Breakpoints are **not** hit during app startup before the debug proxy is running. This includes breakpoints in the `Program` file and breakpoints in the [`OnInitialized{Async}` lifecycle methods](xref:blazor/components/lifecycle#component-initialization-oninitializedasync) of components that are loaded by the first page requested from the app.
-**Start Without Debugging** [Ctrl+F5 (Windows) or ⌘+F5 (macOS)] isn't supported. When the app is run in Debug configuration, debugging overhead always results in a small performance reduction.
-
# [Visual Studio Code](#tab/visual-studio-code)
> [!NOTE]
@@ -336,8 +328,6 @@ Publishing an app disables debugger support. To debug a published, hosted Blazor
> [!WARNING]
> Published, hosted Blazor WebAssembly apps should only enable debugging and copying output symbols when deploying published assets ***locally***. Don't deploy a published app into a production environment with the `DebuggerSupport` and `CopyOutputSymbolsToPublishDirectory` properties set to `true`.
-**Start Without Debugging** [Ctrl+F5 (Windows) or ⌘+F5 (macOS)] isn't supported. When the app is run in Debug configuration, debugging overhead always results in a small performance reduction.
-
---
:::moniker-end
diff --git a/aspnetcore/blazor/tooling.md b/aspnetcore/blazor/tooling.md
index 74ee3de9ed0c..0dd96047116a 100644
--- a/aspnetcore/blazor/tooling.md
+++ b/aspnetcore/blazor/tooling.md
@@ -415,7 +415,7 @@ Visual Studio:
:::zone pivot="vsc"
-In VS Code, press Ctrl+F5 (Windows) or ⌘+F5 (macOS) to run the app without debugging.
+In VS Code, press Ctrl+F5 to run the app without debugging.
At the **Select debugger** prompt in the **Command Palette** at the top of the VS Code UI, select **C#**. At the next prompt, select the HTTPS profile (`[https]`).
@@ -477,7 +477,7 @@ Stop the app using the following approach:
Stop the app using the following approach:
1. Close the browser window.
-2. In the command shell, press Ctrl+C (Windows) or ⌘+C (macOS).
+2. In the command shell, press Ctrl+C.
:::zone-end
diff --git a/aspnetcore/blazor/tutorials/build-a-blazor-app.md b/aspnetcore/blazor/tutorials/build-a-blazor-app.md
index 69afe6142abb..0d8e4cd462d7 100644
--- a/aspnetcore/blazor/tutorials/build-a-blazor-app.md
+++ b/aspnetcore/blazor/tutorials/build-a-blazor-app.md
@@ -531,7 +531,7 @@ Save the `Todo.razor` file. The app is automatically rebuilt in the command shel
Add items, edit items, and mark todo items done to test the component.
-When finished, shut down the app in the command shell. Many command shells accept the keyboard command Ctrl+C (Windows) or ⌘+C (macOS) to stop an app.
+When finished, shut down the app in the command shell. Many command shells accept the keyboard command Ctrl+C to stop an app.
## Publish to Azure
diff --git a/aspnetcore/blazor/tutorials/movie-database-app/part-1.md b/aspnetcore/blazor/tutorials/movie-database-app/part-1.md
index fbf729753b81..cda5e6cc3a35 100644
--- a/aspnetcore/blazor/tutorials/movie-database-app/part-1.md
+++ b/aspnetcore/blazor/tutorials/movie-database-app/part-1.md
@@ -215,7 +215,7 @@ Stop the app using the following approach:
Stop the app using the following approach:
1. Close the browser window.
-2. In the command shell, press Ctrl+C (Windows) or ⌘+C (macOS).
+2. In the command shell, press Ctrl+C.
:::zone-end
diff --git a/aspnetcore/blazor/tutorials/movie-database-app/part-2.md b/aspnetcore/blazor/tutorials/movie-database-app/part-2.md
index c5f4fecd887b..d5d06457903d 100644
--- a/aspnetcore/blazor/tutorials/movie-database-app/part-2.md
+++ b/aspnetcore/blazor/tutorials/movie-database-app/part-2.md
@@ -476,7 +476,7 @@ Stop the app using the following approach:
Stop the app using the following approach:
1. Close the browser window.
-2. From the command shell, press Ctrl+C (Windows) or ⌘+C (macOS).
+2. From the command shell, press Ctrl+C.
:::zone-end
diff --git a/aspnetcore/blazor/tutorials/movie-database-app/part-3.md b/aspnetcore/blazor/tutorials/movie-database-app/part-3.md
index 53fee73b4848..3d84efdf764e 100644
--- a/aspnetcore/blazor/tutorials/movie-database-app/part-3.md
+++ b/aspnetcore/blazor/tutorials/movie-database-app/part-3.md
@@ -167,7 +167,7 @@ Stop the app by closing the browser's window and pressing Shift+
:::zone pivot="cli"
-Stop the app by closing the browser's window and pressing Ctrl+C (Windows) or ⌘+C (macOS) in the command shell.
+Stop the app by closing the browser's window and pressing Ctrl+C in the command shell.
:::zone-end
@@ -338,7 +338,7 @@ Stop the app by closing the browser's window and pressing Shift+
:::zone pivot="cli"
-Stop the app by closing the browser's window and pressing Ctrl+C (Windows) or ⌘+C (macOS) in the command shell.
+Stop the app by closing the browser's window and pressing Ctrl+C in the command shell.
:::zone-end
diff --git a/aspnetcore/blazor/tutorials/movie-database-app/part-4.md b/aspnetcore/blazor/tutorials/movie-database-app/part-4.md
index 9ccc063121dd..126c27f1671c 100644
--- a/aspnetcore/blazor/tutorials/movie-database-app/part-4.md
+++ b/aspnetcore/blazor/tutorials/movie-database-app/part-4.md
@@ -253,7 +253,7 @@ If the database contains records from earlier testing, run the app and delete th
:::zone pivot="cli"
-If the database contains records from earlier testing, run the app and delete the entities that you created in the database. Stop the app by closing the browser's window and pressing Ctrl+C (Windows) or ⌘+C (macOS) in the command shell.
+If the database contains records from earlier testing, run the app and delete the entities that you created in the database. Stop the app by closing the browser's window and pressing Ctrl+C (Windows) in the command shell.
:::zone-end
@@ -339,7 +339,7 @@ If the app is running, shut the app down by closing the browser's window and pre
:::zone pivot="cli"
-If the app is running, shut the app down by closing the browser's window and pressing Ctrl+C (Windows) or ⌘+C (macOS) in the command shell.
+If the app is running, shut the app down by closing the browser's window and pressing Ctrl+C in the command shell.
:::zone-end
diff --git a/aspnetcore/blazor/tutorials/movie-database-app/part-5.md b/aspnetcore/blazor/tutorials/movie-database-app/part-5.md
index 388822ed0feb..5d8a9e6845e9 100644
--- a/aspnetcore/blazor/tutorials/movie-database-app/part-5.md
+++ b/aspnetcore/blazor/tutorials/movie-database-app/part-5.md
@@ -135,7 +135,7 @@ To align the model and the database schema, create and apply an EF Core *databas
>
> When using VS Code, close the browser's window and stop the app in VS Code with **Run** > **Stop Debugging** or by pressing Shift+F5 on the keyboard.
>
-> When using the .NET CLI, close the browser's window and stop the app in the command shell with Ctrl+C (Windows) or ⌘+C (macOS).
+> When using the .NET CLI, close the browser's window and stop the app in the command shell with Ctrl+C.
:::zone pivot="vs"
diff --git a/aspnetcore/blazor/tutorials/movie-database-app/part-6.md b/aspnetcore/blazor/tutorials/movie-database-app/part-6.md
index 1da06c5c5e01..64b6ffbdd7ff 100644
--- a/aspnetcore/blazor/tutorials/movie-database-app/part-6.md
+++ b/aspnetcore/blazor/tutorials/movie-database-app/part-6.md
@@ -130,7 +130,7 @@ Stop the app by closing the browser's window and pressing Shift+
:::zone pivot="cli"
-Stop the app by closing the browser's window and pressing Ctrl+C (Windows) or ⌘+C (macOS) in the command shell.
+Stop the app by closing the browser's window and pressing Ctrl+C in the command shell.
:::zone-end
diff --git a/aspnetcore/blazor/tutorials/signalr-blazor.md b/aspnetcore/blazor/tutorials/signalr-blazor.md
index f74d2f5a99af..cde1ef913174 100644
--- a/aspnetcore/blazor/tutorials/signalr-blazor.md
+++ b/aspnetcore/blazor/tutorials/signalr-blazor.md
@@ -248,11 +248,11 @@ Follow the guidance for your tooling:
# [Visual Studio](#tab/visual-studio)
-With the server `BlazorSignalRApp` project selected in **Solution Explorer**, press F5 to run the app with debugging or Ctrl+F5 (Windows)/⌘+F5 (macOS) to run the app without debugging.
+With the server `BlazorSignalRApp` project selected in **Solution Explorer**, press F5 to run the app with debugging or Ctrl+F5 to run the app without debugging.
# [Visual Studio Code](#tab/visual-studio-code)
-Press F5 to run the app with debugging or Ctrl+F5 (Windows)/⌘+F5 (macOS) to run the app without debugging.
+Press F5 to run the app with debugging or Ctrl+F5 to run the app without debugging.
# [.NET CLI](#tab/net-cli/)
@@ -529,7 +529,7 @@ Follow the guidance for your tooling:
# [Visual Studio](#tab/visual-studio)
-In **Solution Explorer**, select the `BlazorWebAssemblySignalRApp.Server` project. Press F5 to run the app with debugging or Ctrl+F5 (Windows)/⌘+F5 (macOS) to run the app without debugging.
+In **Solution Explorer**, select the `BlazorWebAssemblySignalRApp.Server` project. Press F5 to run the app with debugging or Ctrl+F5 to run the app without debugging.
> [!IMPORTANT]
> When executing a hosted Blazor WebAssembly app, run the app from the [solution's](xref:blazor/tooling#visual-studio-solution-file-sln) **:::no-loc text="Server":::** project.
@@ -545,7 +545,7 @@ In **Solution Explorer**, select the `BlazorWebAssemblySignalRApp.Server` projec
For information on configuring VS Code assets in the `.vscode` folder, see the **Linux** operating system guidance in .
-Press F5 to run the app with debugging or Ctrl+F5 (Windows)/⌘+F5 (macOS) to run the app without debugging.
+Press F5 to run the app with debugging or Ctrl+F5 to run the app without debugging.
> [!IMPORTANT]
> When executing a hosted Blazor WebAssembly app, run the app from the [solution's](xref:blazor/tooling#visual-studio-solution-file-sln) **:::no-loc text="Server":::** project.
diff --git a/aspnetcore/fundamentals/host/generic-host.md b/aspnetcore/fundamentals/host/generic-host.md
index 2f9dbd6f6d2c..65f4bc71286b 100644
--- a/aspnetcore/fundamentals/host/generic-host.md
+++ b/aspnetcore/fundamentals/host/generic-host.md
@@ -104,7 +104,7 @@ The implementation controls wh
`Microsoft.Extensions.Hosting.Internal.ConsoleLifetime` is the default `IHostLifetime` implementation. `ConsoleLifetime`:
-* Listens for Ctrl+C/SIGINT (Windows), ⌘+C (macOS), or SIGTERM and calls to start the shutdown process.
+* Listens for Ctrl+C/SIGINT (Windows), Ctrl+C (macOS), or SIGTERM and calls to start the shutdown process.
* Unblocks extensions such as [RunAsync](#runasync) and [WaitForShutdownAsync](#waitforshutdownasync).
## IHostEnvironment
@@ -406,7 +406,7 @@ The difference between `Run*` and `Start*` methods is that `Run*` methods wait f
### RunConsoleAsync
- enables console support, builds and starts the host, and waits for Ctrl+C/SIGINT (Windows), ⌘+C (macOS), or SIGTERM to shut down.
+ enables console support, builds and starts the host, and waits for Ctrl+C/SIGINT (Windows), Ctrl+C (macOS), or SIGTERM to shut down.
### Start
@@ -424,7 +424,7 @@ The difference between `Run*` and `Start*` methods is that `Run*` methods wait f
### WaitForShutdown
- blocks the calling thread until shutdown is triggered by the IHostLifetime, such as via Ctrl+C/SIGINT (Windows), ⌘+C (macOS), or SIGTERM.
+ blocks the calling thread until shutdown is triggered by the IHostLifetime, such as via Ctrl+C/SIGINT (Windows), Ctrl+C (macOS), or SIGTERM.
### WaitForShutdownAsync
@@ -564,7 +564,7 @@ The implementation controls wh
`Microsoft.Extensions.Hosting.Internal.ConsoleLifetime` is the default `IHostLifetime` implementation. `ConsoleLifetime`:
-* Listens for Ctrl+C/SIGINT (Windows), ⌘+C (macOS), or SIGTERM and calls to start the shutdown process.
+* Listens for Ctrl+C/SIGINT (Windows), Ctrl+C (macOS), or SIGTERM and calls to start the shutdown process.
* Unblocks extensions such as [RunAsync](#runasync) and [WaitForShutdownAsync](#waitforshutdownasync).
## IHostEnvironment
@@ -894,7 +894,7 @@ The difference between `Run*` and `Start*` methods is that `Run*` methods wait f
### RunConsoleAsync
- enables console support, builds and starts the host, and waits for Ctrl+C/SIGINT (Windows), ⌘+C (macOS), or SIGTERM to shut down.
+ enables console support, builds and starts the host, and waits for Ctrl+C/SIGINT (Windows), Ctrl+C (macOS), or SIGTERM to shut down.
### Start
@@ -912,7 +912,7 @@ The difference between `Run*` and `Start*` methods is that `Run*` methods wait f
### WaitForShutdown
- blocks the calling thread until shutdown is triggered by the IHostLifetime, such as via Ctrl+C/SIGINT (Windows), ⌘+C (macOS), or SIGTERM.
+ blocks the calling thread until shutdown is triggered by the IHostLifetime, such as via Ctrl+C/SIGINT (Windows), Ctrl+C (macOS), or SIGTERM.
### WaitForShutdownAsync
@@ -1084,7 +1084,7 @@ The implementation controls wh
`Microsoft.Extensions.Hosting.Internal.ConsoleLifetime` is the default `IHostLifetime` implementation. `ConsoleLifetime`:
-* Listens for Ctrl+C/SIGINT (Windows), ⌘+C (macOS), or SIGTERM and calls to start the shutdown process.
+* Listens for Ctrl+C/SIGINT (Windows), Ctrl+C (macOS), or SIGTERM and calls to start the shutdown process.
* Unblocks extensions such as [RunAsync](#runasync) and [WaitForShutdownAsync](#waitforshutdownasync).
## IHostEnvironment
@@ -1401,7 +1401,7 @@ The difference between `Run*` and `Start*` methods is that `Run*` methods wait f
### RunConsoleAsync
- enables console support, builds and starts the host, and waits for Ctrl+C/SIGINT (Windows), ⌘+C (macOS), or SIGTERM to shut down.
+ enables console support, builds and starts the host, and waits for Ctrl+C/SIGINT (Windows), Ctrl+C (macOS), or SIGTERM to shut down.
### Start
@@ -1419,7 +1419,7 @@ The difference between `Run*` and `Start*` methods is that `Run*` methods wait f
### WaitForShutdown
- blocks the calling thread until shutdown is triggered by the IHostLifetime, such as via Ctrl+C/SIGINT (Windows), ⌘+C (macOS), or SIGTERM.
+ blocks the calling thread until shutdown is triggered by the IHostLifetime, such as via Ctrl+C/SIGINT (Windows), Ctrl+C (macOS), or SIGTERM.
### WaitForShutdownAsync
diff --git a/aspnetcore/host-and-deploy/linux-nginx.md b/aspnetcore/host-and-deploy/linux-nginx.md
index 4b65862143cd..4862b05f5e70 100644
--- a/aspnetcore/host-and-deploy/linux-nginx.md
+++ b/aspnetcore/host-and-deploy/linux-nginx.md
@@ -228,7 +228,7 @@ If the app runs on the server but fails to respond over the internet, check the
---
-When done testing the app, shut down the app with Ctrl+C (Windows) or ⌘+C (macOS) at the command prompt.
+When done testing the app, shut down the app with Ctrl+C in the command shell.
### Increase keepalive_requests
diff --git a/aspnetcore/host-and-deploy/linux-nginx/includes/linux-nginx5.md b/aspnetcore/host-and-deploy/linux-nginx/includes/linux-nginx5.md
index 39e833ee73ac..b4824eed0aa2 100644
--- a/aspnetcore/host-and-deploy/linux-nginx/includes/linux-nginx5.md
+++ b/aspnetcore/host-and-deploy/linux-nginx/includes/linux-nginx5.md
@@ -172,7 +172,7 @@ To directly run the app on the server:
If the app runs on the server but fails to respond over the Internet, check the server's firewall and confirm port 80 is open. If using an Azure Ubuntu VM, add a Network Security Group (NSG) rule that enables inbound port 80 traffic. There's no need to enable an outbound port 80 rule, as the outbound traffic is automatically granted when the inbound rule is enabled.
-When done testing the app, shut down the app with Ctrl+C (Windows) or ⌘+C (macOS) at the command prompt.
+When done testing the app, shut down the app with Ctrl+C in the command shell.
## Monitor the app
@@ -618,7 +618,7 @@ To directly run the app on the server:
If the app runs on the server but fails to respond over the Internet, check the server's firewall and confirm port 80 is open. If using an Azure Ubuntu VM, add a Network Security Group (NSG) rule that enables inbound port 80 traffic. There's no need to enable an outbound port 80 rule, as the outbound traffic is automatically granted when the inbound rule is enabled.
-When done testing the app, shut down the app with Ctrl+C (Windows) or ⌘+C (macOS) at the command prompt.
+When done testing the app, shut down the app with Ctrl+C in the command shell.
## Monitor the app
diff --git a/aspnetcore/tutorials/first-mvc-app/adding-controller.md b/aspnetcore/tutorials/first-mvc-app/adding-controller.md
index 2c5e3bb850d4..8d5ff3e148a0 100644
--- a/aspnetcore/tutorials/first-mvc-app/adding-controller.md
+++ b/aspnetcore/tutorials/first-mvc-app/adding-controller.md
@@ -78,7 +78,7 @@ The first comment states this is an [HTTP GET](https://developer.mozilla.org/doc
The second comment specifies an [HTTP GET](https://developer.mozilla.org/docs/Web/HTTP/Methods) method that's invoked by appending `/HelloWorld/Welcome/` to the URL. Later on in the tutorial, the scaffolding engine is used to generate `HTTP POST` methods, which update data.
-Run the app without the debugger by pressing Ctrl+F5 (Windows) or ⌘+F5 (macOS).
+Run the app without the debugger by pressing Ctrl+F5.
Append `/HelloWorld` to the path in the address bar. The `Index` method returns a string.
diff --git a/aspnetcore/tutorials/first-mvc-app/adding-controller/includes/adding-controller7.md b/aspnetcore/tutorials/first-mvc-app/adding-controller/includes/adding-controller7.md
index eb4c71bc01f2..39a804f6cfc5 100644
--- a/aspnetcore/tutorials/first-mvc-app/adding-controller/includes/adding-controller7.md
+++ b/aspnetcore/tutorials/first-mvc-app/adding-controller/includes/adding-controller7.md
@@ -74,7 +74,7 @@ The first comment states this is an [HTTP GET](https://developer.mozilla.org/doc
The second comment specifies an [HTTP GET](https://developer.mozilla.org/docs/Web/HTTP/Methods) method that's invoked by appending `/HelloWorld/Welcome/` to the URL. Later on in the tutorial, the scaffolding engine is used to generate `HTTP POST` methods, which update data.
-Run the app without the debugger by pressing Ctrl+F5 (Windows) or ⌘+F5 (macOS).
+Run the app without the debugger by pressing Ctrl+F5.
Append `/HelloWorld` to the path in the address bar. The `Index` method returns a string.
diff --git a/aspnetcore/tutorials/first-mvc-app/adding-controller/includes/adding-controller8.md b/aspnetcore/tutorials/first-mvc-app/adding-controller/includes/adding-controller8.md
index e94be47e6086..c1dbee6ab924 100644
--- a/aspnetcore/tutorials/first-mvc-app/adding-controller/includes/adding-controller8.md
+++ b/aspnetcore/tutorials/first-mvc-app/adding-controller/includes/adding-controller8.md
@@ -74,7 +74,7 @@ The first comment states this is an [HTTP GET](https://developer.mozilla.org/doc
The second comment specifies an [HTTP GET](https://developer.mozilla.org/docs/Web/HTTP/Methods) method that's invoked by appending `/HelloWorld/Welcome/` to the URL. Later on in the tutorial, the scaffolding engine is used to generate `HTTP POST` methods, which update data.
-Run the app without the debugger by pressing Ctrl+F5 (Windows) or ⌘+F5 (macOS).
+Run the app without the debugger by pressing Ctrl+F5.
Append `/HelloWorld` to the path in the address bar. The `Index` method returns a string.
diff --git a/aspnetcore/tutorials/first-mvc-app/adding-model.md b/aspnetcore/tutorials/first-mvc-app/adding-model.md
index ef296320f1a8..8dd17f7f3826 100644
--- a/aspnetcore/tutorials/first-mvc-app/adding-model.md
+++ b/aspnetcore/tutorials/first-mvc-app/adding-model.md
@@ -63,7 +63,7 @@ Build the project as a check for compiler errors.
[!INCLUDE[](~/includes/add-EF-NuGet-SQLite-CLI-9.md)]
-In Visual Studio Code, press Ctrl+F5 (Windows) or ⌘+F5 (macOS) to run the app without debugging.
+In Visual Studio Code, press Ctrl+F5 to run the app without debugging.
In the *Panel* below the editor region, select the *PROBLEMS* tab, or from the *View* menu, select *Problems* if it is not currently in view. Verify there are no compilation errors.
diff --git a/aspnetcore/tutorials/first-mvc-app/adding-model/includes/adding-model7.md b/aspnetcore/tutorials/first-mvc-app/adding-model/includes/adding-model7.md
index 0dfd1d857bcf..89cf57ff05a3 100644
--- a/aspnetcore/tutorials/first-mvc-app/adding-model/includes/adding-model7.md
+++ b/aspnetcore/tutorials/first-mvc-app/adding-model/includes/adding-model7.md
@@ -51,7 +51,7 @@ Build the project as a check for compiler errors.
[!INCLUDE[](~/includes/add-EF-NuGet-SQLite-CLI-7.md)]
-In Visual Studio Code, press Ctrl+F5 (Windows) or ⌘+F5 (macOS) to run the app without debugging.
+In Visual Studio Code, press Ctrl+F5 to run the app without debugging.
In the *Panel* below the editor region, select the *PROBLEMS* tab, or from the *View* menu, select *Problems* if it is not currently in view. Verify there are no compilation errors.
diff --git a/aspnetcore/tutorials/first-mvc-app/adding-model/includes/adding-model8.md b/aspnetcore/tutorials/first-mvc-app/adding-model/includes/adding-model8.md
index 0a589ce9c695..10f71eee7ced 100644
--- a/aspnetcore/tutorials/first-mvc-app/adding-model/includes/adding-model8.md
+++ b/aspnetcore/tutorials/first-mvc-app/adding-model/includes/adding-model8.md
@@ -51,7 +51,7 @@ Build the project as a check for compiler errors.
[!INCLUDE[](~/includes/add-EF-NuGet-SQLite-CLI-7.md)]
-In Visual Studio Code, press Ctrl+F5 (Windows) or ⌘+F5 (macOS) to run the app without debugging.
+In Visual Studio Code, press Ctrl+F5 to run the app without debugging.
In the *Panel* below the editor region, select the *PROBLEMS* tab, or from the *View* menu, select *Problems* if it is not currently in view. Verify there are no compilation errors.
diff --git a/aspnetcore/tutorials/razor-pages/model.md b/aspnetcore/tutorials/razor-pages/model.md
index 8d632cd3aabd..821d522e46a6 100644
--- a/aspnetcore/tutorials/razor-pages/model.md
+++ b/aspnetcore/tutorials/razor-pages/model.md
@@ -66,7 +66,7 @@ The `Movie` class contains:
[!INCLUDE[](~/includes/add-EF-NuGet-SQLite-CLI-9.md)]
-In Visual Studio Code, press Ctrl+F5 (Windows) or ⌘+F5 (macOS) to run the app without debugging.
+In Visual Studio Code, press Ctrl+F5 to run the app without debugging.
In the *Panel* below the editor region, select the *PROBLEMS* tab, or from the *View* menu, select *Problems* if it is not currently in view. Verify there are no compilation errors.
diff --git a/aspnetcore/tutorials/razor-pages/model/includes/model7.md b/aspnetcore/tutorials/razor-pages/model/includes/model7.md
index 22a282c00fe0..88239e8f6171 100644
--- a/aspnetcore/tutorials/razor-pages/model/includes/model7.md
+++ b/aspnetcore/tutorials/razor-pages/model/includes/model7.md
@@ -53,7 +53,7 @@ The `Movie` class contains:
[!INCLUDE[](~/includes/add-EF-NuGet-SQLite-CLI-7.md)]
-In Visual Studio Code, press Ctrl+F5 (Windows) or ⌘+F5 (macOS) to run the app without debugging.
+In Visual Studio Code, press Ctrl+F5 to run the app without debugging.
In the *Panel* below the editor region, select the *PROBLEMS* tab, or from the *View* menu, select *Problems* if it is not currently in view. Verify there are no compilation errors.
diff --git a/aspnetcore/tutorials/razor-pages/model/includes/model8.md b/aspnetcore/tutorials/razor-pages/model/includes/model8.md
index c9a00a3f4520..e48d1412c91c 100644
--- a/aspnetcore/tutorials/razor-pages/model/includes/model8.md
+++ b/aspnetcore/tutorials/razor-pages/model/includes/model8.md
@@ -54,7 +54,7 @@ The `Movie` class contains:
[!INCLUDE[](~/includes/add-EF-NuGet-SQLite-CLI-8.md)]
-In Visual Studio Code, press Ctrl+F5 (Windows) or ⌘+F5 (macOS) to run the app without debugging.
+In Visual Studio Code, press Ctrl+F5 to run the app without debugging.
In the *Panel* below the editor region, select the *PROBLEMS* tab, or from the *View* menu, select *Problems* if it is not currently in view. Verify there are no compilation errors.
diff --git a/aspnetcore/tutorials/razor-pages/razor-pages-start.md b/aspnetcore/tutorials/razor-pages/razor-pages-start.md
index e59b36a723f2..686994e2c2a5 100644
--- a/aspnetcore/tutorials/razor-pages/razor-pages-start.md
+++ b/aspnetcore/tutorials/razor-pages/razor-pages-start.md
@@ -113,7 +113,7 @@ Close the browser window.
[!INCLUDE[](~/includes/trustCertVSC.md)]
-In Visual Studio Code, press Ctrl+F5 (Windows) or ⌘+F5 (macOS) to run the app without debugging.
+In Visual Studio Code, press Ctrl+F5 to run the app without debugging.
At the **Select debugger** prompt, select **C#**.
diff --git a/aspnetcore/tutorials/razor-pages/razor-pages-start/includes/razor-pages-start7.md b/aspnetcore/tutorials/razor-pages/razor-pages-start/includes/razor-pages-start7.md
index 20f7ef3f2275..4afb7c87006b 100644
--- a/aspnetcore/tutorials/razor-pages/razor-pages-start/includes/razor-pages-start7.md
+++ b/aspnetcore/tutorials/razor-pages/razor-pages-start/includes/razor-pages-start7.md
@@ -119,7 +119,7 @@ Close the browser window.
[!INCLUDE[](~/includes/trustCertVSC.md)]
-In Visual Studio Code, press Ctrl+F5 (Windows) or ⌘+F5 (macOS) to run the app without debugging.
+In Visual Studio Code, press Ctrl+F5 to run the app without debugging.
At the **Select debugger** prompt, select **.NET 5+ and .NET Core**.
diff --git a/aspnetcore/tutorials/razor-pages/razor-pages-start/includes/razor-pages-start8.md b/aspnetcore/tutorials/razor-pages/razor-pages-start/includes/razor-pages-start8.md
index 7a924c48d177..6759f9c45dff 100644
--- a/aspnetcore/tutorials/razor-pages/razor-pages-start/includes/razor-pages-start8.md
+++ b/aspnetcore/tutorials/razor-pages/razor-pages-start/includes/razor-pages-start8.md
@@ -120,7 +120,7 @@ Close the browser window.
[!INCLUDE[](~/includes/trustCertVSC.md)]
-In Visual Studio Code, press Ctrl+F5 (Windows) or ⌘+F5 (macOS) to run the app without debugging.
+In Visual Studio Code, press Ctrl+F5 to run the app without debugging.
At the **Select debugger** prompt, select **.NET 5+ and .NET Core**.