diff --git a/doc/i2s_memcalc.md b/doc/i2s_memcalc.md
index 47806af..151f6df 100644
--- a/doc/i2s_memcalc.md
+++ b/doc/i2s_memcalc.md
@@ -20,12 +20,12 @@ And there are lot's of hogs for those:
 Equalising ones with the others results in **Refresh rate**,
 
 or (rough approximation) 
-<img src="https://render.githubusercontent.com/render/math?math=RefreshRate=\frac{resolution%20\times%20chain%20\times%20(ColorDepth-LSB2MSB)}{%20I%20^2S%20_%20{clock}%20}">
+<img src="https://render.githubusercontent.com/render/math?math=RefreshRate=\frac{%20I%20^2S%20_%20{clock}%20}{resolution%20\times%20chain%20\times%20(ColorDepth-LSB2MSB)}">
 
 [//]: # (github markdown does not like LaTex formulas)
 [//]: # ($$RefreshRate=\frac{resolution \times chain \times (ColorDepth-LSB2MSB)}{ I ^2S _ {clock} }$$)
 
-So, how to find optimum balance for all of these? Obviously you can't change *resolution* and *chain length*, it is physical characteristics and there is not much you can do about it except cutting of your chain or pushing it to the memory limits.
+So, how to find optimum balance for all of these? Obviously you can't change *resolution* and *chain length*, it is physical characteristics and there is not much you can do about it except cutting off your chain or pushing it to the memory limits.
 
 There are 3 parameters you can choose from (actually two:)
  - **Color Depth** - predefined at [build-time]((/doc/BuildOptions.md)) option
@@ -34,7 +34,7 @@ There are 3 parameters you can choose from (actually two:)
 
 - **LSB-to-MSB** transition - it can't  be controlled in any way, library uses it internaly trying to balance all of the above 
 
-Using provided table it is possible to estimate all of the parameters before running the library. Besides calculating memory requirements it could help to find **optimum color depth** for your matrix configuration. For higher resolutions default 8 bits could be too much to sustain minimal refresh rate and avoid annoying flickering. So the library would increase MSB transition to keep the balance, thus reducing dynamic range in shadows and dark colors. As a result it is nearly almost the same as just reducing overal color depth. **But** reducing global color depth would also saves lot's of precious RAM!
+Using provided table it is possible to estimate all of the parameters before running the library. Besides calculating memory requirements it could help to find **optimum color depth** for your matrix configuration. For higher resolutions default 8 bits could be too much to sustain minimal refresh rate and avoid annoying flickering. So the library would increase MSB transition to keep the balance, thus reducing dynamic range in shadows and dark colors. As a result it is nearly almost the same as just reducing overal color depth. **But** reducing global color depth would also save lot's of precious RAM!
 Now it's all up to you to decide :)
 
-/Vortigont/
\ No newline at end of file
+/Vortigont/
diff --git a/library.json b/library.json
index c66a9b8..fae2fc9 100644
--- a/library.json
+++ b/library.json
@@ -10,7 +10,7 @@
     "name": "Faptastic",
     "url": "https://github.com/mrfaptastic/"
   },
-  "version": "2.0.4",
+  "version": "2.0.5",
   "frameworks": "arduino",
   "platforms": "esp32",
   "examples": [
diff --git a/library.properties b/library.properties
index 6b34d81..01ece86 100644
--- a/library.properties
+++ b/library.properties
@@ -1,5 +1,5 @@
 name=ESP32 HUB75 LED MATRIX PANEL DMA Display
-version=2.0.4
+version=2.0.5
 author=Faptastic
 maintainer=Faptastic 
 sentence=Experimental DMA based LED Matrix HUB75 Library