Assorted markup, grammar, and spelling fixes.

3 files changed, 22 insertions, 19 deletions

diff --git a/usr.sbin/bluetooth/hcsecd/hcsecd.conf.5 b/usr.sbin/bluetooth/hcsecd/hcsecd.conf.5
index d27025f..189ca66 100644
--- a/usr.sbin/bluetooth/hcsecd/hcsecd.conf.5
+++ b/usr.sbin/bluetooth/hcsecd/hcsecd.conf.5
@@ -42,14 +42,16 @@ Bluetooth link keys/PIN codes management daemon.
 .Pp
 The
 .Nm
-file is a free-form ASCII text file.
+file is a free-form
+.Tn ASCII
+text file.
 It is parsed by the recursive-descent parser built into
 .Xr hcsecd 8 .
 The file may contain extra tabs and newlines for formatting purposes.
 Keywords in the file are case-sensitive.
 Comments may be placed anywhere within the file (except within quotes).
 Comments begin with the
-.Dq #
+.Ql #
 character and end at the end of the line.
 .Sh FILE FORMAT
 The
@@ -74,29 +76,29 @@ entry
 .Oc
 }
 .Pp
-The following section describes all supported options and arguments
+The following section describes all supported options and arguments.
 .Bl -tag -width indent
 .It Cm bdaddr Ar BD_ADDR
 Specify remote device BD_ADDR for the entry.
 .It Cm name Ar device_name
 Specify user friendly name for the entry.
-Name is a string in a straight double quotes.
+Name is a string in straight double quotes.
 .It Cm key Ar link_key
 Specify link key for the entry.
-Link key is hexadecimal string upto 32 characters in length starting with
-.Dq 0x .
+Link key is hexadecimal string up to 32 characters in length starting with
+.Ql 0x .
 .It Cm key nokey
 Specify no link key for the entry.
 .It Cm pin Ar PIN_code
 Specify PIN code for the entry.
-PIN code is a string upto 16 characters in length in a straight double quotes.
+PIN code is a string up to 16 characters in length in straight double quotes.
 .It Cm pin nopin
 Specify no PIN code for the entry.
 .El
 .Sh EXAMPLES
 A sample
 .Nm
-file
+file:
 .Bd -literal
 # Default entry is applied if no better match found
 # It MUST have 00:00:00:00:00:00 as bdaddr
diff --git a/usr.sbin/bluetooth/sdpcontrol/sdpcontrol.8 b/usr.sbin/bluetooth/sdpcontrol/sdpcontrol.8
index b37c47d..1478aee 100644
--- a/usr.sbin/bluetooth/sdpcontrol/sdpcontrol.8
+++ b/usr.sbin/bluetooth/sdpcontrol/sdpcontrol.8
@@ -51,7 +51,7 @@ Remote SDP servers are identified by their BD_ADDRs.
 Connection to the local SDP server is made via control socket.
 The
 .Nm
-utility will use Service Search Attribute Request and will print results to 
+utility will use Service Search Attribute Request and will print results to
 the standard output and error messages to the standard error.
 .Pp
 The options are as follows:
@@ -95,6 +95,7 @@ utility only implements client side functionality.
 The
 .Nm
 utility only requests the following attributes from the SDP server:
+.Pp
 .Bl -enum -offset indent -compact
 .It
 Service Record Handle
diff --git a/usr.sbin/bluetooth/sdpd/sdpd.8 b/usr.sbin/bluetooth/sdpd/sdpd.8
index 38f4c6b..3bd46c8 100644
--- a/usr.sbin/bluetooth/sdpd/sdpd.8
+++ b/usr.sbin/bluetooth/sdpd/sdpd.8
@@ -79,24 +79,24 @@ The default path is
 Specifies the group the
 .Nm
 should run as after it initializes.
-The value specified may be either a group name or a numeric group id.
+The value specified may be either a group name or a numeric group ID.
 This only works if
 .Nm
 was started as root.
 The default group name is
-.Dq nobody .
+.Dq Li nobody .
 .It Fl h
 Display usage message and exit.
 .It Fl u Ar user
 Specifies the user the
 .Nm
 should run as after it initializes.
-The value specified may be either a user name or a numeric user id.
+The value specified may be either a user name or a numeric user ID.
 This only works if
 .Nm
 was started as root.
 The default user name is
-.Dq nobody .
+.Dq Li nobody .
 .El
 .Sh CAVEAT
 The
@@ -107,21 +107,21 @@ will listen for incoming L2CAP connections on a wildcard BD_ADDR.
 In case of multiple Bluetooth devices connected to the same host it is
 possible to specify which services should be
 .Dq bound
-to which Bluetooth device. Such assigment should be done at service
-registration time.
+to which Bluetooth device.
+Such assigment should be done at service registration time.
 .Pp
 Access rights on the control socket define which application can register,
 remove or change the service.
 The application must be able to write to and read from the control socket
-in order to perform any query to the Service Database via control socket. 
+in order to perform any query to the Service Database via control socket.
 .Pp
 The
 .Nm
-daemon does not checks for duplicated Service Records.
-It only performs minimal check on the service data sent in the Service
+daemon does not check for duplicated Service Records.
+It only performs minimal checking on the service data sent in the Service
 Register request.
 It is assumed that application must obtain all required resources such
-as RFCOMM channels etc. before registering the service.
+as RFCOMM channels etc., before registering the service.
 .Sh BUGS
 Most likely.
 Please report if found.