Document RPC pagination limits (#2572)

* Document RPC pagination limits

* clarify pagination upper limits configuration

* Revert "clarify pagination upper limits configuration"

This reverts commit eb67693.

---------

Co-authored-by: Elliot <elliot@stellar.org>

Author: kalepail

docs/data/apis/rpc/api-reference/structure/pagination.mdx

@@ -6,7 +6,15 @@ title: Pagination
 For methods which support it, the pagination arguments are passed as a final object argument with two values:
 
 - `cursor`: string - (optional) An opaque string which acts as a paging token. Each response will include a `cursor` field which can be included in a subsequent request to obtain the next page of results.
-- `limit`: number - (optional) The maximum number of records returned. The limit for [getEvents](../methods/getEvents.mdx) can range from 1 to 10000 - an upper limit that is hardcoded in Stellar-RPC for performance reasons. If this argument isn't designated, it defaults to 100.
+- `limit`: number - (optional) The maximum number of records returned. Each paginated method has a method-specific range and default.
+
+| Method | Limit range | Default limit |
+| --- | --- | --- |
+| [`getEvents`](../methods/getEvents.mdx) | 1 to 10000 | 100 |
+| [`getLedgers`](../methods/getLedgers.mdx) | 1 to 200 | 50 |
+| [`getTransactions`](../methods/getTransactions.mdx) | 1 to 200 | 50 |
+
+These upper limits are hardcoded in Stellar RPC for performance reasons.
 
 For example, calling a method with pagination parameter set: