Skip to content

Commit 43b519b

Browse files
Update concept-trusted-signing-resources-roles.md- fix format prob
1 parent 12f169c commit 43b519b

File tree

1 file changed

+2
-3
lines changed

1 file changed

+2
-3
lines changed

articles/trusted-signing/concept-trusted-signing-resources-roles.md

Lines changed: 2 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -30,9 +30,8 @@ In the below example structure, notice that an Azure Subscription has a Resource
3030

3131
This ability to have multiple Code Signing Accounts and Certificate Profiles is useful as the service supports Public Trust, Private Trust, CI Policy, VBS Enclave, and Test signing types. For more information on the Certificate Profile types and how they're used, review [Trusted Signing certificate types and management](./concept-trusted-signing-cert-management.md).
3232

33-
34-
>[!NOTE]
35-
>Identity Validations and Certificate Profiles align with either Public or Private Trust. Meaning that a Public Trust Identity Validation is only used for Certificate Profiles that are used for the Public Trust model. For more information, review [Trusted Signing trust models](./concept-trusted-signing-trust-models.md).
33+
> [!NOTE]
34+
> Identity Validations and Certificate Profiles align with either Public or Private Trust. Meaning that a Public Trust Identity Validation is only used for Certificate Profiles that are used for the Public Trust model. For more information, review [Trusted Signing trust models](./concept-trusted-signing-trust-models.md).
3635
3736
### Trusted Signing account
3837

0 commit comments

Comments
 (0)