updated README

README.md

@@ -16,18 +16,6 @@ WaybackProxy is a retro-friendly HTTP proxy which retrieves pages from the [Inte
 4. Try it out! You can edit most settings that are in `config.json` by browsing to http://web.archive.org while on the proxy, although you must edit `config.json` to make them permanent.
 5. Press Ctrl+C to stop the proxy
 
-## Known issues and limitations
-
-* The Wayback Machine itself is not 100% reliable. Known issues include:
-  * Pages newer than the specified date (setting a specific YYYYMMDD date instead of a wider YYYYMM or YYYY helps with that);
-  * Random broken images;
-  * Strange 404 errors caused by bad server responses or incorrect URL capitalization at archival time;
-  * Infinite redirect loops;
-  * Server errors when it's having a bad day.
-* WaybackProxy will work around some redirection scripts (example: `http://example.com/redirect?to=http://...`) which are not archived by the Wayback Machine, but the destination URLs are sometimes not archived either.
-* WaybackProxy is not a generic proxy. The POST and CONNECT methods are not implemented.
-* Transparent proxying mode requires HTTP/1.1 and therefore cannot be used with some really old (pre-1996) browsers. Use standard mode with such browsers.
-
 ## Docker Container
 
 A Dockerfile is included that allows you to run WaybackProxy from a docker container. 
@@ -60,7 +48,7 @@ docker pull cttynul/waybackproxy:latest
 To run:
 
 ```bash
-docker run --rm -it -e DATE=20011225 -p 8888:8888 cttynul/waybackproxy
+docker run -d -e DATE=20011025 -p 8888:8888 cttynul/waybackproxy
 ```
 
 #### Build locally
@@ -73,10 +61,23 @@ docker build --no-cache -f Dockerfile -t waybackproxy .
 To run:
 
 ```bash
-docker run --rm -it -e DATE=20011225 -p 8888:8888 waybackproxy
+docker run -d -e DATE=20011025 -p 8888:8888 waybackproxy
 ```
 
+## Known issues and limitations
+
+* The Wayback Machine itself is not 100% reliable. Known issues include:
+  * Pages newer than the specified date (setting a specific YYYYMMDD date instead of a wider YYYYMM or YYYY helps with that);
+  * Random broken images;
+  * Strange 404 errors caused by bad server responses or incorrect URL capitalization at archival time;
+  * Infinite redirect loops;
+  * Server errors when it's having a bad day.
+* WaybackProxy will work around some redirection scripts (example: `http://example.com/redirect?to=http://...`) which are not archived by the Wayback Machine, but the destination URLs are sometimes not archived either.
+* WaybackProxy is not a generic proxy. The POST and CONNECT methods are not implemented.
+* Transparent proxying mode requires HTTP/1.1 and therefore cannot be used with some really old (pre-1996) browsers. Use standard mode with such browsers.
+
 ## Other links
 
 * [Donate to the Internet Archive](https://archive.org/donate/), they need your help to keep the Wayback Machine and its petabytes upon petabytes of data available to everyone for free with no ads.
 * [Check out 86Box](https://86box.github.io/), the emulator I use for testing WaybackProxy on older browsers.
+* [WaybackProxy](https://hub.docker.com/r/cttynul/waybackproxy) on Docker Hub