chore(docs): Remove duplicative #license

Author: spbsoluble

README.md

@@ -94,11 +94,11 @@ The high level steps required to configure the Azure Keyvault Orchestrator exten
 
 1) [Configure the Azure Keyvault for client access](#configure-the-azure-keyvault-for-client-access)
 
-1) [Create the Store Type in Keyfactor](#create-the-store-type-in-keyfactor)
+1) [Create the Store Type in Keyfactor](#create-the-akv-certificate-store-type)
 
-1) [Install the Extension on the Orchestrator](#install-the-extension-on-the-orchestrator)
+1) [Install the Extension on the Orchestrator](#installation)
 
-1) [Create the Certificate Store](#create-the-certificate-store)
+1) [Create the Certificate Store](#add-a-new-or-existing-azure-keyvault-certificate-store)
 
 _Note that the certificate store type used by this Universal Orchestrator support for Azure Keyvault is not compatible
 with the certificate store type used by with Windows Orchestrator version for Azure Keyvault.
@@ -611,8 +611,6 @@ To use the Azure Key Vault Universal Orchestrator extension, you **must** create
 
     ![AKV Advanced Tab](docsource/images/AKV-advanced-store-type-dialog.png)
 
-    > For Keyfactor **Command versions 24.4 and later**, a Certificate Format dropdown is available with PFX and PEM options. Ensure that **PFX** is selected, as this determines the format of new and renewed certificates sent to the Orchestrator during a Management job. Currently, all Keyfactor-supported Orchestrator extensions support only PFX.
-
     #### Custom Fields Tab
     Custom fields operate at the certificate store level and are used to control how the orchestrator connects to the remote target server containing the certificate store to be managed. The following custom fields should be added to the store type:
 
@@ -679,7 +677,7 @@ To use the Azure Key Vault Universal Orchestrator extension, you **must** create
 
 
 
-> The above installation steps can be supplimented by the [official Command documentation](https://software.keyfactor.com/Core-OnPrem/Current/Content/InstallingAgents/NetCoreOrchestrator/CustomExtensions.htm?Highlight=extensions).
+> The above installation steps can be supplemented by the [official Command documentation](https://software.keyfactor.com/Core-OnPrem/Current/Content/InstallingAgents/NetCoreOrchestrator/CustomExtensions.htm?Highlight=extensions).
 
 
 
@@ -751,7 +749,7 @@ To use the Azure Key Vault Universal Orchestrator extension, you **must** create
         ```
     </details>
 
-> The content in this section can be supplimented by the [official Command documentation](https://software.keyfactor.com/Core-OnPrem/Current/Content/ReferenceGuide/Certificate%20Stores.htm?Highlight=certificate%20store).
+> The content in this section can be supplemented by the [official Command documentation](https://software.keyfactor.com/Core-OnPrem/Current/Content/ReferenceGuide/Certificate%20Stores.htm?Highlight=certificate%20store).
 
 
 ## Discovering Certificate Stores with the Discovery Job
@@ -925,10 +923,6 @@ If the Keyvault does not exist in Azure, and you would like to create it:
 
 ---
 
-#### License
-
-[Apache](https://apache.org/licenses/LICENSE-2.0)
-
 
 
 

docsource/content.md

@@ -662,8 +662,4 @@ If the Keyvault does not exist in Azure, and you would like to create it:
 > :warning: The identity you are using for authentication will need to have sufficient Azure permissions to be able to
 > create new Keyvaults.
 
----
-
-#### License
-
-[Apache](https://apache.org/licenses/LICENSE-2.0)
+---