diff --git a/i2p2www/blog/2021/12/11/i2p-unaffected-cve-2021-44228.draft.rst b/i2p2www/blog/2021/12/11/i2p-unaffected-cve-2021-44228.draft.rst
index 37eb8e351b62e16d4b3da4fcc7a7e9e487e0386a..e1299e2ac3e6362e3fe0c956512300b3a38fd545 100644
--- a/i2p2www/blog/2021/12/11/i2p-unaffected-cve-2021-44228.draft.rst
+++ b/i2p2www/blog/2021/12/11/i2p-unaffected-cve-2021-44228.draft.rst
@@ -1,6 +1,6 @@
-===========================================
+==============================================
 {% trans -%}I2P is not affected by the log4j vulnerability{%- endtrans %}
-===========================================
+==============================================
 
 .. meta::
    :author: idk, zzz
@@ -8,11 +8,6 @@
    :category: security
    :excerpt: {% trans %}I2P doesn't use log4j and is therefore unaffected by CVE-2021-44228{% endtrans %}
 
-{% trans -%}
-Update details
-{%- endtrans %}
-============================================
-
 {% trans -%}
 I2P is not affected by the log4j 0-Day vulnerability which was published
 yesterday, CVE-2021-44228. I2P doesn't use log4j for logging, however we also