Skip to content

Commit 04d418e

Browse files
authored
deleting duplicate terms
1 parent 2fb8978 commit 04d418e

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

articles/deployment-environments/best-practice-catalog-structure.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -28,7 +28,7 @@ The following diagram shows the recommended structure for a repo. Each template
2828
In a linked environment definitions scenario, multiple .json files can point to a single ARM template. ADE checks linked environment definitions sequentially and retrieves the linked files and environment definitions from the repository. For best performance, these interactions should be minimized.
2929

3030
## Update environment definitions and sync changes
31-
Over time, environment definitions environment definitions need updates. You make those updates in your Git repository, and then you must manually sync the catalog up to update the changes to ADE.
31+
Over time, environment definitions need updates. You make those updates in your Git repository, and then you must manually sync the catalog up to update the changes to ADE.
3232

3333
## Files outside recommended structure
3434
In the following example, the Azuredeploy.json file is above the environment.yaml file in the folder structure. This structure is not valid Azure Deployment Environments catalogs. Environment definitions cannot reference content outside of the catalog item folder.

0 commit comments

Comments
 (0)