Updater: document UPDATER_MINRATIO

Advanced setup/Other options.md

@@ -11,4 +11,5 @@
 | `PUBLICIP_FILE` | `/tmp/gluetun/ip` | Any filepath | Filepath to store the public IP address assigned. This will be removed in the `v4` program, instead you might want to use the [HTTP control server](HTTP-control-server) |
 | `VERSION_INFORMATION` | `on` | `on`, `off` | Logs a message indicating if a newer version is available once the VPN is connected |
 | `UPDATER_PERIOD` | `0` | Valid duration string such as `24h` | Period to update the VPN servers data in memory and to /gluetun/servers.json. Set to `0` to disable. This does a burst of DNS over TLS requests, which may be blocked if you set `BLOCK_MALICIOUS=on` for example. |
+| `UPDATER_MINRATIO` | `0.8` | Ratio between `0` (excluded) and `1` | Ratio of servers to be found for the update to succeed, compared to the servers already built in the program |
 | `UPDATER_VPN_SERVICE_PROVIDERS` | the current VPN provider used | Any valid VPN provider name | List of providers to update servers data for, when the updater triggers periodically. If left empty, it defaults to the current VPN provider used at start. |

Advanced setup/Updating servers.md

@@ -37,7 +37,6 @@ Note that this operation is very quick 🚀 for some providers (`private interne
 ⚠️ This will show your ISP/Government/Sniffing actors that you access some VPN service providers and try to resolve their server hostnames.
 That might not be the best solution depending on your location. Plus some of the requests might be blocked, hence not allowing certain server information to be updated.
 
-
 You can also run this with `docker-compose` using:
 
 ```yml