diff --git a/Debugging-your-Config.md b/Debugging-your-Config.md
index dec9f2d..56aa922 100644
--- a/Debugging-your-Config.md
+++ b/Debugging-your-Config.md
@@ -34,7 +34,7 @@ modules are not displayed.
 back to it if you open a new issue.*
 
 Now we need to figure out where exactly the issue lies. This will make it easier for you to diagnose and fix the it.
-We do this with a so called *Minimal, Complete, and Verifiable example* ([mvce](https://stackoverflow.com/help/mcve)).
+We do this with a so called *Minimal, Complete, and Verifiable example* ([mcve](https://stackoverflow.com/help/mcve)).
 The idea is to create a setup where you still have the same problems but with all unnecessary parts stripped out.
 Note that you should not only make your config minimal but also your startup routine, preferably you should start a 
 single polybar instance from the terminal.
@@ -45,7 +45,7 @@ try to run polybar directly from the terminal. If polybar starts from the termin
 with your WM startup routine is causing issues. If it doesn't start, you know the problem lies somewhere else. Without 
 this information you might end up spending a lot of time searching in the wrong places.
 
-Such an MVCE is not only helpful to you but also to people you might end up asking for help. No one wants to see errors
+Such an MCVE is not only helpful to you but also to people you might end up asking for help. No one wants to see errors
 about your missing custom scripts when they help you debug issues with the pulseaudio module. It also shows that you
 have invested time to try and fix the problem yourself and because of that people may be more inclined to help you than
 when you just drop 200 lines of configs on them with the comment "It doesn't work".
@@ -62,7 +62,7 @@ Also consult the [Known Issues](https://github.com/polybar/polybar/wiki/Known-Is
 
 If you completed all the steps above and weren't able to fix the issue yourself, it may be time to ask someone for help.
 On our [SUPPORT.md](https://github.com/polybar/polybar/blob/master/SUPPORT.md) page, you can find resources where you can 
-ask for help. When you finally do reach out, make sure to include the MVCE that you created above as well as precise 
+ask for help. When you finally do reach out, make sure to include the MCVE that you created above as well as precise 
 instructions on how to reproduce your issue.
 
 It is possible that the issue you have experienced is not caused by an incorrect configuration but by an actual bug