RateLimits information is outdated.

[jvanasco]

I believe the ratelimits documentation is outdated in respect to these passages:

If you're actively developing or testing a Let's Encrypt client, please utilize our staging environment instead of the production API.

You can have a maximum of 300 Pending Authorizations on your account. Hitting this rate limit is rare, and happens most often when developing ACME clients.

Note that having a large number of pending authorizations is generally the result of a buggy client. If you're hitting this rate limit frequently you should double-check your client code.

In the past this was 100% accurate - this was almost always happening due to client development.

Over the past few years though, the cause/need for staging environments has increasingly become due to people using automated systems (Docker Containers, AWS images, Ansible, etc) which will either not have the certificates/logs persist OR lack a centralized storage system so multiple nodes each independently invoke a client.

I believe the ratelimits page should have the following:

1- A callout/warning "box" at the top, replacing the text "If you're actively developing or testing a Let's Encrypt client" with something like "Important Information for people using Automated Systems or actively developing/testing clients".

2- Note that an improperly designed automated/scaling system is also a potential cause (where applicable).