Updated PC offer topics

Author: emuench

articles/marketplace/TOC.yml

@@ -475,7 +475,7 @@
         - name: Create Azure VM technical asset
           items:
             - name: Create Azure VM technical asset
-              href: ./partner-center-portal/create-azure-container-technical-assets.md
+              href: ./partner-center-portal/create-azure-container-technical-asset.md
             - name: Azure VM technical asset FAQ
               href: ./partner-center-portal/common-issues-during-vhd-creation.md
             - name: Certify Azure VM image

articles/marketplace/partner-center-portal/azure-vm-create-offer.md

@@ -451,7 +451,7 @@ Open public or private ports on a deployed virtual machine.
 
 #### Properties
 
-**Support accelerated networking** – Select if your VM supports [accelerated](https://go.microsoft.com/fwlink/?linkid=2124513)[networking](https://go.microsoft.com/fwlink/?linkid=2124513).
+**Support accelerated networking** – Select if your VM supports [accelerated networking](https://go.microsoft.com/fwlink/?linkid=2124513).
 
 #### VM Images
 

articles/marketplace/partner-center-portal/common-sas-uri-issues.md

@@ -12,19 +12,19 @@ ms.date: 04/09/2020
 # Common SAS URI issues and fixes
 
 > [!IMPORTANT]
-> We're moving the management of your Azure Virtual Machine offers from Cloud Partner Portal to Partner Center. Until your offers are migrated, please follow the instructions in [Common SAS URL issues and fixes](https://docs.microsoft.com/azure/marketplace/cloud-partner-portal/virtual-machine/cpp-common-sas-url-issues) for Cloud Partner Portal to manage your offers.
+> We're moving the management of your Azure Virtual Machine offers from Cloud Partner Portal to Partner Center. Until your offers are migrated, please follow the instructions in [Common SAS URI issues and fixes](https://docs.microsoft.com/azure/marketplace/cloud-partner-portal/virtual-machine/cpp-common-sas-url-issues) for Cloud Partner Portal to manage your offers.
 
 Following are common issues encountered when working with shared access signatures (which are used to identify and share the uploaded VHDs for your solution), along with suggested resolutions.
 
 | **Issue** | **Failure Message** | **Fix** |
 | --------- | ------------------- | ------- |
 | *Failure in copying images* |  |  |
-| "?" is not found in SAS URL | `Failure: Copying Images. Not able to download blob using provided SAS Uri.` | Update the SAS URI using recommended tools. |
-| "st" and "se" parameters not in SAS URL | `Failure: Copying Images. Not able to download blob using provided SAS Uri.` | Update the SAS URI with proper **Start Date** and **End Date** values. |
+| "?" is not found in SAS URI | `Failure: Copying Images. Not able to download blob using provided SAS Uri.` | Update the SAS URI using recommended tools. |
+| "st" and "se" parameters not in SAS URI | `Failure: Copying Images. Not able to download blob using provided SAS Uri.` | Update the SAS URI with proper **Start Date** and **End Date** values. |
 | "sp=rl" not in SAS URI | `Failure: Copying Images. Not able to download blob using provided SAS Uri.` | Update the SAS URI with permissions set as `Read` and `List`. |
 | SAS URI has white spaces in VHD name | `Failure: Copying Images. Not able to download blob using provided SAS Uri.` | Update the SAS URI to remove white spaces. |
 | SAS URI Authorization error | `Failure: Copying Images. Not able to download blob due to authorization error.` | Review and correct the SAS URI format. Regenerate if necessary. |
-| SAS URI "st" and "se" parameters do not have full date-time specification | `Failure: Copying Images. Not able to download blob due to incorrect SAS URI.` | SAS URI **Start Date** and **End Date** parameters (`st` and `se` substrings) must have full date-time format, such as `11-02-2017T00:00:00Z`. Shortened versions are invalid (some commands in Azure CLI may generate shortened values by default). |
+| SAS URI "st" and "se" parameters do not have full date-time specification | `Failure: Copying Images. Not able to download blob due to incorrect SAS Uri.` | SAS URI **Start Date** and **End Date** parameters (`st` and `se` substrings) must have full date-time format, such as `11-02-2017T00:00:00Z`. Shortened versions are invalid (some commands in Azure CLI may generate shortened values by default). |
 |  |  |  |
 
 For details, see [Using shared access signatures (SAS)](https://azure.microsoft.com/documentation/articles/storage-dotnet-shared-access-signature-part-1/).

articles/marketplace/partner-center-portal/create-azure-vm-technical-asset.md

@@ -132,7 +132,7 @@ To connect to a Linux-based VM, you need a secure shell protocol (SSH) client. T
 7. Open the PuTTY application.
 8. In the PuTTY Configuration dialog, enter the IP address or DNS name of your VM.
 
-        :::image type="content" source="media/avm-putty.png" alt-text="Illustrates the PuTTY terminal settings. the Host Name or IP address and Port boxes are highlighted.":::
+    :::image type="content" source="media/avm-putty.png" alt-text="Illustrates the PuTTY terminal settings. the Host Name or IP address and Port boxes are highlighted.":::
 
 9. Select **Open** to open a PuTTY terminal.
 10. When prompted, enter the account name and password of your Linux VM account.
@@ -166,7 +166,7 @@ Create your image using either the Azure Portal or Azure PowerShell.
 1. On the home page, select **Create a resource**, search for "Template Deployment", and select **Create**.
 2. Choose **Build your own template in the editor**.
 
-        :::image type="content" source="media/avm-custom-deployment.png" alt-text="Illustrates the Custom deployment page.":::
+    :::image type="content" source="media/avm-custom-deployment.png" alt-text="Illustrates the Custom deployment page.":::
 
 3. Paste this [JSON template](https://docs.microsoft.com/azure/marketplace/cloud-partner-portal/virtual-machine/cpp-deploy-json-template) into the editor and select **Save**.
 4. Provide the parameter values for the displayed **Custom deployment** property pages.