From: Sascha Wildner Date: Thu, 4 Mar 2010 06:00:42 +0000 (+0100) Subject: Fix typos in manual pages and user visible messages. X-Git-Tag: v2.7.0~114^2~4 X-Git-Url: https://gitweb.dragonflybsd.org/dragonfly.git/commitdiff_plain/3da63b93f64e24991407a84484525c737926c42f Fix typos in manual pages and user visible messages. --- diff --git a/sbin/disklabel64/disklabel64.8 b/sbin/disklabel64/disklabel64.8 index 623b95a230..234b9761d6 100644 --- a/sbin/disklabel64/disklabel64.8 +++ b/sbin/disklabel64/disklabel64.8 @@ -562,7 +562,7 @@ Your mileage may vary. .Dl "disklabel64 -B -r -w da0s0 auto" .Dl "disklabel64 -e da0s0" .Sh ALIGNMENT -When a virgin disklabel64 is layed down a +When a virgin disklabel64 is laid down a .Dx 2.5 or later kernel will align the partition start offset relative to the physical drive instead of relative to the slice start. diff --git a/sbin/md5/md5.1 b/sbin/md5/md5.1 index 1e08d083b8..8d863b1702 100644 --- a/sbin/md5/md5.1 +++ b/sbin/md5/md5.1 @@ -93,12 +93,12 @@ The use of offsets is implemented using .Fn mmap and will only work on regular files and mmap-able devices. .Pp -If the beginning offset is negative, its absolute value is substracted +If the beginning offset is negative, its absolute value is subtracted from the file's size. Zero thus means the very beginning of each file, which is also the default if the option is omitted entirely. .It Fl e Ar offset -If the end-offset is not positive, its absolute value is substracted +If the end-offset is not positive, its absolute value is subtracted from the file's size. Zero thus means the very end of each file, which is also the default if the option is omitted entirely. diff --git a/share/man/man5/tmpfs.5 b/share/man/man5/tmpfs.5 index 1df592dec6..e2184f0234 100644 --- a/share/man/man5/tmpfs.5 +++ b/share/man/man5/tmpfs.5 @@ -76,18 +76,18 @@ Normal filesystem operations such as fsync(), buffer cache flushing, and vnode recycling have no effect. .Pp .Nm -stores meta-data in wired kernel memory. Meta-data is not backed by -swap so care must be taken if using +stores meta-data in wired kernel memory. +Meta-data is not backed by swap so care must be taken if using .Nm to store large numbers of small files. .Pp It is recommended that a large amount of swap space be reserved on modern .Dx -platforms to accomodate +platforms to accommodate .Nm and other subsystems. -32-bit kernels can accomodate 32G of swap by default while 64-bit kernels -can accomodate 512G of swap by default. +32-bit kernels can accommodate 32G of swap by default while 64-bit kernels +can accommodate 512G of swap by default. These defaults can be increased though it should be noted that 32-bit kernels are ultimately limited by the amount of KVM available in its small 32-bit address space. @@ -97,7 +97,7 @@ will allocate and deallocate swap backing store on the fly based on usage. By default .Nm allows up to 100% of swap space to be used. -If this is not desireable then the size option should be used to limit +If this is not desirable then the size option should be used to limit its size. .Sh EXAMPLES To mount a diff --git a/share/man/man8/swapcache.8 b/share/man/man8/swapcache.8 index 7aafde437c..ac6811a4b5 100644 --- a/share/man/man8/swapcache.8 +++ b/share/man/man8/swapcache.8 @@ -146,7 +146,7 @@ The usefulness is somewhat mitigated by the maximum number of vnodes supported by the system via .Cd kern.maxfiles , because the bulk data in the cache is lost when the related -vnode is recycled. In this case it might be desireable to +vnode is recycled. In this case it might be desirable to take the plunge into running a 64-bit kernel which can support far more vnodes. 32-bit kernels have limited kernel virtual memory (KVM) and cannot reliably support more than around @@ -257,7 +257,7 @@ more in the 100-200G range certainly are. If the machine has only a 1GigE ethernet (100MB/s) there's no point configuring it for more SSD bandwidth. A single SSD of the desired size would be sufficient. .Sh INITIAL BURSTING & REPEATED BURSTING -Even though the average write bandwidth is limited it is desireable +Even though the average write bandwidth is limited it is desirable to have a large initial burst after boot to load the cache. .Cd curburst is initialized to 4GB by default and you can force rebursting diff --git a/sys/platform/pc32/i386/minidump_machdep.c b/sys/platform/pc32/i386/minidump_machdep.c index 43a5e6391f..40bfcaea95 100644 --- a/sys/platform/pc32/i386/minidump_machdep.c +++ b/sys/platform/pc32/i386/minidump_machdep.c @@ -109,7 +109,7 @@ blk_write(struct dumperinfo *di, char *ptr, vm_paddr_t pa, size_t sz) return (EINVAL); } if (ptr != NULL && pa != 0) { - kprintf("cant have both va and pa!\n"); + kprintf("can't have both va and pa!\n"); return (EINVAL); } if (pa != 0 && (((uintptr_t)ptr) % PAGE_SIZE) != 0) { diff --git a/sys/platform/pc64/x86_64/minidump_machdep.c b/sys/platform/pc64/x86_64/minidump_machdep.c index d25cafe9df..10ae3bbc09 100644 --- a/sys/platform/pc64/x86_64/minidump_machdep.c +++ b/sys/platform/pc64/x86_64/minidump_machdep.c @@ -111,7 +111,7 @@ blk_write(struct dumperinfo *di, char *ptr, vm_paddr_t pa, size_t sz) return (EINVAL); } if (ptr != NULL && pa != 0) { - kprintf("cant have both va and pa!\n"); + kprintf("can't have both va and pa!\n"); return (EINVAL); } if (pa != 0 && (((uintptr_t)ptr) % PAGE_SIZE) != 0) { diff --git a/usr.bin/evtranalyze/evtranalyze.1 b/usr.bin/evtranalyze/evtranalyze.1 index 2643121273..e1b8ef0896 100644 --- a/usr.bin/evtranalyze/evtranalyze.1 +++ b/usr.bin/evtranalyze/evtranalyze.1 @@ -65,7 +65,7 @@ displaying the stream events. The flags it accepts are: .Bl -tag -width indent-two .It Fl i Ar interval -Limits the displayed events to those occuring within the +Limits the displayed events to those occurring within the specified time interval. The interval is specified in the form [c|m]:. If