Fix documentation

Author: quietsy

README.md

@@ -50,7 +50,7 @@ This mod gives SWAG the ability to start containers on-demand when accessed thro
 ## Security Consideration:
 Mapping the `docker.sock`, especially in a publicly accessible container is a security liability. Since this mod only needs read-only access to the docker api, the recommended method is to proxy the `docker.sock` via a solution like [our docker socket proxy](https://github.com/linuxserver/docker-socket-proxy), limit the access, and set `DOCKER_HOST=` to point to the proxy address.
 
-Here's a sample compose yaml snippet for linuxserver/docker-socket-proxy:
+Here's a sample compose yaml snippet for `linuxserver/docker-socket-proxy`:
 ```yaml
   socket-proxy:
     image: lscr.io/linuxserver/socket-proxy:latest
@@ -59,12 +59,12 @@ Here's a sample compose yaml snippet for linuxserver/docker-socket-proxy:
       - ALLOW_START=1
       - ALLOW_STOP=1
       - CONTAINERS=1
-      - POST=1
+      - POST=0
     volumes:
       - /var/run/docker.sock:/var/run/docker.sock:ro
     restart: unless-stopped
     read_only: true
     tmpfs:
       - /run
 ```
-Then the env var in SWAG can be set as `DOCKER_HOST=socket-proxy`. This will allow docker cli in SWAG to be able to retrieve info on other containers, but it won't be allowed to spin up new containers.
+Then the env var in SWAG can be set as `DOCKER_HOST=tcp://socket-proxy:2375`. This will allow docker cli in SWAG to be able to retrieve info on other containers, but it won't be allowed to spin up new containers.