diff options
author | Jens Schweikhardt <schweikh@FreeBSD.org> | 2002-12-27 12:15:40 +0000 |
---|---|---|
committer | Jens Schweikhardt <schweikh@FreeBSD.org> | 2002-12-27 12:15:40 +0000 |
commit | 57bd0fc6e89b888516b6a64206715bef500fc2d1 (patch) | |
tree | ab5e026aafe37b18ff362bec5a3c4765fb7813f5 /share/man/man4 | |
parent | aa4d7a8a4bf3d4bfe0ad9a1af83ac6c4693eee55 (diff) |
english(4) police.
Notes
Notes:
svn path=/head/; revision=108317
Diffstat (limited to 'share/man/man4')
-rw-r--r-- | share/man/man4/ahd.4 | 4 | ||||
-rw-r--r-- | share/man/man4/crypto.4 | 2 | ||||
-rw-r--r-- | share/man/man4/geom.4 | 16 | ||||
-rw-r--r-- | share/man/man4/mac_biba.4 | 10 | ||||
-rw-r--r-- | share/man/man4/ng_bluetooth.4 | 2 | ||||
-rw-r--r-- | share/man/man4/ng_btsocket.4 | 2 | ||||
-rw-r--r-- | share/man/man4/ng_hci.4 | 6 | ||||
-rw-r--r-- | share/man/man4/psm.4 | 2 | ||||
-rw-r--r-- | share/man/man4/tcp.4 | 2 | ||||
-rw-r--r-- | share/man/man4/ti.4 | 2 |
10 files changed, 24 insertions, 24 deletions
diff --git a/share/man/man4/ahd.4 b/share/man/man4/ahd.4 index 0ae0460a232e..95c61aa8a8f1 100644 --- a/share/man/man4/ahd.4 +++ b/share/man/man4/ahd.4 @@ -88,7 +88,7 @@ is enabled. Logically OR the following bits together: .Bl -column -offset indent Value Function .Em "Value Function" -0x0001 Show miscellanious information +0x0001 Show miscellaneous information 0x0002 Show sense data 0x0004 Show Serial EEPROM contents 0x0008 Show bus termination settings @@ -118,7 +118,7 @@ configuration option. The value assigned to this option should be a bitmap of all units where target mode is desired. For example, a value of 0x25 would enable target mode on units 0, 2, and 5. -Note that target mode is only supoprted for ultra160 speeds and below. +Note that target mode is only supported for ultra160 speeds and below. .Pp Per target configuration performed in the .Tn SCSI-Select diff --git a/share/man/man4/crypto.4 b/share/man/man4/crypto.4 index f1a7ff6b9290..8382018a289d 100644 --- a/share/man/man4/crypto.4 +++ b/share/man/man4/crypto.4 @@ -69,7 +69,7 @@ Perform a crypto operation against a previously setup session. .El .Sh FEATURES Depending on hardware being present, the following symmetric and -assymetric cryptographic features are potentially available from +asymmetric cryptographic features are potentially available from .Pa /dev/crypto : .Pp .Bl -tag -width ".Dv CRYPTO_RIPEMD160_HMAC" -offset indent -compact diff --git a/share/man/man4/geom.4 b/share/man/man4/geom.4 index 03e58e180b8b..5e0368c53a2a 100644 --- a/share/man/man4/geom.4 +++ b/share/man/man4/geom.4 @@ -126,10 +126,10 @@ A geom with attached consumers has a rank one higher than the highest rank of the geoms of the providers its consumers are attached to. .El -.Sh "SPECIAL TOPOLOGICAL MANEUVRES" +.Sh "SPECIAL TOPOLOGICAL MANEUVERS" In addition to the straightforward attach, which attaches a consumer -to a provider, and dettach, which breaks the bond, a number of special -toplogical maneuvres exists to facilitate configuration and to +to a provider, and detach, which breaks the bond, a number of special +topological maneuvers exists to facilitate configuration and to improve the overall flexibility. .Pp .Em TASTING @@ -174,7 +174,7 @@ not loose quorum. When a provider is orphaned, this does not result in any immediate change in the topology, any attached consumers are still attached, any opened paths are still open, it is the responsibility of the -geoms above to close and dettach as soon as this can happen. +geoms above to close and detach as soon as this can happen. .Pp The typical scenario is that a device driver notices a disk has gone and orphans the provider for it. @@ -184,11 +184,11 @@ Providers, which are not attached, are destroyed right away. Eventually at the toplevel the geom which interfaces to the DEVFS received an orphan event on its consumer and it calls destroy_dev(9) and does an explicit close if the -device was open and then dettaches its consumer. +device was open and then detaches its consumer. The provider below is now no longer attached to and can be -destroyed, if the geom has no more providers it can dettach +destroyed, if the geom has no more providers it can detach its consumer and selfdestruct and so the carnage passes back -down the tree, until the original provider is dettached from +down the tree, until the original provider is detached from and it can be destroyed by the geom serving the device driver. .Pp While this approach seems byzantine, it does provide the maximum @@ -265,7 +265,7 @@ represented by struct bio, originate at a consumer, are scheduled on its attached provider, and when processed, returned to the consumer. It is important to realize that the struct bio which -enters throuh the provider of a particular geom does not "come +enters through the provider of a particular geom does not "come out on the other side". Even simple transformations like MBR and BSD will clone the struct bio, modify the clone, and schedule the clone on their diff --git a/share/man/man4/mac_biba.4 b/share/man/man4/mac_biba.4 index 0f1584c4b485..2c0c48201d68 100644 --- a/share/man/man4/mac_biba.4 +++ b/share/man/man4/mac_biba.4 @@ -1,12 +1,12 @@ .\" Copyright (c) 2002 Networks Associates Technology, Inc. .\" All rights reserved. -.\" +.\" .\" This software was developed for the FreeBSD Project by Chris .\" Costello at Safeport Network Services and NAI Labs, the Security .\" Research Division of Network Associates, Inc. under DARPA/SPAWAR .\" contract N66001-01-C-8035 ("CBOSS"), as part of the DARPA CHATS .\" research program. -.\" +.\" .\" Redistribution and use in source and binary forms, with or without .\" modification, are permitted provided that the following conditions .\" are met: @@ -15,7 +15,7 @@ .\" 2. Redistributions in binary form must reproduce the above copyright .\" notice, this list of conditions and the following disclaimer in the .\" documentation and/or other materials provided with the distribution. -.\" +.\" .\" THIS SOFTWARE IS PROVIDED BY THE AUTHORS AND CONTRIBUTORS ``AS IS'' AND .\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE .\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE @@ -27,7 +27,7 @@ .\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY .\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF .\" SUCH DAMAGE. -.\" +.\" .\" $FreeBSD$ .Dd NOVEMBER 18, 2002 .Os @@ -171,7 +171,7 @@ The Biba integrity model is also similar to with the exception that the dominance operator and access rules are reversed, preventing the downward flow of information rather than the upward flow of information. -Multi-Level Security (MLS) protects the confentiality, rather than the +Multi-Level Security (MLS) protects the confidentiality, rather than the integrity, of subjects and objects. .Sh SEE ALSO .Xr lomac 4 , diff --git a/share/man/man4/ng_bluetooth.4 b/share/man/man4/ng_bluetooth.4 index b5a7d62783a7..a8591d0854c9 100644 --- a/share/man/man4/ng_bluetooth.4 +++ b/share/man/man4/ng_bluetooth.4 @@ -59,7 +59,7 @@ A read-write integer variable that controls the HCI connection timeout, i.e.\& how long the HCI layer will wait for the .Dv Connection_Complete event. -Normaly this should not be required as Bluetooth devices have +Normally this should not be required as Bluetooth devices have connection timeout of their own and will send event back. This timeout is required to ensure that no connection will stall in case when the HCI diff --git a/share/man/man4/ng_btsocket.4 b/share/man/man4/ng_btsocket.4 index 7df217f8fecf..564b50a879d1 100644 --- a/share/man/man4/ng_btsocket.4 +++ b/share/man/man4/ng_btsocket.4 @@ -242,7 +242,7 @@ Not implemented. .It Dv SO_L2CAP_FLUSH Get (set) value of the flush timeout. .Bf -emphasis -Not implemeted. +Not implemented. .Ef .El .Sh HOOKS diff --git a/share/man/man4/ng_hci.4 b/share/man/man4/ng_hci.4 index 9f9cbae2d7a6..122013de2998 100644 --- a/share/man/man4/ng_hci.4 +++ b/share/man/man4/ng_hci.4 @@ -207,7 +207,7 @@ SCO data packets that the Host Controller can have waiting for transmission in its buffers. .El .Pp -As soon as HCI initialization has been successfuly performed, HCI control +As soon as HCI initialization has been successfully performed, HCI control application must turn on .Dq inited bit for the node. @@ -271,8 +271,8 @@ structure. .It Dv raw Raw hook. Every HCI frame (including HCI command frame) that goes in -or out will be delivired to the hook. -Usually Bluetooth raw HCI sockets layer is connected to the hook. +or out will be delivered to the hook. +Usually the Bluetooth raw HCI socket layer is connected to the hook. Single HCI frame contained in single .Vt mbuf structure. diff --git a/share/man/man4/psm.4 b/share/man/man4/psm.4 index c882b9f47a7c..2248f3efc94a 100644 --- a/share/man/man4/psm.4 +++ b/share/man/man4/psm.4 @@ -766,7 +766,7 @@ At debug level 2, much more detailed information is logged. .Sh CAVEATS Many pad devices behave as if the first (left) button were pressed if the user `taps' the surface of the pad. -In contrast, some pad products, e.g. some verions of ALPS GlidePoint +In contrast, some pad products, e.g. some versions of ALPS GlidePoint and Interlink VersaPad, treat the tapping action as fourth button events. .Pp diff --git a/share/man/man4/tcp.4 b/share/man/man4/tcp.4 index ef7d132b8e74..77ea455c8a71 100644 --- a/share/man/man4/tcp.4 +++ b/share/man/man4/tcp.4 @@ -303,7 +303,7 @@ recycling for a few minutes. .It tcp.inet.tcp.rexmit_{min,slop} Adjust the retransmit timer calculation for TCP. The slop is typically added to the raw calculation to take into account -occassional variances that the SRTT (smoothed round trip time) +occasional variances that the SRTT (smoothed round trip time) is unable to accomodate, while the minimum specifies an absolute minimum. While a number of TCP RFCs suggest a 1 second minimum these RFCs tend to focus on streaming behavior diff --git a/share/man/man4/ti.4 b/share/man/man4/ti.4 index 21c481aa978d..dc50eed5b480 100644 --- a/share/man/man4/ti.4 +++ b/share/man/man4/ti.4 @@ -225,7 +225,7 @@ Dump the trace buffer from the card. The argument is .Vt "struct ti_trace_buf" . .It Dv ALT_ATTACH This ioctl is used for compatibility with Alteon's Solaris driver. They -apparantly only have one character interface for debugging, so they have +apparently only have one character interface for debugging, so they have to tell it which Tigon instance they want to debug. This ioctl is a noop for .Fx . |