Doc updates for banning and client_idle_timeout

Author: levkk

docs/configuration/pgdog.toml/general.md

@@ -148,7 +148,6 @@ queries as possible.
 
 Default: **`60_000`** (60s)
 
-
 ### `query_timeout`
 
 Maximum amount of time to wait for a Postgres query to finish executing. Use only in unreliable network conditions or when Postgres runs on unreliable hardware.
@@ -192,6 +191,12 @@ Close client connections that have been idle, i.e., haven't sent any queries, fo
 
 Default: **`none`** (disabled)
 
+### `client_login_timeout`
+
+Maximum amount of time new clients have to complete authentication. Clients that don't will be disconnected.
+
+Default: **`60_000`** (60s)
+
 ## Load balancer
 
 ### `load_balancing_strategy`

docs/features/load-balancer/healthchecks.md

@@ -87,7 +87,10 @@ ban_timeout = 300_000 # 5 minutes
 
 The **default** value is **5 minutes** (`300_000` milliseconds).
 
-If the database is still broken once the ban expires, it will fail a health check and will be removed from the load balancer again.
+!!! note
+    A database will not be placed back into the load balancer until it passes a health check again.
+
+    Make sure that `idle_healthcheck_timeout` is set to a lower setting than `ban_timeout`, so health checks have time to run before you expect the database to resume serving traffic.
 
 ### False positives