fixing reviewer feedback in other articles

ianjmcm · ianjmcm · commit 50356484f526 · 2024-04-11T13:34:33.000-04:00
diff --git a/articles/trusted-signing/How-To-Certificate-Revocation.md b/articles/trusted-signing/How-To-Certificate-Revocation.md
@@ -1,11 +1,11 @@
 ---
-title: Revoke a certificate profile in Trusted Signing #Required; page title displayed in search results. Include the word "quickstart". Include the brand.
-description: how-to revoke a Trusted Signing certificate from Azure portal. #Required; article description that is displayed in search results. Include the word "quickstart".
-author: mehasharma #Required; your GitHub user alias, with correct capitalization.
-ms.author: mesharm #Required; microsoft alias of author; optional team alias.
-ms.service: trusted-signing #Required; service per approved list. service slug assigned to your service by ACOM.
-ms.topic: how-to #Required; leave this attribute/value as-is.
-ms.date: 03/31/2024 #Required; mm/dd/yyyy format.
+title: Revoke a certificate profile in Trusted Signing 
+description: how-to revoke a Trusted Signing certificate from Azure portal. 
+author: mehasharma 
+ms.author: mesharm 
+ms.service: azure-code-signing 
+ms.topic: how-to 
+ms.date: 03/31/2024 
 ---
 
 
diff --git a/articles/trusted-signing/How-To-Signing-History.md b/articles/trusted-signing/How-To-Signing-History.md
@@ -1,16 +1,16 @@
 ---
-title: Access signed transactions in Trusted Signing #Required; page title displayed in search results. Include the word "quickstart". Include the brand.
-description: How-to access signed transactions in Trusted Signing in Azure portal. #Required; article description that is displayed in search results. Include the word "quickstart".
-author: mehasharma #Required; your GitHub user alias, with correct capitalization.
-ms.author: mesharm #Required; microsoft alias of author; optional team alias.
-ms.service: trusted-signing #Required; service per approved list. service slug assigned to your service by ACOM.
-ms.topic: how-to #Required; leave this attribute/value as-is.
-ms.date: 04/01/2024 #Required; mm/dd/yyyy format.
+title: Access signed transactions in Trusted Signing 
+description: How-to access signed transactions in Trusted Signing in Azure portal. 
+author: mehasharma 
+ms.author: mesharm 
+ms.service: azure-code-signing 
+ms.topic: how-to 
+ms.date: 04/01/2024 
 ---
 
 # Access signed transactions in Trusted Signing
 
-Review the details of the signing requests executed by Trusted Signing in Azure Portal. 
+Review the details of the signing requests executed by Trusted Signing in Azure portal. 
 Currently there are four different options enabled:  
 - Log Analytics workspace  
 - Storage Account  
diff --git a/articles/trusted-signing/TOC.yml b/articles/trusted-signing/TOC.yml
@@ -12,6 +12,10 @@
       href: how-to-signing-integrations.md
     - name: Sign CI Policies with Trusted Signing
       href: how-to-sign-ci-policy.md
+    - name: Access signed transactions in Trusted Signing 
+      href: how-to-signing-history.md
+    - name: Revoke a certificate profile in Trusted Signing
+      href: how-to-certificate-revocation.md
   - name: Quickstart
     items:
     - name: Quickstart onboarding
diff --git a/articles/trusted-signing/how-to-sign-ci-policy.md b/articles/trusted-signing/how-to-sign-ci-policy.md
@@ -1,12 +1,12 @@
 ---
-title: Signing CI Policies #Required; page title is displayed in search results. Include the brand.
-description: Learn how to sign new CI policies with Trusted Signing. #Required; article description that is displayed in search results. 
-author: microsoftshawarma #Required; your GitHub user alias, with correct capitalization.
-ms.author: rakiasegev #Required; microsoft alias of author; optional team alias.
-ms.service: azure-code-signing #Required; service per approved list. slug assigned by ACOM.
-ms.topic: how-to #Required; leave this attribute/value as-is.
-ms.date: 04/04/2024 #Required; mm/dd/yyyy format.
-ms.custom: template-how-to-pattern #Required; leave this attribute/value as-is.
+title: Signing CI Policies 
+description: Learn how to sign new CI policies with Trusted Signing.  
+author: microsoftshawarma 
+ms.author: rakiasegev 
+ms.service: azure-code-signing 
+ms.topic: how-to 
+ms.date: 04/04/2024 
+ms.custom: template-how-to-pattern 
 ---
 
 # Sign CI Policies with Trusted Signing
diff --git a/articles/trusted-signing/how-to-signing-integrations.md b/articles/trusted-signing/how-to-signing-integrations.md
@@ -1,12 +1,12 @@
 ---
-title: Implement signing integrations with Trusted Signing #Required; page title is displayed in search results. Include the brand.
-description: Learn how to set up signing integrations with Trusted Signing. #Required; article description that is displayed in search results. 
-author: microsoftshawarma #Required; your GitHub user alias, with correct capitalization.
-ms.author: rakiasegev #Required; microsoft alias of author; optional team alias.
-ms.service: azure-code-signing #Required; service per approved list. slug assigned by ACOM.
-ms.topic: how-to #Required; leave this attribute/value as-is.
-ms.date: 04/04/2024 #Required; mm/dd/yyyy format.
-ms.custom: template-how-to-pattern #Required; leave this attribute/value as-is.
+title: Implement signing integrations with Trusted Signing 
+description: Learn how to set up signing integrations with Trusted Signing.  
+author: microsoftshawarma 
+ms.author: rakiasegev 
+ms.service: azure-code-signing 
+ms.topic: how-to
+ms.date: 04/04/2024 
+ms.custom: template-how-to-pattern 
 ---
 
 # Implement Signing Integrations with Trusted Signing
@@ -46,15 +46,15 @@ To download and install SignTool:
 1.	Download the latest version of SignTool + Windows Build Tools NuGet at: [Microsft.Windows.SDK.BuildTools](https://www.nuget.org/packages/Microsoft.Windows.SDK.BuildTools/)
 2.	Install SignTool from Windows SDK (min version: 10.0.2261.755)
 
- Another option is to use the latest nuget.exe to download and extract the latest SDK Build Tools NuGet package by completing the following steps (PowerShell):
+ Another option is to use the latest `nuget.exe` to download and extract the latest SDK Build Tools NuGet package by completing the following steps (PowerShell):
 
-1.	Download nuget.exe by running the following download command:  
+1.	Download `nuget.exe` by running the following download command:  
 
 ```
 Invoke-WebRequest -Uri https://dist.nuget.org/win-x86-commandline/latest/nuget.exe -OutFile .\nuget.exe  
 ```
 
-2.	Install nuget.exe by running the following install command:
+2.	Install `nuget.exe` by running the following install command:
 ```
 .\nuget.exe install Microsoft.Windows.SDK.BuildTools -Version 10.0.20348.19 
 ```
diff --git a/articles/trusted-signing/index.yml b/articles/trusted-signing/index.yml
@@ -30,6 +30,12 @@ landingContent:
         links:
           - text: Sign CI Policies with Trusted Signing
             url: how-to-sign-ci-policy.md
+          - text: Signing Integrations with Trusted Signing
+            url: how-to-signing-integrations.md
+          - text: Access signed transactions in Trusted Signing 
+            url: how-to-sign-history.md
+          - text: Revoke a certificate profile in Trusted Signing
+            url: how-to-certificate-revocation.md
   - title: Overview
     linkLists:
         - linkListType: overview
diff --git a/articles/trusted-signing/quickstart.md b/articles/trusted-signing/quickstart.md
@@ -61,7 +61,7 @@ The resources must be created in Azure regions where Trusted Signing is currentl
 - Globally unique.
 - Case insensitive (“Abc” is the same as “abc”).
 
-# [Az CLI](#tab/account-cli)
+# [Azure CLI](#tab/account-cli)
 
 The resources must be created in Azure regions where Trusted Signing is currently available. Refer to the table below for the current Azure regions with Trusted Signing resources: 
 
@@ -91,7 +91,7 @@ az upgrade [--all {false, true}]
    [--allow-preview {false, true}]
     [--yes]
 ```
-5.  To set your default subscription id, use the `az account set -s <subscriptionId>` command. 
+5.  To set your default subscription ID, use the `az account set -s <subscriptionId>` command. 
 
 6.  Create a resource group using the following command:
 ```
@@ -130,7 +130,7 @@ You can complete your own Identity Validation by filing out the request form wit
 Here are the steps to create an Identity Validation request:
 1.  Navigate to your new Trusted Signing account in the Azure portal.
 2.  Confirm you have the **Trusted Signing Identity Verifier role**. 
-•   For role Based Access management (RBAC) access management, see link to RBAC and role assignment.
+•   For Role Based Access management (RBAC) access management, see link to RBAC and role assignment.
 3.  From either the Trusted Signing account overview page or from Objects, select **Identity Validation**.
 4.  Select **New Identity Validation** > Public or Private. 
     - Public identity validation is applicable to certificate profile types: Public Trust, Public Trust Test, VBS Enclave (this isn't supported yet).
@@ -224,7 +224,7 @@ trustedsigning certificate-profile show -g myRG --account-name MyAccount -n  MyP
 - Begin with a letter, end with a letter or digit, and not contain consecutive hyphens.
 - Unique within the account.
 - Inherits region from the account.
-- Case insensitive (“Abc” is the same as “abc”) .
+- Case insensitive (“Abc” is the same as “abc”).
 
 **Helpful commands**:
 - Show help for sample commands and detailed parameter descriptions:   `trustedsigning certificate-profile create -–help`
