fix: clarify wording and context, link to image

specify in the example docker compose to use a container registry link
as a shortcut around building

README.org

@@ -31,12 +31,12 @@ These are the abstractions used to represent beacons and the management of beaco
 - Commands are issued to beacon instances or categories
 
 * Running
-Running sparse will require knowing what ports to use for HTTPS access for the beacons. For the most common use case of port 443, the following Docker compose file should work:
+Running sparse will require knowing what ports to the beacons will connect to via HTTPS. For the most common use case of port 443, the following Docker compose file should work:
 
 #+BEGIN_SRC yaml
 services:
   server:
-    image: sparse-server:latest
+    image: gitea.riouxs.co/andrew.rioux/sparse-server:latest
     volumes:
       - ./files:/sparse-server
     ports:
@@ -45,7 +45,7 @@ services:
     restart: always
 #+END_SRC
 
-Once deployed, add the first user with the following command:
+Once deployed, add the first sparse management interface user with the following command:
 
 #+BEGIN_SRC sh
 docker compose exec server /bin/sparse-server user create -n USERNAME
@@ -54,6 +54,7 @@ docker compose exec server /bin/sparse-server user create -n USERNAME
 Once deployed, the management interface is available at port 3000 over HTTP.
 
 ** Deploying a beacon
+- Sign into the management interface of the sparse C2 server
 - Add a listener with a port that matches the port specified in the docker compose and allowed through NAT, and use an IP address that can be routed to this C2 server
 - Add a configuration to perform a periodic callback
 - Add a template, selecting the prior listener and configuration. It will need an IP address that corresponds to the LAN that the beacon will be running on