mirror of
https://github.com/XRPLF/xrpl-dev-portal.git
synced 2025-11-27 23:25:51 +00:00
Migrate content syntax via script
The changes in this commit were auto-generated by running tool/migrate.sh Following this commit, the Dactyl build no longer works but the Redocly build (mostly) should.
This commit is contained in:
@@ -35,11 +35,11 @@ Optional fields are available for all transactions, with additional fields avail
|
||||
|
||||
You send the transaction to the ledger as a command from JavaScript, Python, the command line, or any compatible service. The rippled servers propose transactions to the XRPL.
|
||||
|
||||

|
||||

|
||||
|
||||
When 80% of the validators approve a current set of proposed transactions, they are recorded as part of the permanent ledger. The rippled server returns the results of the transaction you sent.
|
||||
|
||||
For more information on Transactions, see [Transactions](transactions.html).
|
||||
For more information on Transactions, see [Transactions](../concepts/transactions/index.md).
|
||||
|
||||
## How Do Requests Work?
|
||||
|
||||
@@ -49,7 +49,7 @@ The fields you send vary with the type of information you request. They typicall
|
||||
|
||||
When you submit your request, it might be processed by a rippled server or by a Clio server, a server that is dedicated to responding to requests.
|
||||
|
||||

|
||||

|
||||
|
||||
Clio servers take some of the load off the other rippled servers on the XRPL to improve processing speed and reliability.
|
||||
|
||||
@@ -109,7 +109,6 @@ The request returns a wealth of information. Here is an example response for an
|
||||
}
|
||||
}
|
||||
```
|
||||
For information on the fields in an Account record, see [Accounts](accounts.html).
|
||||
|
||||
Next: [Software Ecosystem](software-ecosystem.html)
|
||||
For information on the fields in an Account record, see [Accounts](../concepts/accounts/accounts.md).
|
||||
|
||||
Next: [Software Ecosystem](software-ecosystem.md)
|
||||
|
||||
Reference in New Issue
Block a user