Skip to content

Commit 07702ba

Browse files
authored
Update concept-azure-developer-cli-with-deployment-environments.md
1 parent 117e241 commit 07702ba

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

articles/deployment-environments/concept-azure-developer-cli-with-deployment-environments.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -31,7 +31,7 @@ At scale, using ADE and `azd` together enables you to provide a way for develope
3131

3232
The Azure Developer CLI commands are designed to work with standardized templates. Each template is a code repository that adheres to specific file and folder conventions. The templates contain the assets `azd` needs to provision an Azure Deployment Environment environment. When you run a command like `azd up`, the tool uses the template assets to execute various workflow steps, such as provisioning or deploying resources to Azure.
3333

34-
The following is a typical `azd` template structure:
34+
The following is a typical template structure:
3535

3636
```txt
3737
├── infra [ Contains infrastructure as code files ]
@@ -46,7 +46,7 @@ The following is a typical `azd` template structure:
4646

4747
All `azd` templates include the following assets:
4848

49-
- *infra folder* - Contains all of the Bicep or Terraform infrastructure as code files for the azd template. The infra folder is not used in `azd` with ADE. ADE provides the infrastructure as code files for the `azd` template. You don't need to include these files in your `azd` template.
49+
- *infra folder* - The infra folder is not used in `azd` with ADE. It contains all of the Bicep or Terraform infrastructure as code files for the azd template. ADE provides the infrastructure as code files for the `azd` template. You don't need to include these files in your `azd` template.
5050

5151
- *azure.yaml file* - A configuration file that defines one or more services in your project and maps them to Azure resources for deployment. For example, you might define an API service and a web front-end service, each with attributes that map them to different Azure resources for deployment.
5252

@@ -107,4 +107,4 @@ When the dev center feature is enabled, the default behavior of some common azd
107107

108108
- [Add and configure an environment definition](./configure-environment-definition.md)
109109
- [Create an environment by using the Azure Developer CLI](./how-to-create-environment-with-azure-developer.md)
110-
- [Make your project compatible with Azure Developer CLI](/azure/developer/azure-developer-cli/make-azd-compatible?pivots=azd-create)
110+
- [Make your project compatible with Azure Developer CLI](/azure/developer/azure-developer-cli/make-azd-compatible?pivots=azd-create)

0 commit comments

Comments
 (0)