From 91f4c9532080c99880b74e3db480c67b27eb13cd Mon Sep 17 00:00:00 2001 From: Anurag <110373364+pkcs8@users.noreply.github.com> Date: Sat, 7 Oct 2023 01:38:12 +0530 Subject: [PATCH] Update RippleState Reserve description in ripplestate.md 'owner reserve of' text appears twice. --- .../ledger-data/ledger-entry-types/ripplestate.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/references/protocol-reference/ledger-data/ledger-entry-types/ripplestate.md b/content/references/protocol-reference/ledger-data/ledger-entry-types/ripplestate.md index beff667756..c08b41753f 100644 --- a/content/references/protocol-reference/ledger-data/ledger-entry-types/ripplestate.md +++ b/content/references/protocol-reference/ledger-data/ledger-entry-types/ripplestate.md @@ -87,7 +87,7 @@ The two accounts connected by the trust line can each change their own settings ## {{currentpage.name}} Reserve -A `RippleState` entry counts as one item towards the owner reserve of [owner reserve](reserves.html#owner-reserves) of _one or both_ of the accounts it connects. In typical cases, the holder of a token owes a reserve and the issuer of the token does not. +A `RippleState` entry counts as one item towards the [owner reserve](reserves.html#owner-reserves) of _one or both_ of the accounts it connects. In typical cases, the holder of a token owes a reserve and the issuer of the token does not. Specifically, the entry counts towards an account's reserve if that account modifies a trust line to put it in a non-default state. The `lsfLowReserve` and `lsfHighReserve` flags indicate which account(s) are responsible for the owner reserve. The protocol automatically sets these flags when it modifies a trust line.