Markup fixes.

1 files changed, 16 insertions, 16 deletions

diff --git a/share/man/man4/vkbd.4 b/share/man/man4/vkbd.4
index 40ec4bce..dcba17d 100644
--- a/share/man/man4/vkbd.4
+++ b/share/man/man4/vkbd.4
@@ -8,7 +8,7 @@
 .Nm vkbd
 .Nd the virtual AT keyboard interface
 .Sh SYNOPSIS
-.Cd device vkbd
+.Cd "device vkbd"
 .Sh DESCRIPTION
 The
 .Nm
@@ -18,25 +18,24 @@ described as the virtual AT keyboard analog of the
 that is,
 .Nm
 does for virtual AT keyboards what the
-.Nm pty
+.Xr pty 4
 driver does for terminals.
 .Pp
 The
 .Nm
 driver, like the
-.Nm pty
+.Xr pty 4
 driver, provides two interfaces: a keyboard interface like the usual
 facility it is simulating (a virtual AT keyboard in the case of
 .Nm ,
 or a terminal for
-.Nm pty ) ,
+.Xr pty 4 ) ,
 and a character-special device
 .Dq control
 interface.
 .Pp
 The virtual AT keyboards are named
-.Dq Li vkbd0 ,
-.Dq Li vkbd1 ,
+.Pa vkbd0 , vkbd1 ,
 etc., one for each control device that has been opened.
 .Pp
 The
@@ -46,26 +45,26 @@ interface permits opens on the special control device
 When this device is opened,
 .Nm
 will return a handle for the lowest unused
-.Nm vkbdctl
+.Pa vkbdctl
 device (use
 .Xr devname 3
 to determine which).
 .Pp
-Each virtual AT keyboad supports the usual keyboard interface
+Each virtual AT keyboard supports the usual keyboard interface
 .Xr ioctl 2 Ns s ,
 and thus can be used with
 .Xr kbdcontrol 1
 like any other keyboard.
 The control device supports exactly the same
 .Xr ioctl 2 Ns s
-as the virtual AT keyboad device.
+as the virtual AT keyboard device.
 Writing AT scan codes to the control device generates an input on
 the virtual AT keyboard, as if the
 (non-existent)
 hardware had just received it.
 .Pp
-The virtual AT kerboard control device, normally
-.Pa /dev/vkbdctl Ns Sy N ,
+The virtual AT keyboard control device, normally
+.Pa /dev/vkbdctl Ns Aq Ar N ,
 is exclusive-open
 (it cannot be opened if it is already open)
 and is restricted to the super-user.
@@ -85,12 +84,12 @@ call passes AT scan codes to be
 .Dq received
 from the virtual AT keyboard.
 Each AT scan code must be passed as
-.Vt unsigned int .
+.Vt "unsigned int" .
 Although AT scan codes must be passes as
-.Vt unsigned int Ns s ,
+.Vt "unsigned int" Ns s ,
 the size of the buffer passed to
 .Xr write 2
-still should be in bytes, i.e.
+still should be in bytes, i.e.,
 .Bd -literal -offset indent
 static unsigned int     codes[] =
 {
@@ -141,8 +140,9 @@ will not work with it.
 Current implementation of the
 .Xr syscons 4
 driver can accept input from only one keyboard, even if it is virtual.
-Thus is it not possible to have both wired and virtual keyboard to be active
-at the same time. It is, however, in principal possible to obtain AT scan
+Thus it is not possible to have both wired and virtual keyboard to be active
+at the same time.
+It is, however, in principal possible to obtain AT scan
 codes from the different sources and write them into the same virtual keyboard.
 The virtual keyboard state synchronization is the user's responsibility.
 .Sh HISTORY