From 3498eb484a380ce2238efbc370374dc6301d0656 Mon Sep 17 00:00:00 2001 From: Toh4iem9 Date: Sun, 5 Jul 2026 23:49:17 +0200 Subject: [PATCH] docs: Strict --- .../Authors/Ehlers/1_Smoothers/Zero-Lag_EMA_Pro_Suite.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Indicators/MyIndicators/Authors/Ehlers/1_Smoothers/Zero-Lag_EMA_Pro_Suite.md b/Indicators/MyIndicators/Authors/Ehlers/1_Smoothers/Zero-Lag_EMA_Pro_Suite.md index 54fbce1..b35960b 100644 --- a/Indicators/MyIndicators/Authors/Ehlers/1_Smoothers/Zero-Lag_EMA_Pro_Suite.md +++ b/Indicators/MyIndicators/Authors/Ehlers/1_Smoothers/Zero-Lag_EMA_Pro_Suite.md @@ -60,7 +60,7 @@ $$\text{ZLEMA}_t = \alpha \times \left( \text{EMA}_t + \text{best\_gain} \times The entire suite is optimized to conform with our strict quantitative design guidelines: -* **Szigorú Chronological Sorting Safeguards:** +* **Strict Chronological Sorting Safeguards:** Because both the Double EMA and the Ehlers Optimized Gain calculations rely on a highly state-sensitive recursive history ($t-1$), any reverse-chronological array indexing will completely corrupt the calculations. To prevent this, the suite enforces chronological sorting (`ArraySetAsSeries(..., false)`) on all price inputs inside `OnCalculate()`. This is also applied inside all internal resizes within the calculator classes. * **Memory Safety Validation (Pointer Guards):**