fix: correct pagination limits for getLedgers and getTransactions in OpenRPC spec

Author: miguelnietoa

static/stellar-rpc.openrpc.json

@@ -902,7 +902,7 @@
               },
               "limit": {
                 "type": "number",
-                "description": "The maximum number of records returned. The limit for getEvents 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."
+                "description": "The maximum number of records returned. The limit for getLedgers can range from 1 to 200 - an upper limit that is hardcoded in Stellar-RPC for performance reasons. If this argument isn't designated, it defaults to 50."
               }
             }
           }
@@ -1391,7 +1391,7 @@
               },
               "limit": {
                 "type": "number",
-                "description": "The maximum number of records returned. The limit for getEvents 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."
+                "description": "The maximum number of records returned. The limit for getTransactions can range from 1 to 200 - an upper limit that is hardcoded in Stellar-RPC for performance reasons. If this argument isn't designated, it defaults to 50."
               }
             }
           }
@@ -2415,4 +2415,4 @@
     }
   ],
   "components": {}
-}
+}