Applied comments

Author: joexumsft

articles/azure-app-configuration/concept-snapshots.md

@@ -45,7 +45,7 @@ As snapshots are immutable entities, snapshots can only be created and archived.
 * **Recover snapshot**: Recovering a snapshot puts it back in an active state. At this point, the snapshot is no longer subject to expiration based on its configured retention period. Recovery is only possible in the retention period after archival.
 
 > [!NOTE]
-> The retention period can only be set during the creation of a snapshot. The default value for retention period is 30 days for Standard and Premium stores and 7 days for Free and Developer stores.
+> The retention period can only be set during the creation of a snapshot. The default value for retention period is 30 days for Standard and Premium tier stores and 7 days for Free and Developer tier stores.
 
 ## Requirements for snapshot operations
 

articles/azure-app-configuration/faq.yml

@@ -76,7 +76,14 @@ sections:
           
           The following are considerations for choosing a tier.
 
-          - **Purpose**: The Free tier is perfect for evaluating the service in non-production environments, allowing you to explore its features without any cost. The Developer tier is designed for non-production development and testing environments, offering enhanced capabilities at low cost. The Standard tier is tailored for medium-volume production use cases, providing a balance of performance and cost-efficiency. For high-volume or enterprise-level production needs, the Premium tier offers the highest level of performance and scalability, ensuring your applications run smoothly even under heavy load.
+          - **Purpose**: The Free tier is perfect for evaluating the service in non-production environments, allowing you to explore its features without any cost.
+
+              The Developer tier is cost-efficient for low-volume, non-production use cases and comes equipped with features and capabilities specifically tailored for development and testing needs.
+
+              The Standard tier is designed for medium-volume production and non-production use cases, providing a balance of performance and cost-efficiency.
+
+              For high-volume or enterprise-level production needs, the Premium tier offers the highest level of performance and scalability, ensuring your applications run smoothly even under heavy loads.
+
           - **Resources per subscription**: A resource consists of a single configuration store. Each subscription is limited to one configuration store per region in the Free tier. Subscriptions can have an unlimited number of configuration stores in the Developer, Standard and Premium tiers.
           - **Storage per resource**: In the Free tier, each configuration store is limited to 10 MB of regular storage and 10 MB of snapshot storage. In the Developer tier, each configuration store can use up to 500 MB of regular storage and an additional 500 MB of snapshot storage. In the Standard tier, each configuration store can use up to 1 GB of regular storage and an additional 1 GB of snapshot storage. In the Premium tier, each configuration store can use up to 4 GB of regular storage and an additional 4 GB of snapshot storage.
           - **Revision history**: App Configuration stores a history of all changes made to keys. In the Free and Developer tier, this history is stored for seven days. In the Standard and Premium tiers, this history is stored for 30 days.
@@ -89,17 +96,20 @@ sections:
               Premium tier stores have no quota limit on requests, ensuring that access to the store is never blocked.
           - **Throughput**: App Configuration stores in all tiers have a throughput allowance. Requests exceeding this allowance receive an HTTP status code 429 response.
 
-              Stores in the Free tier have no guaranteed throughput.
-
-              Stores in the Developer tier have no guaranteed throughput.
+              Stores in the Free tier and Developer tier have no guaranteed throughput.
 
               Stores in the Standard tier allow run rate† up to 300 requests per second (RPS) for read requests and up to 60 RPS for write requests.
 
               Stores in the Premium tier allow run rate† up to 450 RPS for read requests and up to 100 RPS for write requests.
 
               †The run rate is typically measured as the average number of requests handled by an App Configuration store without throttling over a specified period.
           - **Service level agreement**: The Free tier and Developer tier don't have an SLA. The Standard tier has an SLA of 99.9% availability and 99.95% availability with geo-replication enabled. The Premium tier has an SLA of 99.9% availability and 99.99% availability with geo-replication enabled.
-          - **Features**: All tiers include functionalities, including encryption with Microsoft-managed keys, authentication via access key or Microsoft Entra ID, Azure role-based access control (RBAC), managed identity, service tags, and availability zone redundancy. The Developer tier adds Private Link support to these functionalities. The Standard and Premium tiers offer more functionalities, including encryption with customer-managed keys, soft delete protection, and geo-replication capability.
+          - **Features**: All tiers include functionalities, including encryption with Microsoft-managed keys, authentication via access key or Microsoft Entra ID, Azure role-based access control (RBAC), managed identity, service tags, and availability zone redundancy.
+
+              The Developer tier also includes support for Private Link.
+
+              The Standard and Premium tiers offer more functionalities, including encryption with customer-managed keys, soft delete protection, and geo-replication capability.
+
           - **Cost**: There's no cost to use a Free tier store.
 
               Developer tier stores have a daily usage charge, which includes the first 3,000 requests each day. Requests beyond this daily allocation incur an overage charge.

articles/azure-app-configuration/monitor-app-configuration.md

@@ -179,7 +179,7 @@ The following table lists common and recommended alert rules for App C
 
 | Alert type | Condition | Description  |
 |:---|:---|:---|
-|Request quota usage exceeded | RequestQuotaUsage >= 100 | The configuration store has exceeded the [request quota usage](./faq.yml#are-there-any-limits-on-the-number-of-requests-made-to-app-configuration). Upgrade your store to a higher tier or follow the [best practices](./howto-best-practices.md#reduce-requests-made-to-app-configuration) to optimize your usage. |
+|Request quota usage exceeded | RequestQuotaUsage >= 100 | The configuration store has exceeded the [request quota usage](./faq.yml#are-there-any-limits-on-the-number-of-requests-made-to-app-configuration). Upgrade your store or follow the [best practices](./howto-best-practices.md#reduce-requests-made-to-app-configuration) to optimize your usage. |