diff --git a/arednHow-toGuides/local-package-repo.rst b/arednHow-toGuides/local-package-repo.rst
index 9060aaa..6c9d247 100644
--- a/arednHow-toGuides/local-package-repo.rst
+++ b/arednHow-toGuides/local-package-repo.rst
@@ -7,7 +7,7 @@ There may be cases where your mesh nodes have no way to access the AREDN |trade|
 Configure your Package Server
 =============================
 
-Your package server must be connected to the mesh as a host on your local node's LAN network, using a node that also has Internet access via its WAN interface. You should add this host to the node's *DHCP Reservation List*. You do not need to add the package host to the *Advertised Services List* of the node to which it is connected. The package server should be given a hostname that is unique on your mesh, typically prefixed with the callsign of the server owner. You can use any operating system platform you desire *(Windows, Linux, Mac),* as long as it has the ability to function as a web server. The following are the two main tasks required of the local package server:
+Your package server must be connected to the mesh as a host on your local node's LAN network, using a node that also has Internet access via its WAN interface. The reason this node is connected to the Internet is to allow the web server to download updated files from the AREDN |trade| Internet server, but the node's Internet connection is not advertised or allowed for use by other nodes or devices on the mesh network. You should add this host to the node's *DHCP Reservation List*. You do not need to add the package host to the *Advertised Services List* of the node to which it is connected. The package server should be given a hostname that is unique on your mesh, typically prefixed with the callsign of the server owner. You can use any operating system platform you desire *(Windows, Linux, Mac),* as long as it has the ability to function as a web server. The following are the two main tasks required of the local package server:
 
 * Obtain the set of AREDN |trade| software files from ``downloads.arednmesh.org``
 * Make those files available via your computer's web server so nodes can query the package URLs