diff --git a/Auto‐Updating-wallabag's-site‐depended-config.md b/Auto‐Updating-wallabag's-site‐depended-config.md
index 4940ad9..772b7ea 100644
--- a/Auto‐Updating-wallabag's-site‐depended-config.md
+++ b/Auto‐Updating-wallabag's-site‐depended-config.md
@@ -1,11 +1,11 @@
 Wallabag only updates its config files as part of releases for the wallabag package. However, since these config files originate from another project, they can also be loaded from the original repo into a separate folder and automatically kept up to date there.
 
-#### Prerequisites:
+### Prerequisites:
 
 - A self-hosted instance of wallabag    
 - GIT package installed - or - a self-hosted Fulltext-RSS instance (current versions need a paid license)
 
-#### Do NOT try to...
+### Do NOT try to...
 
 ...auto-update config files directly within wallabag's path under `vendor/j0ker/graby-site-config/`, this would be overwritten when installing a new wallabag update.
 
@@ -76,7 +76,7 @@ Wallabag does not use a new config immediately after it has been updated. Becaus
 
 ### Tip 2: Make backup of config
 
-At the moment config files under `app/configs/` are not persistent. You should do a backup before upgrading your wallabag version. As service.yml will be overwritten, when upgrading wallabag, you need to restore the settings, you mad above.
+At the moment config files under `app/configs/` are not persistent. You should do a backup before upgrading your wallabag version. As service.yml will be overwritten, when upgrading wallabag, you need to restore the settings, you made above.
 
 ### Dockerized wallabag