diff --git a/Configuring-Multiple-Servers.md b/Configuring-Multiple-Servers.md
index 388b976..0a81548 100644
--- a/Configuring-Multiple-Servers.md
+++ b/Configuring-Multiple-Servers.md
@@ -16,7 +16,7 @@ This subdirectory-based approach was chosen for its relative simplicity and beca
 
 - **All configured servers accessible externally via a browser**
 
-  LiveAtlas needs to be able to make requests to each configured server from the visitor's browser. This means all of your configured Dynmap/Squaremap/Pl3xmap server URLs need to be publicly accessible, and meet all browser imposed restrictions:
+  LiveAtlas needs to be able to make requests to each configured server from the visitor's browser. This means all of your configured server URLs need to be publicly accessible, and meet all browser imposed restrictions:
 
   - If your servers are accessed via a [different origin](https://developer.mozilla.org/en-US/docs/Web/Security/Same-origin_policy#definition_of_an_origin) to LiveAtlas itself, then you will need to ensure [CORS headers](https://developer.mozilla.org/en-US/docs/Web/HTTP/CORS) are configured correctly. Headers for the Dynmap internal webserver can be configured using Dynmap's [http-response-headers setting](https://github.com/webbukkit/dynmap/wiki/Configuration.txt#http-response-headers)