add changes to faq

Author: TacoTechSharma

articles/trusted-signing/faq.yml

@@ -148,22 +148,22 @@ sections:
           | :------------------- | :------------------- |
           | 400          | An Azure authentication error. This error is due to caching of certificates. Add `"ExcludeCredentials": ["SharedTokenCacheCredential"]` to your JSON file. For more information, see [DefaultAzureCredential Class (Azure.Identity)](/dotnet/api/azure.identity.defaultazurecredential?view=azure-dotnet). |
           | 401          |  You aren't authenticated. Sign out and sign back in. |
-          | 403          | - Check Trusted Signing role. <br>     
-                           - Check Trusted Signing account name and Trusted Signing Certificate profile name in your metadata.json. <br>
-                          - Check dlib and dlib path. <br>
-                          - Install C++ Redistributables: Download link: https://docs.microsoft.com/en-us/cpp/windows/latest-supported-vc-redist?view=msvc-170. <br>
-                          - Check .Net version, dlib version, and Windows SDK version. <br>
-                          - Check if Trusted Signing role is assigned to the identity trying to sign the file. <br>
-                          - Check if the corresponding Identity Validation is in "Completed" state. <br>
-                          - Verify if you access the Trusted Signing endpoint from this VM or machine?Try executing the action on a different VM or machine. It can be a potential network issue. <br>
-                          - For Private Trust scenarios 403: The user object ID to do the signing is different than the user object ID to call the  Get-azCodeSigningRootCert. The appropriate object ID needs to have the role “Trusted Signing Certificate Profile Signer.|
           | 404          |  Ensure that no changes were made to your configuration or firewalls rules. |
           | "MsalUiRequiredException"           |  Typically occurs due to the local cache. The error resolves after the cache is refreshed from Azure. |
           | No certificates were found that met all the given criteria.         |  Check the dlib path, dlib version, dlib name, filename, and SignTool version. This error means that it's trying to pull certificates from your local machine and not by using Trusted Signing certificates. |
           | Error: SignerSign() failed." (-2147024846/0x80070032)           |  Ensure that you're using the latest version of SignTool. |
           | Error code (-2147024885/0x8007000b)            |  For MSIX signing, indicates that the publisher in the manifest file doesn't match the certificate subject. Check the publisher that's listed in the manifest file. |
           | No error codes, SignTool silently fails          |  Ensure that the relevant .NET runtime version is installed. |
           | Azure.Identity.CredentialUnavailableException         |  You might see this error in [environments outside Azure](https://github.com/Azure/azure-sdk-for-net/issues/29471). If you are working outside of Azure, we recommend that you add "exclude ManagedIdentity". |
+          | 403          | - Check Trusted Signing role.      
+                           - Check Trusted Signing account name and Trusted Signing Certificate profile name in your metadata.json. 
+                          - Check dlib and dlib path. 
+                          - Install C++ Redistributables: Download link: https://docs.microsoft.com/en-us/cpp/windows/latest-supported-vc-redist?view=msvc-170.
+                          - Check .NET version, dlib version, and Windows SDK version. 
+                          - Check if Trusted Signing role is assigned to the identity trying to sign the file. 
+                          - Check if the corresponding Identity Validation is in "Completed" state.
+                          - Verify if you access the Trusted Signing endpoint from this VM or machine?Try executing the action on a different VM or machine. It can be a potential network issue. 
+                          - For Private Trust scenarios 403: The user object ID to do the signing is different than the user object ID to call the  Get-azCodeSigningRootCert. The appropriate object ID needs to have the role “Trusted Signing Certificate Profile Signer.|
   - name: Cost Management and Billing
     questions:  
        - question: How do I view usage costs and billing information for Trusted Signing resources?

articles/trusted-signing/quickstart.md

@@ -254,14 +254,15 @@ To create an identity validation request:
 | :------------------- | :------------------- |
 | Onboarding           | Trusted Signing at this time can onboard only legal business entities that have verifiable tax history of three or more years. For a quicker onboarding process, ensure that public records for the legal business entity that you're validated are up to date. |
 | Accuracy             | Ensure that you provide the correct information for public identity validation. If you need to make any changes after it is created, you must complete a new identity validation request. This change affects the associated certificates that are being used for signing. |
-| More documentation            | If we need more documentation to process the identity validation request, you're notified through email. You can upload the documents in the Azure portal. The documentation request email contains information about file size requirements. Ensure that any documents you provide are the most current. 
-- All documents submitted must be issued within the previous 12 months or where the expiration date is a future date that is at least two months away.<br>
- - If it is not possible to provide additional documentation, please update your account information to match any legal documents already provided or your official Company registration details. <br> 
- - When providing official business document, such as business registration form, business charter, or articles of incorporation that list the company name and address as it is provided at the time of Identity Validation request creation.<br>
- - Ensure the domain registration or domain invoice from registration or renewal that lists the entity/contact name and domain as it is state on the request.
 | Failed email verification            | If email verification fails, you must initiate a new identity validation request. |
 | Identity validation status            | You're notified through email when there's an update to the identity validation status. You can also check the status in the Azure portal at any time. |
 | Processing time            | Processing your identity validation request takes from 1 to 7 business days (possibly longer if we need to request more documentation from you). |
+| More documentation            | If we need more documentation to process the identity validation request, you're notified through email. You can upload the documents in the Azure portal. The documentation request email contains information about file size requirements. Ensure that any documents you provide are the most current. 
+- All documents submitted must be issued within the previous 12 months or where the expiration date is a future date that is at least two months away.
+ - If it is not possible to provide additional documentation, please update your account information to match any legal documents already provided or your official Company registration details. 
+ - When providing official business document, such as business registration form, business charter, or articles of incorporation that list the company name and address as it is provided at the time of Identity Validation request creation.
+ - Ensure the domain registration or domain invoice from registration or renewal that lists the entity/contact name and domain as it is state on the request.</ul>|                                                            
+
 
 
 ## Create a certificate profile