Clean up the description

README.md

···
 
 These instructions assume a user `www-data` on the host for Docker to use.
 
-1. In `knot-docker` directory, create Docker image with
-   `docker build -t knot:latest --build-arg TAG=master --build-arg UID=$(id -u www-data) --build-arg GID=$(id -u www-data) .`
+1. In `knot-docker` directory, edit the TAG variable in the Dockerfile and create Docker image with
+   `docker build -t knot:latest --build-arg UID=$(id -u www-data) --build-arg GID=$(id -u www-data) .`
 2. In this directory, create bind mount directories with `mkdir keys repositories server`
 3. Ensure `repositories` and `server` are owned by `www-data`
    with `chown www-data:www-data repositories server`
···
 4. Create Docker container with `docker-compose up -d`
 5. Knot is now ready for reverse proxy from `KNOT_SERVER_HOSTNAME:443` to local port 5555
    (knot verification will not work over HTTP port 80!)
-
-<!--
-Once the container is up, the Git repositories directory
-needs to be specified explicitly as `/home/git/repositories` in `AuthorizedKeysCommand`
-(see [knot-hosting](https://tangled.sh/@tangled.sh/core/blob/master/docs/knot-hosting.md#repositories)).
-Create the file `/etc/ssh/sshd_config.d/authorized_keys_command.conf` with the following:
-
-```
-Match User git
-  AuthorizedKeysCommand /usr/bin/knot keys -o authorized-keys -git-dir /home/git/repositories
-  AuthorizedKeysCommandUser nobody
-```
-
-(This should probably be done in the Dockerfile when building the image.)
--->
 
 ## Repository troubleshooting