docs: drop exact counts that go stale when inventory changes (#2721)

fluxer_docs/src/content/docs/admin-api/index.mdx

@@ -40,7 +40,7 @@ Where an operation stacks several requirements, Fluxer evaluates each separately
 
 The effective ACL set of a session or an Admin OAuth2 bearer credential is the set stored on the account. The effective set of an Admin API key is the set stored on the key, subject to the owner check above. [Set user ACLs](/admin-api/users/#set-user-acls) writes an account's set. Holding `admin:authenticate` or `*` is the whole definition of an account that can reach the Admin API.
 
-Two operations derive their required ACLs from the validated request body.
+The operations below derive their required ACLs from the validated request body.
 
 [Update guild](/admin-api/guilds/#update-guild) maps each present body field to one ACL and requires every ACL in that set.
 
@@ -413,7 +413,7 @@ The registry is returned in this order by [List ACLs](#list-acls). A value outsi
 | acl:set:user | Replaces the Admin ACL set held by an account |
 | admin_api_key:manage | Creates, reads, renames, and revokes [Admin API keys](/admin-api/api-keys/) |
 | application:lookup | Reads [Admin application](/admin-api/applications/) resources, including the applications owned by one account |
-| application:list:by_owner<sup>2</sup> | Reads the two application listings |
+| application:list:by_owner<sup>2</sup> | Reads the application listings |
 | application:transfer_ownership | Transfers OAuth2 application ownership |
 | archive:trigger:guild | Creates guild [archives](/admin-api/archives/) |
 | archive:trigger:user | Creates user archives |
@@ -526,11 +526,11 @@ The registry is returned in this order by [List ACLs](#list-acls). A value outsi
 
 <sup>2</sup> [List applications](/admin-api/applications/#list-applications) and [List user applications](/admin-api/users/#list-user-applications) accept it in place of `application:lookup`, and no other operation reads it
 
-<sup>3</sup> The three archive reads accept `archive:view_all`, `archive:trigger:user`, or `archive:trigger:guild`, so an Admin who can create archives can also read them
+<sup>3</sup> The archive reads accept `archive:view_all`, `archive:trigger:user`, or `archive:trigger:guild`, so an Admin who can create archives can also read them
 
 <sup>4</sup> [Block a user's current avatar](/admin-api/blocklists/#block-a-users-current-avatar) requires it as well
 
-<sup>5</sup> [Update guild](/admin-api/guilds/#update-guild) names all five of these as one any-of requirement and then requires every one that the submitted body maps to
+<sup>5</sup> [Update guild](/admin-api/guilds/#update-guild) names all of these as one any-of requirement and then requires every one that the submitted body maps to
 
 <sup>6</sup> The permission admits no operation of its own. It only widens what an already admitted read returns