Update in JSON-RPC info

api/json-rpc.mdx

@@ -12,6 +12,14 @@ To interact with soroban-rpc from inside a JavaScript application, use the [Java
 
 When XDR is passed as a parameter or returned, it is always a string encoded using standard base64.
 
+:::info
+
+Please note that parameter structure must contain named parameters as a by-name
+object, and not as positional arguments as a by-position array. Positional
+arguments as a by-position array will be deprecated in future RPC releases.
+
+:::
+
 ## Open-RPC Specification
 
 Soroban-RPC provides an [OpenRPC] specification document that can be used to mock, build, and/or validate both server and client software implementations. This document is used to generate all of our [methods] documentation pages. You can view the full [specification document here]. Additionally, you can experiment with this specificaiton document in the [OpenRPC Playground].

openrpc/src/contentDescriptors/Transaction.json

@@ -11,7 +11,7 @@
     "UnsignedTransaction": {
         "name": "transaction",
         "summary": "transaction to be simulated",
-        "description": "In order for the RPC server to successfully simulate a Stellar transaction, the provided transaction must contain only a single operation of the type `invokeHostFunction`. Please note that parameter structure within the request must contain named parameters as a by-name object, and not as positional arguments as a by-position array.",
+        "description": "In order for the RPC server to successfully simulate a Stellar transaction, the provided transaction must contain only a single operation of the type `invokeHostFunction`.",
         "required": true,
         "schema": {
             "$ref": "#/components/schemas/Transaction"