--- wikisrc/users/mbalmer/keylock.mdwn	2009/12/29 09:26:30	1.4
+++ wikisrc/users/mbalmer/keylock.mdwn	2020/09/09 15:47:01	1.7
@@ -18,14 +18,17 @@ can access them through the <b>hw.keyloc
 
 The following components have been added:
 
-* '''{{manual page|gpiolock|4|}}''' a driver for GPIO attached keylocks.
+* <b>[[!template id=man name="gpiolock" section="4"]]</b>
+a driver for GPIO attached keylocks.
  The driver registers with the in-kernel keylock "subsystem". See
 [gpiolock.c](http://cvsweb.de.netbsd.org/cgi-bin/cvsweb.cgi/src/sys/dev/gpio/gpiolock.c?rev=HEAD).
 
-* <b>secmodel_keylock</b>, a {{manual page|kauth|9}} security model that
+* <b>secmodel_keylock</b>, a
+[[!template id=man name="kauth" section="9"]]
+security model that
 authorizes based on the keylock "closedness".  Wheter the rightmost
 (default) or leftmost position of the keylock means open can be
-controlled using the '''hw.keylock.order''' sysctl variable. This
+controlled using the <b>hw.keylock.order</b> sysctl variable. This
 variable can only be changed if the keylock state is OPEN. See
 [secmodel_keylock.c](http://cvsweb.de.netbsd.org/cgi-bin/cvsweb.cgi/src/sys/secmodel/keylock/secmodel_keylock.c?rev=HEAD).
 
@@ -49,7 +52,8 @@ that means leaves room for interpretatio
 show what makes sense in the end).
 
 To enable the keylock support, the keylock security model, and the
-{{manual page|gpiolock|4|}} driver, add the following lines to your
+[[!template id=man name="gpiolock" section="4"]]
+driver, add the following lines to your
 kernel configuration file:
 
 	options KEYLOCK
@@ -57,7 +61,8 @@ kernel configuration file:
 	gpiolock* at gpio?
 
 Of course you must have at least one GPIO device in your system for the
-{{manual page|gpiolock|4|}} driver to work and the lock must be
+[[!template id=man name="gpiolock" section="4"]]
+driver to work and the lock must be
 connected properly.
 
 <b>Please keep in mind that this is an experimental feature...</b>