From 1969d8882b08d43684805cb4cda90a66f2f5a6cf Mon Sep 17 00:00:00 2001
From: TheNerd02 <143094437+TheNerd02@users.noreply.github.com>
Date: Fri, 3 Oct 2025 14:09:49 +0200
Subject: [PATCH] Update configure-high-availability.md
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

The documentation mentions 2 physical server, implying the configuration can only be applied when hardware servers are being used not virtual machines. However below that There are some caveats about using cloud platforms (implying it would be possible to apply this configuration to the cloud as well) "Some cloud platforms don’t allow direct IP management with keepalived. If you’re using a cloud environment, check whether it supports VIP assignment."
---
 .../nim/system-configuration/configure-high-availability.md   | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/content/nim/system-configuration/configure-high-availability.md b/content/nim/system-configuration/configure-high-availability.md
index 5e679df7e..47e280052 100644
--- a/content/nim/system-configuration/configure-high-availability.md
+++ b/content/nim/system-configuration/configure-high-availability.md
@@ -26,7 +26,7 @@ This guide shows how to configure HA for NGINX Instance Manager using `keepalive
 
 Before setting up high availability (HA) for NGINX Instance Manager, make sure you have:
 
-- Two physical servers with NGINX Instance Manager installed
+- Two servers with NGINX Instance Manager installed
 - A reserved virtual IP address (VIP) that always points to the active instance
 - An NFS share that both servers can access
 - Permissions to manage IP addresses at the operating system level
@@ -259,4 +259,4 @@ If failover does not work as expected, check the following:
 
 ## Need help?
 
-For additional support, visit the [F5 Support Portal](https://support.f5.com).
\ No newline at end of file
+For additional support, visit the [F5 Support Portal](https://support.f5.com).