From ebb633b5f6ee3ac6e07e9233c3cbfeb55411f055 Mon Sep 17 00:00:00 2001
From: James Lyne <jim+github@not-null.co.uk>
Date: Tue, 7 Sep 2021 14:44:22 +0100
Subject: [PATCH] Updated Configuring Multiple Servers (markdown)

---
 Configuring-Multiple-Servers.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/Configuring-Multiple-Servers.md b/Configuring-Multiple-Servers.md
index 4f8f090..c6ff1d4 100644
--- a/Configuring-Multiple-Servers.md
+++ b/Configuring-Multiple-Servers.md
@@ -52,7 +52,7 @@ This subdirectory-based approach was chosen for its relative simplicity and beca
 
     Multiple server support is configured in index.html. Look for the `<script>` containing the `window.liveAtlasConfig` object and edit the `servers` property to include the servers you want to be accessible within LiveAtlas. The key of each server object will be used in the URL to access it. 
 
-    Each server object should contain a `dynmap` or `pl3xmap` property which contains the URLs necessary for displaying the map. Dynmap maps require several URLs which can typically be found in the `standalone/config.js` file for the server. Pl3xmap maps require just the URL the map is currently viewable at. Making all URLs absolute is recommended to avoid ambiguity.
+    Each server object should contain a `dynmap` or `pl3xmap` property which contains the URLs necessary for displaying the map. Dynmap maps require several URLs which can be found in the `standalone/config.js` file for the server. Pl3xmap maps require just the URL the map is currently viewable at. Making all URLs absolute is recommended to avoid ambiguity.
 
     An example with 2 dynmap servers named `creative` and `survival` and a 3rd Pl3xmap server: