From 1579c709eb48dc002a14730047d72f66a9e2c8c7 Mon Sep 17 00:00:00 2001
From: Mike Battista <13860912+mikebattista@users.noreply.github.com>
Date: Tue, 15 Apr 2025 13:27:25 -0400
Subject: [PATCH 1/2] Added note about adding an application manifest file in
 Visual Studio.

---
 .../desktop/modernize/grant-identity-to-nonpackaged-apps.md | 6 ++++--
 1 file changed, 4 insertions(+), 2 deletions(-)

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 662a961346..131a4b214b 100644
--- a/hub/apps/desktop/modernize/grant-identity-to-nonpackaged-apps.md
+++ b/hub/apps/desktop/modernize/grant-identity-to-nonpackaged-apps.md
@@ -18,7 +18,7 @@ To build and register an identity package, follow these steps:
 
 1. [Create a package manifest for the identity package](#create-a-package-manifest-for-the-identity-package)
 2. [Build and sign the identity package](#build-and-sign-the-identity-package)
-3. [Add identity metadata to your desktop application manifest](#add-identity-metadata-to-your-desktop-application-manifest)
+3. [Add identity metadata to your desktop application manifests](#add-identity-metadata-to-your-desktop-application-manifests)
 4. [Register the identity package in your installer](#register-the-identity-package-in-your-installer)
 
 ## Create a package manifest for the identity package
@@ -95,10 +95,12 @@ 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 manifest
+### 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.
+
 Below is an example [application manifest](/windows/win32/sbscs/application-manifests) snippet demonstrating the `msix` element required to connect your binaries with metadata from your identity package.
 
 ```xml

From 43f01c8d7b549fd78ba1a376998cd5492f188543 Mon Sep 17 00:00:00 2001
From: Steven White <31261191+stevewhims@users.noreply.github.com>
Date: Tue, 15 Apr 2025 10:53:28 -0700
Subject: [PATCH 2/2] Update formatting

---
 .../desktop/modernize/grant-identity-to-nonpackaged-apps.md   | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

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 131a4b214b..979b026c9d 100644
--- a/hub/apps/desktop/modernize/grant-identity-to-nonpackaged-apps.md
+++ b/hub/apps/desktop/modernize/grant-identity-to-nonpackaged-apps.md
@@ -99,9 +99,9 @@ Note: For how to build and sign the identity package within a CI/CD pipeline wit
 
 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](/windows/win32/sbscs/application-manifests) 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"?>