edits

Author: ktoliver

articles/batch/TOC.yml

@@ -111,10 +111,10 @@
       href: batch-pools-without-public-IP-addresses-classic-retirement-migration-guide.md
     - name: TLS 1.0 and TLS 1.1 
       href: batch-tls-101-migration-guide.md
-    - name: Job and pool lifetime statistics APIs
+    - name: Job and pool lifetime statistics
       href: job-pool-lifetime-statistics-migration-guide.md
-    - name: Low-priority VMs
-      href: low-priority-VMs-retirement-migration-guide.md
+    - name: Low-priority virtual machines
+      href: low-priority-vms-retirement-migration-guide.md
 - name: How-to guides
   items:
   - name: Manage Batch accounts

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

@@ -18,7 +18,7 @@ Often, you need to store secure data for an application. Your data must be secur
 
 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.
+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.
 
 ## Feature end of support
 

articles/batch/low-priority-vms-retirement-migration-guide.md

@@ -8,7 +8,7 @@ ms.topic: how-to
 ms.date: 08/10/2022
 ---
 
-# Migrate low-priority VMs to spot VMs in Batch
+# Migrate Batch low-priority VMs to Azure Spot Virtual Machines
 
 The Azure Batch feature low-priority virtual machines (VMs) is being retired on *September 30, 2025*. Learn how to migrate your Batch low-priority VMs to Azure Spot Virtual Machines.
 
@@ -22,7 +22,7 @@ You can use low-priority VMs to take advantage of unused capacity in Azure. The
 
 Low-priority VMs are a deprecated preview feature and won't be generally available. Spot VMs offered through the Azure Spot Virtual Machines service are the official, preemptible offering from the Azure compute platform. Spot Virtual Machines is generally available. On September 30, 2025, we'll retire the low-priority VMs feature. After that date, existing low-priority pools in Batch might no longer work and you can't provision new low-priority VMs.
 
-## Alternative: Use spot VMs in Azure Spot Virtual Machines
+## Alternative: Use Azure Spot Virtual Machines
 
 As of May 2020, Azure offers spot VMs in Batch in addition to low-priority VMs. Like low-priority VMs, you can use the spot VM option to purchase spare capacity at a deeply discounted price in exchange for the possibility that the VM will be evicted. Unlike low-priority VMs, you can use the spot VM option for single VMs and scale sets. Virtual machine scale sets scale up to meet demand. When used with a spot VM, a virtual machine scale set allocates only when capacity is available.