diff --git a/hub/apps/desktop/modernize/grant-identity-to-nonpackaged-apps.md b/hub/apps/desktop/modernize/grant-identity-to-nonpackaged-apps.md
index 979b026c9d..b1a58db3db 100644
--- a/hub/apps/desktop/modernize/grant-identity-to-nonpackaged-apps.md
+++ b/hub/apps/desktop/modernize/grant-identity-to-nonpackaged-apps.md
@@ -95,13 +95,15 @@ SignTool.exe sign /fd SHA256 /a /f <path to certificate>\MyCertificate.pfx /p <c
 
 Note: For how to build and sign the identity package within a CI/CD pipeline with production certificates, see the [MSIX and CI/CD Pipeline Overview](/windows/msix/desktop/cicd-overview) for examples.
 
-### Add identity metadata to your desktop application manifests
+## Add identity metadata to your desktop application manifests
 
 You connect the identity package with your application executables by including [application manifests](/windows/win32/sbscs/application-manifests) (a.k.a side-by-side or fusion manifests) with metadata that matches metadata from the identity package manifest.
 
-In Visual Studio, you can add an [application manifest](/windows/win32/sbscs/application-manifests) to an executable project by opening the **Project** context menu, and selecting **Add** > **New Item** > **Application Manifest File**.

+In Visual Studio, you can add an [application manifest](/windows/win32/sbscs/application-manifests) to an executable project by opening the **Project** context menu, and selecting **Add** > **New Item** > **Application Manifest File**.
+
+
+Below is an example application manifest snippet demonstrating the `msix` element required to connect your binaries with metadata from your identity package.
 
-Below is an example application manifest snippet demonstrating the `msix` element required to connect your binaries with metadata from your identity package.

 
 ```xml
 <?xml version="1.0" encoding="utf-8"?>