From 9599cbb4a0be0d1d2ea7409fbc63b5bc36cbee82 Mon Sep 17 00:00:00 2001 From: Sai Kumar Date: Fri, 11 Aug 2023 20:49:52 +0530 Subject: [PATCH] fix the markdown lint --- x/leverage/EXAMPLES.md | 6 +++--- x/leverage/README.md | 2 +- 2 files changed, 4 insertions(+), 4 deletions(-) diff --git a/x/leverage/EXAMPLES.md b/x/leverage/EXAMPLES.md index 80609d3e46..e4c677ede9 100644 --- a/x/leverage/EXAMPLES.md +++ b/x/leverage/EXAMPLES.md @@ -53,7 +53,7 @@ However, this actually underestimates the max borrow amount because asset `B` qu What will actually happen, is any newly borrowed `B` will be paired with collateral `A` in the highest priority special asset pair (and also any collateral `A` that is floating around in regular assets) before being matched with leftover collateral. First it will take from the `$10 A` sitting in normal assets (and displace the `$1 D` which was being covered by that collateral onto the unused collateral at the bottom). If the `$1 D` could only be partially moved due to a limited amount of unused collateral, we would compute the amount of `A` collateral that would be freed up, and the resulting size of the `B` max borrow, and return there. -(This logic is a recursive` MaxWithdraw(A)`) +(This logic is a recursive `MaxWithdraw(A)`) Position after first displacement of collateral `A`: @@ -86,7 +86,7 @@ Position after second displacement of collateral `A`: Note that the `(A,C, 0.4)` special pair which was used is now unused, as its collateral was moved to the more efficient pair `(A,B,0.5)`. There is still a little left over collateral `D`, so with all the special pairs dealt with, the ordinary assets can be settled. Due to the rule "borrowed assets are listed by collateral weight, descending" any remaining borrow `B` will insert itself below rows containing borrowed `A`, but above any rows containing borrowed `C` or `D`. -This functions as a recursive` MaxWithdraw(D)` from this example position since only `D` collateral is being affected. +This functions as a recursive `MaxWithdraw(D)` from this example position since only `D` collateral is being affected. Position after final displacement of collateral `D`: | Collateral | Borrow | Weight | Change in Position | @@ -110,4 +110,4 @@ Overall Result: Therefore `MaxBorrow(B) = $25 + $5 + $5 = $35`. -This is greater than the naive estimate of `$26` from the start of the example. +This is greater than the naive estimate of `$26` from the start of the example. diff --git a/x/leverage/README.md b/x/leverage/README.md index 460964d10d..7e6c0121f7 100644 --- a/x/leverage/README.md +++ b/x/leverage/README.md @@ -298,7 +298,7 @@ It will abort and return zero if all collateral is in use. Any user whose borrow value is above their liquidation threshold is eligible to be liquidated. -Each token in the `Token Registry` has a parameter called `LiquidationThreshold`, always greater than or equal to collateral weight, but less than 1, which determines the portion of the token's value that goes towards a borrower's liquidation threshold when the token is used as collateral. +Each token in the `Token Registry` has a parameter called `LiquidationThreshold`, always greater than or equal to collateral weight, but less than 1, which determines the portion of the token's value that goes towards a borrower's liquidation threshold when the token is used as collateral. When a borrow position is limited by simple borrow limit (without special asset pairs or borrow factor), a user's liquidation threshold is the sum of the contributions from each denomination of collateral they have deposited: