Rename the program to sww and its deciding daemon to discriminator (closes #218) (#221)

docs/rules.md

@@ -32,7 +32,7 @@ scanner-agent  user_agent  ban     (?i)\b(sqlmap|nikto|nuclei|wpscan)\b
 ## The default file
 
 The image ships one file, `share/rules.d/00-default.rules`, installed as
-`/etc/smallwebwaf/rules.d/00-default.rules`:
+`/etc/sww/rules.d/00-default.rules`:
 
 ```
 # 00-default.rules: probes no real visitor sends, anchored at the site root
@@ -54,19 +54,20 @@ empty-agent      user_agent  log     ^$
 
 ## A file of your own
 
-`servewaf` reads the rule files in its own container. Rules of your own go in a
-file named to sort after the default, such as `50-site.rules`:
+`discriminator` reads the rule files in its own container. Rules of your own go
+in a file named to sort after the default, such as `50-site.rules`:
 
 ```
 # 50-site.rules: WordPress probes, which this site never serves
 wp-probe         path        ban     (?i)^/(wp-login\.php|xmlrpc\.php|wp-admin/)
 ```
 
-A `Dockerfile` built on the `smallwebwaf` image, for `servewaf` to run from,
-adds it:
+A `Dockerfile` built on the `smallwebwaf` image, for `discriminator` to run
+from, adds it:
 
 ```dockerfile
-COPY 50-site.rules /etc/smallwebwaf/rules.d/50-site.rules
+COPY 50-site.rules /etc/sww/rules.d/50-site.rules
 ```
 
-Or mount it there. A `path` rule applies on every site behind that `servewaf`.
+Or mount it there. A `path` rule applies on every site behind that
+`discriminator`.