diff --git a/conf/radiusd/mschap.conf.example b/conf/radiusd/mschap.conf.example
index d9be0676a82a..b6e761664bd3 100644
--- a/conf/radiusd/mschap.conf.example
+++ b/conf/radiusd/mschap.conf.example
@@ -377,7 +377,7 @@ mschap chrooted_mschap {
 #	retry_msg = "Re-enter (or reset) the password"
 }
 
-	mschap chrooted_mschap_mppe {
+mschap chrooted_mschap_mppe {
 	#
 	#  If you are using /etc/smbpasswd, see the 'passwd'
 	#  module for an example of how to use /etc/smbpasswd
@@ -457,109 +457,109 @@ mschap chrooted_mschap {
 	#  connection pool.
 	#
 	pool {
-#  Connections to create during module instantiation.
-#  If the server cannot create specified number of
-#  connections during instantiation it will exit.
-#  Set to 0 to allow the server to start without the
-#  winbind daemon being available.
-start = ${thread[pool].start_servers}
+		#  Connections to create during module instantiation.
+		#  If the server cannot create specified number of
+		#  connections during instantiation it will exit.
+		#  Set to 0 to allow the server to start without the
+		#  winbind daemon being available.
+		start = ${thread[pool].start_servers}
 
-#  Minimum number of connections to keep open
-min = ${thread[pool].min_spare_servers}
+		#  Minimum number of connections to keep open
+		min = ${thread[pool].min_spare_servers}
 
-#  Maximum number of connections
-#
-#  If these connections are all in use and a new one
-#  is requested, the request will NOT get a connection.
-#
-#  Setting 'max' to LESS than the number of threads means
-#  that some threads may starve, and you will see errors
-#  like 'No connections available and at max connection limit'
-#
-#  Setting 'max' to MORE than the number of threads means
-#  that there are more connections than necessary.
-max = ${thread[pool].max_servers}
+		#  Maximum number of connections
+		#
+		#  If these connections are all in use and a new one
+		#  is requested, the request will NOT get a connection.
+		#
+		#  Setting 'max' to LESS than the number of threads means
+		#  that some threads may starve, and you will see errors
+		#  like 'No connections available and at max connection limit'
+		#
+		#  Setting 'max' to MORE than the number of threads means
+		#  that there are more connections than necessary.
+		max = ${thread[pool].max_servers}
 
-#  Spare connections to be left idle
-#
-#  NOTE: Idle connections WILL be closed if "idle_timeout"
-#  is set.  This should be less than or equal to "max" above.
-spare = ${thread[pool].max_spare_servers}
+		#  Spare connections to be left idle
+		#
+		#  NOTE: Idle connections WILL be closed if "idle_timeout"
+		#  is set.  This should be less than or equal to "max" above.
+		spare = ${thread[pool].max_spare_servers}
 
-#  Number of uses before the connection is closed
-#
-#  0 means "infinite"
-uses = 0
+		#  Number of uses before the connection is closed
+		#
+		#  0 means "infinite"
+		uses = 0
 
-#  The number of seconds to wait after the server tries
-#  to open a connection, and fails.  During this time,
-#  no new connections will be opened.
-retry_delay = 30
+		#  The number of seconds to wait after the server tries
+		#  to open a connection, and fails.  During this time,
+		#  no new connections will be opened.
+		retry_delay = 30
 
-#  The lifetime (in seconds) of the connection
-#
-#  NOTE: A setting of 0 means infinite (no limit).
-lifetime = 86400
+		#  The lifetime (in seconds) of the connection
+		#
+		#  NOTE: A setting of 0 means infinite (no limit).
+		lifetime = 86400
 
-#  The pool is checked for free connections every
-#  "cleanup_interval".  If there are free connections,
-#  then one of them is closed.
-cleanup_interval = 300
+		#  The pool is checked for free connections every
+		#  "cleanup_interval".  If there are free connections,
+		#  then one of them is closed.
+		cleanup_interval = 300
 
-#  The idle timeout (in seconds).  A connection which is
-#  unused for this length of time will be closed.
-#
-#  NOTE: A setting of 0 means infinite (no timeout).
-idle_timeout = 600
-
-#  NOTE: All configuration settings are enforced.  If a
-#  connection is closed because of "idle_timeout",
-#  "uses", or "lifetime", then the total number of
-#  connections MAY fall below "min".  When that
-#  happens, it will open a new connection.  It will
-#  also log a WARNING message.
-#
-#  The solution is to either lower the "min" connections,
-#  or increase lifetime/idle_timeout.
-}
+		#  The idle timeout (in seconds).  A connection which is
+		#  unused for this length of time will be closed.
+		#
+		#  NOTE: A setting of 0 means infinite (no timeout).
+		idle_timeout = 600
 
-passchange {
-# This support MS-CHAPv2 (not v1) password change
-# requests.  See doc/mschap.rst for more IMPORTANT
-# information.
-#
-# Samba/ntlm_auth - if you are using ntlm_auth to
-# validate passwords, you will need to use ntlm_auth
-# to change passwords.  Uncomment the three lines
-# below, and change the path to ntlm_auth.
-#
-#		ntlm_auth = "/usr/bin/ntlm_auth --helper-protocol=ntlm-change-password-1"
-#		ntlm_auth_username = "username: %{mschap:User-Name}"
-#		ntlm_auth_domain = "nt-domain: %{mschap:NT-Domain}"
+		#  NOTE: All configuration settings are enforced.  If a
+		#  connection is closed because of "idle_timeout",
+		#  "uses", or "lifetime", then the total number of
+		#  connections MAY fall below "min".  When that
+		#  happens, it will open a new connection.  It will
+		#  also log a WARNING message.
+		#
+		#  The solution is to either lower the "min" connections,
+		#  or increase lifetime/idle_timeout.
+	}
 
-# To implement a local password change, you need to
-# supply a string which is then expanded, so that the
-# password can be placed somewhere.  e.g. passed to a
-# script (exec), or written to SQL (UPDATE/INSERT).
-# We give both examples here, but only one will be
-# used.
-#
-#		local_cpw = "%{exec:/path/to/script %{mschap:User-Name} %{MS-CHAP-New-Cleartext-Password}}"
-#
-#		local_cpw = "%{sql:UPDATE radcheck set value='%{MS-CHAP-New-NT-Password}' where username='%{SQL-User-Name}' and attribute='NT-Password'}"
-}
+	passchange {
+		# This support MS-CHAPv2 (not v1) password change
+		# requests.  See doc/mschap.rst for more IMPORTANT
+		# information.
+		#
+		# Samba/ntlm_auth - if you are using ntlm_auth to
+		# validate passwords, you will need to use ntlm_auth
+		# to change passwords.  Uncomment the three lines
+		# below, and change the path to ntlm_auth.
+		#
+		#		ntlm_auth = "/usr/bin/ntlm_auth --helper-protocol=ntlm-change-password-1"
+		#		ntlm_auth_username = "username: %{mschap:User-Name}"
+		#		ntlm_auth_domain = "nt-domain: %{mschap:NT-Domain}"
 
-# For Apple Server, when running on the same machine as
-# Open Directory.  It has no effect on other systems.
-#
-#	use_open_directory = yes
+		# To implement a local password change, you need to
+		# supply a string which is then expanded, so that the
+		# password can be placed somewhere.  e.g. passed to a
+		# script (exec), or written to SQL (UPDATE/INSERT).
+		# We give both examples here, but only one will be
+		# used.
+		#
+		#		local_cpw = "%{exec:/path/to/script %{mschap:User-Name} %{MS-CHAP-New-Cleartext-Password}}"
+		#
+		#		local_cpw = "%{sql:UPDATE radcheck set value='%{MS-CHAP-New-NT-Password}' where username='%{SQL-User-Name}' and attribute='NT-Password'}"
+	}
 
-# On failure, set (or not) the MS-CHAP error code saying
-# "retries allowed".
-allow_retry = no
+	# For Apple Server, when running on the same machine as
+	# Open Directory.  It has no effect on other systems.
+	#
+	#	use_open_directory = yes
 
-# An optional retry message.
-#	retry_msg = "Re-enter (or reset) the password"
+	# On failure, set (or not) the MS-CHAP error code saying
+	# "retries allowed".
+	allow_retry = no
+
+	# An optional retry message.
+	#	retry_msg = "Re-enter (or reset) the password"
 }
 
 mschap chrooted_mschap_machine {