From 7c92da08c82f4679df7e48ca4667e21dd4d262cd Mon Sep 17 00:00:00 2001 From: Gavin Wood Date: Mon, 17 Jul 2023 11:59:39 +0200 Subject: [PATCH] Update text/0001-agile-coretime.md Co-authored-by: Muharem Ismailov --- text/0001-agile-coretime.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/text/0001-agile-coretime.md b/text/0001-agile-coretime.md index a85ea9f..84eb337 100644 --- a/text/0001-agile-coretime.md +++ b/text/0001-agile-coretime.md @@ -156,7 +156,7 @@ The eventual usage of the funds paid is out of scope for the present proposal. #### Renewals -At any time when there are there are remaining Regions of Bulk Coretime to be sold, *including during the Interlude Period*, then certain Bulk Coretime assignmnents may be *Renewed*. This is similar to a purchase in that funds must be paid and it consumes one of the Regions of Bulk Coretime which would otherwise be placed for purchase. However there are two key differences. +At any time when there are remaining Regions of Bulk Coretime to be sold, *including during the Interlude Period*, then certain Bulk Coretime assignmnents may be *Renewed*. This is similar to a purchase in that funds must be paid and it consumes one of the Regions of Bulk Coretime which would otherwise be placed for purchase. However there are two key differences. Firstly, the price paid is exactly `RENEWAL_PRICE_CAP` more than what the purchase/renewal price was in the previous sale.