ARCHIVE/xrpl-dev-portal
1
0
Fork 0
mirror of https://github.com/XRPLF/xrpl-dev-portal.git synced 2025-11-12 15:55:49 +00:00
Code Issues Packages Projects Releases Wiki Activity

Merge pull request #31 from mDuo13/gh-pages

Browse Source 
fixed typo in websocket
This commit is contained in:
Rome Reginelli
2014-08-28 16:30:56 -07:00
parent 2474c49200 ddbf50edb6
commit 9149fa9159
1 changed files with 3 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
websocket_api.md
View File

@@ -298,11 +298,11 @@ All field names are case-sensitive. In responses, fields that are taken directly
Different types of objects are uniquely identified in different ways:
*Accounts* are identified by their *address*, a base-58-encoded string, for example `"r9cZA1mLK5R5Am25ArfXFmqgNwjZgnfk59`". Addresses always start with "r". You can also provide an un-encoded hex representation instead.
*Accounts* are identified by their *address*, a [base-58-encoded](https://wiki.ripple.com/Encodings) string, for example `"r9cZA1mLK5R5Am25ArfXFmqgNwjZgnfk59"`. Addresses always start with "r". You can also provide an un-encoded hex representation instead.
Transactions are identified by their *hash*, which is a [SHA-512](http://en.wikipedia.org/wiki/Sha512) hash of the transaction's binary format. Transaction hashes are represented as hex strings.
*Transactions* are identified by their *hash*, which is a [SHA-512](http://en.wikipedia.org/wiki/Sha512) hash of the transaction's binary format. Transaction hashes are represented as hex strings.
Each instance of the Ripple Ledger has a sequence number and a hash value. See [Specifying a Ledger Instance](#specifying-a-ledger-instance) for details.
Each instance of the Ripple *Ledger* has a sequence number and a hash value. See [Specifying a Ledger Instance](#specifying-a-ledger-instance) for details.
### Specifying a Ledger Instance ###