minor formatting fixes (#2494)

diff --git a/documentation/dotnet-trace-instructions.md b/documentation/dotnet-trace-instructions.md
index 8d065bce3e972f8269d59f79da4e1260db10d892..154996a927d691f4316190b1110bae2e4a6268f4 100644 (file)
--- a/documentation/dotnet-trace-instructions.md
+++ b/documentation/dotnet-trace-instructions.md
@@ -84,14 +84,12 @@ Output File    : E:\temp\gcperfsim\trace.nettrace
 Press <Enter> or <Ctrl+C> to exit...
 ```
 
-You can stop collecting the trace by pressing `<Enter>` or `<Ctrl + C>` key. Doing this will also exit `hello.exe`.
+You can stop collecting the trace by pressing <kbd>Enter</kbd> or <kbd>Ctrl</kbd> + <kbd>C</kbd> key. Doing this will also exit `hello.exe`.
 
-### NOTE
-* Launching `hello.exe` via dotnet-trace will redirect its input/output and you will not be able to interact with it on the console by default. Use the --show-child-io switch to interact with its stdin/stdout.
-
-* Exiting the tool via CTRL+C or SIGTERM will safely end both the tool and the child process.
-
-* If the child process exits before the tool, the tool will exit as well and the trace should be safely viewable.
+> [!NOTE]
+> * Launching hello.exe via dotnet-trace will redirect its input/output and you will not be able to interact with it on the console by default. Use the `--show-child-io` switch to interact with its stdin/stdout.
+> * Exiting the tool via CTRL+C or SIGTERM will safely end both the tool and the child process.
+> * If the child process exits before the tool, the tool will exit as well and the trace should be safely viewable.
 
 
 ## Viewing the trace captured from dotnet-trace
@@ -282,4 +280,4 @@ Options:
     The format of the output trace file.  This defaults to "nettrace" on Windows and "speedscope" on other OSes.
 
   -- <command> (for target applications running .NET 5.0 or later only)
-    The command to run to launch a child process and trace from startup.
\ No newline at end of file
+    The command to run to launch a child process and trace from startup.