docs: rate-limits page states the backstop's exception (#358)
Paragraph 2 said a quiet instance is never limited, which the backstop contradicts. Replaced with the approved paragraph.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
1 file changed,
+1
−1
docs/site/rate-limits.md+1 −1
diff --git a/docs/site/rate-limits.md b/docs/site/rate-limits.md| index c09773dc7..2cc503502 100644 |
| --- a/docs/site/rate-limits.md |
| +++ b/docs/site/rate-limits.md |
| @@ -2,7 +2,7 @@ |
| The platform stops one visitor from taking over an instance. It does this at the edge, so a refused request never reaches the app and never wakes a sleeping one. |
| -A quiet instance is never limited. Limits only start when the instance is busy, and then the visitors with the most requests in flight are turned away first. Everyone else carries on as normal, including many people sharing one address, like an office or a phone network. |
| +A quiet instance is never limited except by the backstop, which only a flood from one address reaches. The other limits only start when the instance is busy, and then the visitors with the most requests in flight are turned away first. Everyone else carries on as normal, including many people sharing one address, like an office or a phone network. |
| ## What a refused visitor sees |