artall-2

Author: v-thpra

articles/api-center/set-up-api-center.md

@@ -4,7 +4,7 @@ description: Learn how to use the Azure portal to set up an API center for API d
 author: dlepow
 ms.service: azure-api-center
 ms.topic: quickstart
-ms.date: 08/25/2025
+ms.date: 10/13/2025
 ms.author: danlep 
 ---
 

articles/api-management/api-management-key-concepts-experiment.md

@@ -6,7 +6,7 @@ author: dlepow
 
 ms.service: azure-api-management
 ms.topic: overview
-ms.date: 06/27/2022
+ms.date: 10/13/2025
 ms.author: danlep
 ms.custom: mvc
 

articles/api-management/soft-delete.md

@@ -5,7 +5,7 @@ ms.service: azure-api-management
 ms.topic: how-to
 author: dlepow
 ms.author: danlep
-ms.date: 02/07/2022
+ms.date: 10/13/2025
 ---
 
 # API Management soft-delete (preview)
@@ -38,7 +38,7 @@ Recovery and other operations on a soft-deleted instance are enabled through [RE
 
 ## Soft-delete behavior
 
-You can use any API version to create your API Management instance. When you use the Azure portal, Azure REST API, or another Azure tool using API version `2020-06-01-preview` or later to delete an API Management instance, it's automatically soft-deleted. 
+You can use any API version to create your API Management instance. When you use the Azure portal, Azure REST API, or another Azure tool using API version `2020-06-01-preview` or later to delete an API Management instance, the instance is automatically soft-deleted. 
 
 Once an API Management instance is soft-deleted, the service exists in a deleted state, making it inaccessible to normal API Management operations.
 
@@ -48,7 +48,7 @@ In the soft-deleted state:
 - Azure will schedule the permanent deletion of the underlying data corresponding to the API Management instance after the predetermined (48 hour) retention period. 
 - You can't reuse the name of the API Management instance.
 
-If you don't recover or purge your API Management instance within 48 hours, it's automatically deleted permanently. 
+If you don't recover or purge your API Management instance within 48 hours, the instance is automatically deleted permanently. 
 
 ## List deleted API Management instances
 
@@ -119,7 +119,7 @@ https://management.azure.com/subscriptions/{subscriptionId}/resourceGroups/{reso
 Use the API Management [Purge](/rest/api/apimanagement/current-ga/deleted-services/purge) operation, substituting `{subscriptionId}`, `{location}`, and `{serviceName}` with your Azure subscription, resource location, and API Management name.
 
 > [!NOTE]
-> To purge a soft-deleted instance, you must have the following RBAC permissions at the subscription scope in addition to Contributor access to the API Management instance: Microsoft.ApiManagement/locations/deletedservices/delete, Microsoft.ApiManagement/deletedservices/read.
+> To purge a soft-deleted instance, you must have the following role-based access control (RBAC) permissions at the subscription scope in addition to Contributor access to the API Management instance: Microsoft.ApiManagement/locations/deletedservices/delete, Microsoft.ApiManagement/deletedservices/read.
 
 ```rest
 DELETE https://management.azure.com/subscriptions/{subscriptionId}/providers/Microsoft.ApiManagement/locations/{location}/deletedservices/{serviceName}?api-version=2021-08-01
@@ -139,9 +139,9 @@ You **can't** reuse the name of an API Management instance in a new deployment:
 
 - While the instance is soft-deleted.
 
-- In a subscription other than the one used to deploy the original instance, even after the original instance has been permanently deleted (purged) from Azure. This restriction applies whether the new subscription used is in the same or a different Microsoft Entra tenant. The restriction is in effect for several days or longer after deletion, depending on the subscription type. 
+- In a subscription other than the one used to deploy the original instance, even after the original instance is permanently deleted (purged) from Azure. This restriction applies whether the new subscription used is in the same or a different Microsoft Entra tenant. The restriction is in effect for several days or longer after deletion, depending on the subscription type. 
 
-  This restriction is because Azure reserves the service host name to a customer's tenant for a reservation period to prevent the threat of subdomain takeover with dangling DNS entries. For more information, see [Prevent dangling DNS entries and avoid subdomain takeover](/azure/security/fundamentals/subdomain-takeover). To see all dangling DNS entries for subscriptions in a Microsoft Entra tenant, see [Identify dangling DNS entries](/azure/security/fundamentals/subdomain-takeover#identify-dangling-dns-entries). 
+  This restriction is because Azure reserves the service host name to a customer's tenant for a reservation period to prevent the threat of subdomain takeover with dangling domain name system (DNS) entries. For more information, see [Prevent dangling DNS entries and avoid subdomain takeover](/azure/security/fundamentals/subdomain-takeover). To see all dangling DNS entries for subscriptions in a Microsoft Entra tenant, see [Identify dangling DNS entries](/azure/security/fundamentals/subdomain-takeover#identify-dangling-dns-entries). 
 
 
 ## Related content