diff --git a/admin-guide/troubleshooting/pam.md b/admin-guide/troubleshooting/pam.md
index 60889798..63f7d8f1 100644
--- a/admin-guide/troubleshooting/pam.md
+++ b/admin-guide/troubleshooting/pam.md
@@ -3,7 +3,7 @@
 Checking PAM issues can be quite tricky.
 
 
-# Debugging Messages with `pam_echo.so`
+## Debugging Messages with `pam_echo.so`
 
 This can be used to print a message. When placed on every PAM step it shows how far the processing goes and maybe where the error might be:
 
@@ -38,7 +38,7 @@ auth        optional      pam_echo.so "Have passed pam_localuser and pam_unix"
 ```
 
 
-# PAM Call Stack with SystemTap
+## PAM Call Stack with SystemTap
 
 When debugging an PAM issue with the RedHat support, they provided us a neat Systemtab script to create a PAM call stack of the `do_pam_setcred()` function in sshd. You find it [here](pam/para-callgraph-pam.stp).