Merge pull request #1690 from ferdeen/patch-2

Update profiling-feature-tour.md

Author: v-shils

docs/profiling/profiling-feature-tour.md

@@ -28,7 +28,7 @@ While you are debugging, you can use the **Diagnostic Tools** window to analyze
 
 The **Diagnostic Tools** window is often the preferred way to profile apps, but for Release builds you can also do a post-mortem analysis of your app instead. If you want more information on different approaches, see [Run profiling tools with or without the debugger](../profiling/running-profiling-tools-with-or-without-the-debugger.md). To see profiling tool support for different app types, see [Which tool should I use?](#which-tool-should-i-use).
 
-> ![NOTE]
+> [!NOTE]
 > You can use the post-mortem tools with Windows 7 and later. Windows 8 and later is required to run profiling tools with the debugger (**Diagnostic Tools** window).
 
 ## Analyze CPU Usage
@@ -162,4 +162,4 @@ Here is a table that lists the different tools Visual Studio offers and the diff
 |[JavaScript Memory](../profiling/javascript-memory.md)|no|yes for HTML, no for XAML|no|
 
 ## See also  
- [Debugging in Visual Studio](../debugger/debugging-in-visual-studio.md)
+ [Debugging in Visual Studio](../debugger/debugging-in-visual-studio.md)