Adding aka.ms links

Author: RoseHJM

articles/deployment-environments/concept-extensibility-model.md

@@ -13,12 +13,12 @@ ms.date: 10/17/2024
 
 # What is the ADE Extensibility Model?
 
-Azure Deployment Environments (ADE) enables you to provide a curated set of infrastructure-as-code (IaC) templates that your development teams use to perform deployments. ADE offers power and flexibility for organizations through an extensibility model which enables platform engineers to define pre-approved templates using their preferred IaC framework.
-The following diagram shows the full workflow for ADE. The catalog stores IaC templates, which reference container images for use in deployments. Platform engineers curate these images and templates, and configure environment settings based on the stage of development, enabling developers to create highly specific deployment environments. Developers can create ad hoc environments for dev/test purposes or shared environments as part of their CI/CD pipeline, or as part of an automated pipeline.
+Azure Deployment Environments (ADE) enables you to provide a curated set of infrastructure-as-code (IaC) templates that your development teams use to perform deployments. ADE offers power and flexibility for organizations through an extensibility model which enables platform engineers to define preapproved templates using their preferred IaC framework.
+The following diagram shows the full workflow for ADE. The catalog stores IaC templates, which reference container images for use in deployments. Platform engineers curate these images and templates, and configure environment settings based on the stage of development, enabling developers to create highly specific deployment environments. Developers can create improvised environments for dev/test purposes or shared environments as part of their CI/CD pipeline, or as part of an automated pipeline.
 
 :::image type="content" source="media/concept-extensibility-model/deployment-environments-overview.svg" alt-text="tezr":::
 
-The extensibility model enables platform engineers to define the app infrastructure using their preferred IaC framework including ARM, Bicep, Terraform, and Pulumi. Platform engineers create and customize container images for different scenarios. They push these images to a container registry and reference them in the environment definition’s metadata file. This ensures that whenever a deployment is made, the deployment execution happens based on how the container image is configured. The following diagram shows the relationship between the custom images stored in a container registry, and the environment definition within the catalog. 
+The extensibility model enables platform engineers to define the app infrastructure using their preferred IaC framework including Azure Resource Manager (ARM), Bicep, Terraform, and Pulumi. Platform engineers create and customize container images for different scenarios. They push these images to a container registry and reference them in the environment definition’s metadata file. This ensures that whenever a deployment is made, the deployment execution happens based on how the container image is configured. The following diagram shows the relationship between the custom images stored in a container registry, and the environment definition within the catalog. 
 
 :::image type="content" source="media/concept-extensibility-model/extensibility-model-detail.svg" alt-text="tetet":::
 
@@ -30,49 +30,35 @@ You can choose from multiple options for creating and building custom images, de
 **1. Use a standard image**
 For first party frameworks - ARM and Bicep - ADE provides standard images that customers can take advantage of and can just use identifiers ARM or Bicep to configure the respective IaC template as an environment definition. For ARM or Bicep deployments, you can use the standard image by referencing it in the environment.yaml file and defining resources in the template file (*azuredeploy.json*, *main.bicep*).
 
-For instructions, see: aka.ms/arm-bicep-standard.
+For instructions, see: [Use a standard container image](aka.ms/arm-bicep-standard).
 
 **1. Create a custom image using a script**
 To make the process of building a custom image and pushing it to a container registry easier, Microsoft provides a script that builds and pushes the image to a registry that you specify. 
 
-For instructions, see: aka.ms/arm-bicep-custom-script.
+For instructions, see: [Create a custom container image by using a script](aka.ms/arm-bicep-custom-script).
 
 **1. Create a custom image manually**
 For more complex scenarios, start with the standard image and customize it by installing software packages and adjusting settings. Build the image and upload it to a container registry where ADE can access it. Specify the image's location in the environment.yaml file.
 
-For instructions, see: aka.ms/arm-bicep-custom.
+For instructions, see: [Create a custom container image manually](aka.ms/arm-bicep-custom-manual).
 
 ### Terraform
-**1. Leverage a GitHub workflow to create Terraform specific container image**
-You can leverage the published GitHub workflow to help create a container image that is Terraform specific. You can upload the new image to a container registry and use it by referencing it in the environment.yaml file and defining resources in the template file (*main.tf*).
-
-For instructions, see: aka.ms/terraform-workflow-standard.
-
-**1. Create a Terraform specific container image with a script**
-You can use a GitHub workflow to create a custom Terraform image that includes the software, settings, and other customizations you need for your Terraform specific image. You can then upload the new image to a container registry and use it by referencing it in the environment.yaml file.
-
-For instructions, see: aka.ms/terraform-workflow-custom.
 
 **1. Create a Terraform specific container image manually**
 You can use a GitHub workflow to create a custom Terraform image that includes the software, settings, and other customizations you need for your Terraform specific image. You can then upload the new image to a container registry and use it by referencing it in the environment.yaml file.
 
-For instructions, see: aka.ms/terraform-workflow-custom.
+For instructions, see: [Create a container image using a GitHub workflow](aka.ms/terraform-workflow-custom-manual).
 
 ### Pulumi
 **1. Use a standard image**
 The Pulumi team provides a prebuilt image to get you started, which you can use directly from your ADE environment definitions. For Pulumi images, you can use the standard image by referencing it in the environment.yaml file and defining the resources to deploy in the project file (*pulumi.yaml*).
 
-For instructions, see: aka.ms/pulumi-standard.
-
-**1. Create a custom image using a script**
-To make the process of building a custom image and pushing it to a container registry easier, Pulumi provides a script that builds and pushes the image to a registry that you specify. 
-
-For instructions, see: aka.ms/pulumi-custom-script.
+For instructions, see: [Use a standard container image provided by Pulumi](aka.ms/pulumi-standard).
 
 **1. Create a custom image manually**
 For more complex scenarios, start with the standard image and customize it by installing software packages and adjusting settings. Build the image and upload it to a container registry where ADE can access it. Specify the image's location in the environment.yaml file.
 
-For instructions, see: aka.ms/pulumi-custom.
+For instructions, see: [Create a custom image](aka.ms/pulumi-custom-manual).
 
 ## Related content 
 

articles/deployment-environments/how-to-configure-extensibility-model-custom-image.md

@@ -47,7 +47,7 @@ You can take one of the following approaches to use container images with ADE:
 
 ## Use a standard container image
 
-ADE supports ARM and Bicep without requiring any extra configuration. You can create an environment definition that deploys Azure resources for a deployment environment by adding the template files (like *azuredeploy.json* and *environment.yaml*) to your catalog. ADE then uses the standard ARM-Bicep container image to create the deployment environment.
+ADE supports Azure Resource Manager (ARM) and Bicep without requiring any extra configuration. You can create an environment definition that deploys Azure resources for a deployment environment by adding the template files (like *azuredeploy.json* and *environment.yaml*) to your catalog. ADE then uses the standard ARM-Bicep container image to create the deployment environment.
 
 In the *environment.yaml* file, the `runner` property specifies the location of the container image you want to use. To use the standard image published on the Microsoft Artifact Registry, use the respective identifiers `runner`.
 
@@ -109,7 +109,7 @@ You can take one of the following approaches to use container images with ADE:
 - **Create a custom container image:** You can create a workflow that creates a Terraform specific image customized with all the software, settings, and configuration that you need.
  
 
-## Create a container image leveraging a GitHub workflow
+## Create a container image using a GitHub workflow
 Creating a custom container image allows you to customize your deployments to fit your requirements. You can create custom images based on the ADE standard images.
 
 After you complete the image customization, you must build the image and push it to your container registry.