fixing typos and index cards

Author: microsoftshawarma

articles/trusted-signing/faq.yml

@@ -116,7 +116,7 @@ sections:
       - question: How do I fix pop-up credentials when using GCP?
         answer: |
           - Since GCP doesn't have Azure Managed Identity resource by default, an [Environment Credential](https://docs.microsoft.com/dotnet/api/azure.identity.defaultazurecredential?view=azure-dotnet) needs to be set up. 
-          Use the [EnvironmentCredential Class]https://docs.microsoft.com/dotnet/api/azure.identity.environmentcredential?view=azure-dotnet) to set up the credential. The recommendation is:
+          Use the [EnvironmentCredential Class](https://docs.microsoft.com/dotnet/api/azure.identity.environmentcredential?view=azure-dotnet) to set up the credential. The recommendation is:
           ```AZURE_TENANT_ID  The Microsoft Entra tenant(directory) ID. 
           AZURE_CLIENT_ID The client(application) ID of an App Registration in the tenant. 
           AZURE_CLIENT_SECRET A client secret that was generated for the App Registration. ````

articles/trusted-signing/index.yml

@@ -18,13 +18,7 @@ landingContent:
 # Cards and links should be based on top customer tasks or top subjects
 # Start card title with a verb
   # Card 
-  - title: Signing Integrations
-    linkLists:
-      - linkListType: how-to-guide
-        links:
-          - text: Implement Signing Integrations with Trusted Signing
-            url: how-to-signing-integrations.md
-  - title: CI Policy Signing
+  - title: How-To Guides
     linkLists:
       - linkListType: how-to-guide
         links:
@@ -48,6 +42,12 @@ landingContent:
         links:
           - text: Tutorial on assigning roles in the Trusted Signing service
             url: tutorial-assign-roles.md
+  - title: Quickstart with Trusted Signing
+    linkLists:
+      - linkListType: quickstart
+        links:
+          - text: Trusted Signing Quickstart
+            url: quickstart.md
   - title: Learn about Signing
     linkLists:
       - linkListType: concept

articles/trusted-signing/quickstart.md

@@ -34,12 +34,14 @@ The resources must be created in Azure regions where Trusted Signing is currentl
 | Region               | Region Class Fields  | Endpoint URI Value     |
 | :------------------- | :------------------- |:---------------|
 | East US              | EastUS               | <https://eus.codesigning.azure.net>  |
-| West US              |West US                | <https://wus.codesigning.azure.net>           |
+| West US3<sup>[1](#myfootnote1)</sup>              |West US3                | <https://wus3.codesigning.azure.net>           |
 | West Central US      | WestCentralUS                | <https://wcus.codesigning.azure.net/>              |
 | West US 2                 |   WestUS2                   | <https://wus2.codesigning.azure.net/>              |
 | North Europe              | NorthEurope               | <https://neu.codesigning.azure.net>  |
 | West Europe              | WestEurope               | <https://weu.codesigning.azure.net>  |
 
+<a name="myfootnote1">1</a>: WestUS3 coming soon!
+
 1. Sign in to the [Azure portal](https://portal.azure.com/).
 2. From either the Azure portal menu or the Home page, select **Create a resource**.
 3. In the Search box, enter **Trusted Signing account**.