From ddbf50edb6ad2fef8f727e6d50302aae073bd8d4 Mon Sep 17 00:00:00 2001 From: mDuo13 Date: Thu, 28 Aug 2014 16:29:34 -0700 Subject: [PATCH] fixed typo in websocket --- websocket_api.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/websocket_api.md b/websocket_api.md index 83c4bac4da..eb324e4c21 100644 --- a/websocket_api.md +++ b/websocket_api.md @@ -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 ###