Removed CentOS References and Caution info

Author: Padmalathas

articles/batch/batch-pool-node-error-checking.md

@@ -1,15 +1,12 @@
 ---
 title: Pool and node errors
 description: Learn about background operations, errors to check for, and how to avoid errors when you create Azure Batch pools and nodes.
-ms.date: 04/11/2023
+ms.date: 06/10/2024
 ms.topic: how-to
 ---
 
 # Azure Batch pool and node errors
 
-> [!CAUTION]
-> This article references CentOS, a Linux distribution that is nearing End Of Life (EOL) status. Please consider your use and planning accordingly. For more information, see the [CentOS End Of Life guidance](~/articles/virtual-machines/workloads/centos/centos-end-of-life.md).
-
 Some Azure Batch pool creation and management operations happen immediately. Detecting failures for these operations is straightforward, because errors usually return immediately from the API, command line, or user interface. However, some operations are asynchronous, run in the background, and take several minutes to complete. This article describes ways to detect and avoid failures that can occur in the background operations for pools and nodes.
 
 Make sure to set your applications to implement comprehensive error checking, especially for asynchronous operations. Comprehensive error checking can help you promptly identify and diagnose issues.
@@ -106,7 +103,7 @@ Other reasons for `unusable` nodes might include the following causes:
 
 - A custom VM image is invalid. For example, the image isn't properly prepared.
 - A VM is moved because of an infrastructure failure or a low-level upgrade. Batch recovers the node.
-- A VM image has been deployed on hardware that doesn't support it. For example, a CentOS HPC image is deployed on a [Standard_D1_v2](/azure/virtual-machines/dv2-dsv2-series) VM.
+- A VM image has been deployed on hardware that doesn't support it.
 - The VMs are in an [Azure virtual network](batch-virtual-network.md), and traffic has been blocked to key ports.
 - The VMs are in a virtual network, but outbound traffic to Azure Storage is blocked.
 - The VMs are in a virtual network with a custom DNS configuration, and the DNS server can't resolve Azure storage.