From d3271361ea26365a78f9ebe8506d026e7332f2e3 Mon Sep 17 00:00:00 2001
From: bash <31279994+hermensbas@users.noreply.github.com>
Date: Thu, 14 Nov 2024 20:53:32 +0100
Subject: [PATCH] Updated Playerbot Configuration (markdown)

---
 Playerbot-Configuration.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/Playerbot-Configuration.md b/Playerbot-Configuration.md
index 626edee..f92c6b2 100644
--- a/Playerbot-Configuration.md
+++ b/Playerbot-Configuration.md
@@ -5,7 +5,7 @@ or can't be active. An active bots takes and eats alot more resources then an id
 The following logic is applied to determine whether a bot is active or not, applied in the explained order.
 
 ```
-1. NOT ACTIVE: When server just started and the server update is smaller then (max amount of bots * 0.12 seconds) 
+1. NOT ACTIVE: When server just started and the server uptime smaller then (max amount of bots * 0.12 seconds) 
 2. ALWAYS ACTIVE: When bot is in battleground, instance or raid.
 3. ALWAYS ACTIVE: When in combat and not in party (defend urself)
 4. ALWAYS ACTIVE: If bot zone has a real players