Skip to content

Commit e1fe21d

Browse files
fixing typos in docs
1 parent 4a541bf commit e1fe21d

File tree

2 files changed

+4
-4
lines changed

2 files changed

+4
-4
lines changed

articles/trusted-signing/how-to-sign-ci-policy.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ author: microsoftshawarma
55
ms.author: rakiasegev
66
ms.service: trusted-signing
77
ms.topic: how-to
8-
ms.date: 04/04/2024
8+
ms.date: 06/03/2024
99
ms.custom: template-how-to-pattern
1010
---
1111

@@ -32,12 +32,12 @@ To complete the steps in this article, you need:
3232
Import-Module .\Az.CodeSigning.psd1
3333
```
3434

35-
1. Optionally, you can create a *metadata.json* file that looks like this example:
35+
1. Optionally, you can create a *metadata.json* file that looks like this example:(`"Endpoint"` URI value must be a URI that aligns with the region where you created your Trusted Signing account and certificate profile when you set up these resources.)
3636

3737
```json
3838
{
3939
"Endpoint":"https://xxx.codesigning.azure.net/",
40-
"TrustedSigningAccountName":"<Trusted Signing Account Name>",
40+
"CodeSigningAccountName":"<Trusted Signing Account Name>",
4141
"CertificateProfileName":"<Certificate Profile Name>"
4242
}
4343
```

articles/trusted-signing/how-to-signing-integrations.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -101,7 +101,7 @@ To sign by using Trusted Signing, you need to provide the details of your Truste
101101
{
102102
"Endpoint": "<Trusted Signing account endpoint>",
103103
"CodeSigningAccountName": "<Trusted Signing account name>",
104-
"CertificateProfileName": "<certificate profile name>",
104+
"CertificateProfileName": "<Certificate profile name>",
105105
"CorrelationId": "<Optional CorrelationId value>"
106106
}
107107
```

0 commit comments

Comments
 (0)