edits

Author: ktoliver

articles/batch/TOC.yml

@@ -103,9 +103,9 @@
     href: high-availability-disaster-recovery.md
   - name: Task runtime environment variables
     href: batch-compute-node-environment-variables.md
-  - name: Batch feature retirements
+  - name: Feature retirements
     items:
-    - name: Certificates for access management
+    - name: Batch certificates
       href: batch-certificate-migration-guide.md
     - name: Pools without public IP addresses (classic)
       href: batch-pools-without-public-IP-addresses-classic-retirement-migration-guide.md

articles/batch/batch-certificate-migration-guide.md

@@ -14,9 +14,9 @@ On *February 29, 2024*, the certificates feature for Azure Batch access manageme
 
 ## About the feature
 
-Often, you need to store secure data in an application. Your data must be securely managed so that only administrators or authorized users can access it.
+Often, you need to store secure data for an application. Your data must be securely managed so that only administrators or authorized users can access it.
 
-Azure Batch offers two ways to secure access management. You can use a certificate that you create and manage in Azure Batch or you can use Azure Key Vault to store an access key. Using a key vault is an Azure standard way to deliver more controlled secure access management.
+Currently, Azure Batch offers two ways to secure access. You can use a certificate that you create and manage in Azure Batch or you can use Azure Key Vault to store an access key. Using a key vault is an Azure-standard way to deliver more controlled secure access management.
 
 Currently, you can use a certificate at the account level in Azure Batch. You must generate the certificate and upload it manually to Batch by using the Azure portal. To access the certificate, the certificate must be associated with and installed for only the current user. A certificate typically is valid for one year, and it must be updated each year.
 
@@ -32,7 +32,7 @@ In Key Vault, you get these benefits:
 
 After the certificates feature in Azure Batch is retired on February 29, 2024, a certificate in Batch might not work as expected. After that date, you won't be able to create a pool by using a certificate. Pools that continue to use certificates after the feature is retired might increase in size and cost.
 
-## Alternative: Use Key Vault to secure your Batch resources
+## Alternative: Use Key Vault
 
 Azure Key Vault is an Azure service you can use to store and manage secrets, certificates, tokens, keys, and other configuration values that give authenticated users access to secure applications and services. Key Vault is based on the idea that security is improved and standardized when you remove hard-coded secrets and keys from application code that's deployed.
 
@@ -70,7 +70,7 @@ For more information, see [Quickstart: Create a key vault by using the Azure por
 
 ### Create a key vault by using PowerShell
 
-1. Use the PowerShell option in Azure Cloud Shell to sign in to your account;
+1. Use the PowerShell option in Azure Cloud Shell to sign in to your account:
 
    ```powershell
    Login-AzAccount

articles/batch/job-pool-lifetime-statistics-migration-guide.md

@@ -1,30 +1,30 @@
 ---
 title: Migrate from job and pool lifetime statistics to logs in Azure Batch
-description: Learn how to migrate your Batch monitoring approach from using job and pool lifetime statistics APIs to using logs and plan for feature end of support.
+description: Learn how to migrate your Batch monitoring approach from using job and pool lifetime statistics API to using logs and plan for feature end of support.
 author: harperche
 ms.author: harpercheng
 ms.service: batch
 ms.topic: how-to
 ms.date: 08/15/2022
 ---
 
-# Migrate from job and pool lifetime statistics APIs to logs in Batch
+# Migrate from job and pool lifetime statistics API to logs in Batch
 
-The Azure Batch lifetime statistics APIs for jobs and pools will be retired on *April 30, 2023*. Learn how to migrate your Batch monitoring approach from using the lifetime statistics APIs to using logs.
+The Azure Batch lifetime statistics API for jobs and pools will be retired on *April 30, 2023*. Learn how to migrate your Batch monitoring approach from using the lifetime statistics API to using logs.
 
 ## About the feature
 
-Currently, you can use APIs to retrieve lifetime statistics for jobs and pools in Batch. You can use the APIs to get lifetime statistics for all the jobs and pools in a Batch account or for a specific job or pool. The APIs collect statistical data from when the Batch account was created until the last time the account was updated or from when a job or pool was created. A customer might use the job and pool lifetime statistics APIs to help them analyze and evaluate their Batch usage.
+Currently, you can use API to retrieve lifetime statistics for jobs and pools in Batch. You can use the API to get lifetime statistics for all the jobs and pools in a Batch account or for a specific job or pool. The API collects statistical data from when the Batch account was created until the last time the account was updated or from when a job or pool was created. A customer might use the job and pool lifetime statistics API to help them analyze and evaluate their Batch usage.
 
 To make statistical data available to customers, the Batch service allocates batch pools and schedule jobs with an in-house MapReduce implementation to do a periodic, background rollup of statistics. The aggregation is performed for all Batch accounts, pools, and jobs in each region, regardless of whether a customer needs or queries the stats for their account, pool, or job. The operating cost includes 11 VMs allocated in each region to execute MapReduce aggregation jobs. For busy regions, we had to increase the pool size further to accommodate the extra aggregation load.
 
-The MapReduce aggregation logic was implemented by using legacy code, and no new features are being added or improvised due to technical challenges with legacy code. Still, the legacy code and its hosting repository need to be updated frequently to accommodate increased loads in production and to meet security and compliance requirements. Also, because the APIs are featured to provide lifetime statistics, the data is growing and demands more storage and performance issues, even though most customers don't use the API. The Batch service currently uses all the compute and storage usage charges that are associated with MapReduce pools and jobs.
+The MapReduce aggregation logic was implemented by using legacy code, and no new features are being added or improvised due to technical challenges with legacy code. Still, the legacy code and its hosting repository need to be updated frequently to accommodate increased loads in production and to meet security and compliance requirements. Also, because the API is featured to provide lifetime statistics, the data is growing and demands more storage and performance issues, even though most customers don't use the API. The Batch service currently uses all the compute and storage usage charges that are associated with MapReduce pools and jobs.
 
 ## Feature end of support
 
-The lifetime statistics APIs are designed and maintained to help you troubleshoot your Batch services. However, not many customers actually use the APIs. The customers who use the APIs are interested in extracting details for not more than a month. More advanced ways of getting data about logs, pools, and jobs can be collected and used on a need basis by using Azure portal logs, alerts, log export, and other methods.
+The lifetime statistics API is designed and maintained to help you troubleshoot your Batch services. However, not many customers actually use the API. The customers who use the API are interested in extracting details for not more than a month. More advanced ways of getting data about logs, pools, and jobs can be collected and used on a need basis by using Azure portal logs, alerts, log export, and other methods.
 
-When the job and pool lifetime statistics APIs are retired on April 30, 2023, the APIs will no longer work, and they'll return an appropriate HTTP response error code to the client.
+When the job and pool lifetime statistics API is retired on April 30, 2023, the API will no longer work, and it will return an appropriate HTTP response error code to the client.
 
 ## Alternative: Set up logs in the Azure portal