Skip to content

Commit cc04477

Browse files
committed
really fixing filenames
1 parent 1f6dea7 commit cc04477

File tree

2 files changed

+5
-2
lines changed

2 files changed

+5
-2
lines changed

articles/trusted-signing/How-To-Signing-History.md

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -34,4 +34,6 @@ Follow the steps to access and send sign transactions to your storage account:
3434
6. Navigate to the storage account created in step 1. In this example, we will use storage account **storagetestneu1**. 
3535
7. From storage account resource, navigate to **Containers** under **Data storage**. 
3636
8. From the list, select container named **insights-logs-signtransactions** and navigate to the date and time you're looking to download the log.   
37-
37+
38+
39+

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

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -122,4 +122,5 @@ This section explains how to set up other not [SignTool](#set-up-signtool-with-t
122122

123123
* Azure PowerShell: App Control for Business CI Policy – To use Trusted Signing for CI policy signing follow the instructions at [Signing a New CI policy](./how-to-sign-ci-policy.md) and visit the [Az.CodeSigning PowerShell Module](/powershell/azure/install-azps-windows).
124124

125-
* Trusted Signing SDK – To create your own signing integration our [Trusted Signing SDK](https://www.nuget.org/packages/Azure.CodeSigning.Sdk) is publicly available.
125+
* Trusted Signing SDK – To create your own signing integration our [Trusted Signing SDK](https://www.nuget.org/packages/Azure.CodeSigning.Sdk) is publicly available.
126+

0 commit comments

Comments
 (0)