--- wikisrc/users/mbalmer/keylock.mdwn	2009/12/29 09:31:15	1.6
+++ wikisrc/users/mbalmer/keylock.mdwn	2020/09/09 15:47:01	1.7
@@ -18,13 +18,13 @@ can access them through the <b>hw.keyloc
 
 The following components have been added:
 
-* <b>[gpiolock(4)](http://netbsd.gw.com/cgi-bin/man-cgi?gpiolock+4+NetBSD-current)</b>
+* <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
-[kauth(9)](http://netbsd.gw.com/cgi-bin/man-cgi?kauth+9+NetBSD-current)
+[[!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
@@ -52,7 +52,7 @@ that means leaves room for interpretatio
 show what makes sense in the end).
 
 To enable the keylock support, the keylock security model, and the
-[gpiolock(4)](http://netbsd.gw.com/cgi-bin/man-cgi?gpiolock+4+NetBSD-current)
+[[!template id=man name="gpiolock" section="4"]]
 driver, add the following lines to your
 kernel configuration file:
 
@@ -61,7 +61,7 @@ kernel configuration file:
 	gpiolock* at gpio?
 
 Of course you must have at least one GPIO device in your system for the
-[gpiolock(4)](http://netbsd.gw.com/cgi-bin/man-cgi?gpiolock+4+NetBSD-current)
+[[!template id=man name="gpiolock" section="4"]]
 driver to work and the lock must be
 connected properly.