diff --git a/docs/core/whats-new/dotnet-10/sdk.md b/docs/core/whats-new/dotnet-10/sdk.md
index 56df18a69ef28..8b873cbcf0591 100644
--- a/docs/core/whats-new/dotnet-10/sdk.md
+++ b/docs/core/whats-new/dotnet-10/sdk.md
@@ -33,7 +33,7 @@ You can now use the `dotnet tool exec` command to execute a .NET tool without in
 
 ```bash
 dotnet tool exec --source ./artifacts/package/ dotnetsay  "Hello, World!"
-Tool package dotnetsay @1.0.0 will be downloaded from source <source>.
+Tool package dotnetsay@1.0.0 will be downloaded from source <source>.
 Proceed? [y/n] (y): y
   _   _          _   _                __        __                 _       _   _
  | | | |   ___  | | | |   ___         \ \      / /   ___    _ __  | |   __| | | |
@@ -43,7 +43,7 @@ Proceed? [y/n] (y): y
                                 |/
 ```
 
-This downloads and runs the specified tool package in one command. By default, users are prompted to confirm the download if the tool doesn't already exist locally. The latest version of the chosen tool package is used unless an explicit version is specified (for example, `dotnetsay @0.1.0`).
+This downloads and runs the specified tool package in one command. By default, users are prompted to confirm the download if the tool doesn't already exist locally. The latest version of the chosen tool package is used unless an explicit version is specified (for example, `dotnetsay@0.1.0`).
 
 One-shot tool execution works seamlessly with local tool manifests. If you run a tool from a location containing a `.config/dotnet-tools.json` nearby, the version of the tool in that configuration will be used instead of the latest version available.
 
@@ -52,7 +52,7 @@ One-shot tool execution works seamlessly with local tool manifests. If you run a
 The `dnx` script provides a streamlined way to execute tools. It forwards all arguments to the `dotnet` CLI for processing, making tool usage as simple as possible:
 
 ```bash
-dnx dotnetsay  "Hello, World!"
+dnx dotnetsay "Hello, World!"
 ```
 
 The actual implementation of the `dnx` command is in the `dotnet` CLI itself, allowing its behavior to evolve over time.