summaryrefslogtreecommitdiffstats
path: root/share/man
diff options
context:
space:
mode:
authorru <ru@FreeBSD.org>2005-02-15 09:27:00 +0000
committerru <ru@FreeBSD.org>2005-02-15 09:27:00 +0000
commit136924cea45cc799b4b1febb17cd957209a402dc (patch)
tree7740d2d81dc57b79cd3c665d31a2acab1dc04e7b /share/man
parent5cd9fb8f6ce21f7176161abbb37102691daf739b (diff)
downloadFreeBSD-src-136924cea45cc799b4b1febb17cd957209a402dc.zip
FreeBSD-src-136924cea45cc799b4b1febb17cd957209a402dc.tar.gz
Expand contractions.
Diffstat (limited to 'share/man')
-rw-r--r--share/man/man4/lpt.42
-rw-r--r--share/man/man4/pass.42
-rw-r--r--share/man/man9/buf.92
3 files changed, 3 insertions, 3 deletions
diff --git a/share/man/man4/lpt.4 b/share/man/man4/lpt.4
index 3856652..8b3dd57 100644
--- a/share/man/man4/lpt.4
+++ b/share/man/man4/lpt.4
@@ -74,7 +74,7 @@ In order to retrieve printer info from /dev/lpt0, just apply the
.Nm cat
command to the device.
If the printer supports IEEE1284 nibble mode and has
-data to send to the host, you'll get it.
+data to send to the host, you will get it.
.Sh FILES
.Bl -tag -width Pa -compact
.It Pa /dev/lpt0
diff --git a/share/man/man4/pass.4 b/share/man/man4/pass.4
index e3f8c01..b96d6ba 100644
--- a/share/man/man4/pass.4
+++ b/share/man/man4/pass.4
@@ -85,7 +85,7 @@ corresponding to the device in question.
Although this ioctl is available through the
.Nm
driver, it is of limited use, since the caller must already know that
-the device in question is a passthrough device if they're issuing this
+the device in question is a passthrough device if they are issuing this
ioctl.
It is probably more useful to issue this ioctl through the
.Xr xpt 4
diff --git a/share/man/man9/buf.9 b/share/man/man9/buf.9
index 2343e27..5ee05f3 100644
--- a/share/man/man9/buf.9
+++ b/share/man/man9/buf.9
@@ -73,7 +73,7 @@ size is 4096).
.Pp
VM buffers also keep track of a byte-granular dirty range and valid range.
This feature is normally only used by the NFS subsystem.
-I'm not sure why it
+I am not sure why it
is used at all, actually, since we have DEV_BSIZE valid/dirty granularity
within the VM buffer.
If a buffer dirty operation creates a 'hole',
OpenPOWER on IntegriCloud