Update docs/ide/managing-assembly-and-manifest-signing.md

Author: ghogen

docs/ide/managing-assembly-and-manifest-signing.md

@@ -58,7 +58,7 @@ For .NET Core (and .NET 5 and later) C# projects in Visual Studio 2022:
 1. Under **Build**, look for **Strong naming**, and select the **Sign the assembly** checkbox. Additional options for the key file and delay signing appear when you check the box.
 1. Specify a key file.
 
-If you don't have a key file, you can use the command line to [create an `.snk` file](/dotnet/standard/assembly/create-public-private-key-pair). You can also use or generate a certificate in a `.pfx` file using the **Publish** process, and in the **Sign manifests** step, you can create a test certificate, or use a production certificate, such as one issued by your IT department. See [Deploy a .NET Windows Desktop app with ClickOnce](../deployment/quickstart-deploy-using-clickonce-folder.md).
+If you don't have a key file, you can use the command line to [create an `.snk` file](/dotnet/standard/assembly/create-public-private-key-pair). You can also use or generate a certificate in a `.pfx` file using the **Publish** process, and in the **Sign manifests** step, you can create a test certificate to use only during development and testing, or for production, use a certificate issued by your IT department or by an authorized source. See [Deploy a .NET Windows Desktop app with ClickOnce](../deployment/quickstart-deploy-using-clickonce-folder.md).
 
 For .NET Framework and Visual Basic projects in Visual Studio 2022, or in Visual Studio 2019: