edits

Author: v-albemi

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

@@ -13,12 +13,13 @@ ms.date: 03/20/2025
 
 # Best practices for Azure Deployment Environment catalogs
 
-This article describes the best practice guidelines for structuring an Azure Deployment Environments catalog.
+This article describes best practices for structuring an Azure Deployment Environments catalog.
 
 ## Structure the catalog for efficient caching
-As a platform engineer, you should structure your catalog in a way that makes it easier and quicker for Azure Deployment Environments to find and cache environment definitions efficiently. By organizing the repository into a specific structure, you can better target files for caching and improve the overall performance of the deployment process. It's essential for platform engineers to understand these guidelines and structure their repositories accordingly to ensure optimal results.
 
-When you attach a catalog to a dev center, Deployment Environments scans the catalog for an environment.yaml file. On locating the file, ADE assumes the files in that folder and subfolders form an environment definition. ADE caches only the required files, not the entire repository. 
+Platform engineers should structure catalogs in a way that makes it easier and quicker for Azure Deployment Environments to find and cache environment definitions efficiently. By organizing the repository into a specific structure, you can better target files for caching and improve the overall performance of the deployment process. To ensure optimal results, platform engineers need to understand these guidelines and structure their repositories accordingly.
+
+When you attach a catalog to a dev center, Deployment Environments scans the catalog for a manifest.yaml file. On locating the file, ADE assumes the files in that folder and subfolders form an environment definition. ADE caches only the required files, not the entire repository. 
 
 The following diagram shows the recommended structure for a repo. Each template resides within a single folder.