Grammar tweaking. "has been" is very often not as good as "is" or "was".
This commit is contained in:
parent
043fc4cb15
commit
38a029c121
@ -65,7 +65,7 @@ argument should always be given as a full path name, e.g.\&
|
||||
Running the
|
||||
.Nm
|
||||
utility without any of the optional flags will report the drive type
|
||||
that has been registered with the device driver.
|
||||
that is registered with the device driver.
|
||||
In the shortest form, a single string describing the drive type will
|
||||
be returned.
|
||||
Possible values are:
|
||||
@ -97,7 +97,7 @@ density settings in kilobytes.
|
||||
.Ss Debug Control
|
||||
If the
|
||||
.Xr fdc 4
|
||||
driver has been configured with the
|
||||
driver was configured with the
|
||||
.Dv FDC_DEBUG
|
||||
option, by default, device debugging information is still disabled
|
||||
since it could produce huge amounts of kernel messages.
|
||||
@ -115,7 +115,7 @@ affect any drives and controllers using the
|
||||
.Xr fdc 4
|
||||
driver, regardless which
|
||||
.Ar device
|
||||
has been specified on the
|
||||
was specified on the
|
||||
.Nm
|
||||
command line.
|
||||
.Ss Density Control
|
||||
@ -129,7 +129,7 @@ to specify the format of the medium in kilobytes.
|
||||
Depending on the
|
||||
underlying drive type, the value is compared against a table of known
|
||||
commonly used device density settings for that drive, and if a match
|
||||
has been found, those settings will be used.
|
||||
is found, those settings will be used.
|
||||
Currently, the following
|
||||
values for the respective drive types are acceptable:
|
||||
.Bl -item
|
||||
@ -320,9 +320,9 @@ The
|
||||
.Nm
|
||||
utility appeared in
|
||||
.Fx 2.0 ,
|
||||
and has been vastly overhauled in
|
||||
and was vastly overhauled in
|
||||
.Fx 5.0 .
|
||||
.Sh AUTHORS
|
||||
The program and this man page have been contributed by
|
||||
The program and this man page was contributed by
|
||||
.An J\(:org Wunsch ,
|
||||
Dresden.
|
||||
|
Loading…
x
Reference in New Issue
Block a user