From d2be3e131174d81d4407cf1625f781f4ad3b3d1b Mon Sep 17 00:00:00 2001
From: Alex Oranov <114924866+AOranov@users.noreply.github.com>
Date: Mon, 1 May 2023 14:24:41 +0300
Subject: [PATCH] Update LqMiningSimple.md

---
 protocols/LqMiningSimple.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/protocols/LqMiningSimple.md b/protocols/LqMiningSimple.md
index f6f9f6d..b97acce 100644
--- a/protocols/LqMiningSimple.md
+++ b/protocols/LqMiningSimple.md
@@ -19,7 +19,7 @@ Liquidity Mining (LM) Pool is represented on-chain as a UTxO with the following
 | `epoch`            | `Int`       | Index of the epoch being compounded                           |
 
 _Notes_:
-* `maxRoundingError` can be estimated as `epochNum` . Since the exact number of participants is difficult to predict in advance,
+* `maxRoundingError` can be estimated as `epochNum`. Since the exact number of participants is difficult to predict in advance,
 It is convenient to choose a larger value, but it should be << `programBudget / epochNum` . If the `maxRoundingError` value is too small, the **LM program may break**,
 and if the value is too large, the **distribution of rewards may be incorrect**!
 * `execBudget` is **not necessary** for Self-Hosted LM Pool
@@ -74,7 +74,7 @@ Creator will have to monitor ERGs balance and perform additional deposits.
 #### General LM Pool initialization rules
 When initializing an LM Pool (Self-Hosted or Delegated), the following actions **must be performed:**
 1. Correct config: 
-   1. `epochNum` <= `maxRoundingError` << `programBudget / epochNum`
+   1. `epochNum` < `maxRoundingError` << `programBudget / epochNum`
    2. `programBudget` stored in R5 of the LM Pool Box == (Total LM program budget - 1L)
 
 2. Initial transaction with correct tokens' amounts, the creator of the LM Pool should also Deposit