diff options
Diffstat (limited to 'share')
60 files changed, 118 insertions, 118 deletions
diff --git a/share/man/man3/pthread.3 b/share/man/man3/pthread.3 index faf7ec2..076aefe 100644 --- a/share/man/man3/pthread.3 +++ b/share/man/man3/pthread.3 @@ -299,7 +299,7 @@ Lock a mutex and block until it becomes available or until the timeout expires. .Ft int .Fn pthread_mutex_trylock "pthread_mutex_t *mutex" .Xc -Try to lock a mutex, but don't block if the mutex is locked by another thread, +Try to lock a mutex, but do not block if the mutex is locked by another thread, including the current thread. .It Xo .Ft int diff --git a/share/man/man3/pthread_testcancel.3 b/share/man/man3/pthread_testcancel.3 index 4bbd0cc..5ceba4c 100644 --- a/share/man/man3/pthread_testcancel.3 +++ b/share/man/man3/pthread_testcancel.3 @@ -156,7 +156,7 @@ always be restored to its value on entry to the object. .Pp This follows from a modularity argument: if the client of an object (or the client of an object that uses that object) has disabled cancelability, it is -because the client doesn't want to have to worry about how to clean up if the +because the client does not want to have to worry about how to clean up if the thread is canceled while executing some sequence of actions. If an object is called in such a state and it enables cancelability and a cancellation diff --git a/share/man/man3/sysexits.3 b/share/man/man3/sysexits.3 index 044d61e..d8c2ded 100644 --- a/share/man/man3/sysexits.3 +++ b/share/man/man3/sysexits.3 @@ -80,7 +80,7 @@ A service is unavailable. This can occur if a support program or file does not exist. This can also be used as a catchall message when -something you wanted to do doesn't work, but you don't know why. +something you wanted to do does not work, but you do not know why. .It Sy EX_SOFTWARE Pq 70 An internal software error has been detected. This should be limited diff --git a/share/man/man4/awi.4 b/share/man/man4/awi.4 index 3e5036b..13a0012 100644 --- a/share/man/man4/awi.4 +++ b/share/man/man4/awi.4 @@ -43,7 +43,7 @@ driver also supports a variant of adhoc mode out of spec for DS radio cards, which makes it possible to communicate with adhoc mode of .Xr wi 8 driver. -The NWID doesn't affect in this mode. +The NWID does not affect in this mode. .Pp For more information on configuring this device, see .Xr ifconfig 8 . diff --git a/share/man/man4/bpf.4 b/share/man/man4/bpf.4 index 58eb6be..d9cb0ce 100644 --- a/share/man/man4/bpf.4 +++ b/share/man/man4/bpf.4 @@ -214,7 +214,7 @@ and .It Li bs_drop the number of packets which were accepted by the filter but dropped by the kernel because of buffer overflows -(i.e., the application's reads aren't keeping up with the packet traffic). +(i.e., the application's reads are not keeping up with the packet traffic). .El .It Dv BIOCIMMEDIATE .Pq Li u_int @@ -349,7 +349,7 @@ header will be word aligned. Suitable precautions must be taken when accessing the link layer protocol fields on alignment restricted machines. -(This isn't a problem on an Ethernet, since +(This is not a problem on an Ethernet, since the type field is a short falling on an even offset, and the addresses are probably accessed in a bytewise fashion). .Pp @@ -586,7 +586,7 @@ BPF_RET+BPF_A accept A bytes BPF_RET+BPF_K accept k bytes .Ed .It Dv BPF_MISC -The miscellaneous category was created for anything that doesn't +The miscellaneous category was created for anything that does not fit into the above classes, and for any new instructions that might need to be added. Currently, these are the register transfer instructions diff --git a/share/man/man4/cy.4 b/share/man/man4/cy.4 index 3cd45df..0797473 100644 --- a/share/man/man4/cy.4 +++ b/share/man/man4/cy.4 @@ -171,11 +171,11 @@ In particular, the initial states for non (POSIX) standard flags should be set to suit the devices attached and may need to be locked to prevent buggy programs from changing them. E.g., CRTSCTS should be locked on for devices that support -RTS/CTS handshaking at all times and off for devices that don't +RTS/CTS handshaking at all times and off for devices that do not support it at all. CLOCAL should be locked on for devices -that don't support carrier. -HUPCL may be locked off if you don't +that do not support carrier. +HUPCL may be locked off if you do not want to hang up for some reason. In general, very bad things happen if something is locked to the wrong state, and things should not diff --git a/share/man/man4/da.4 b/share/man/man4/da.4 index 4a6068a..b3d3822 100644 --- a/share/man/man4/da.4 +++ b/share/man/man4/da.4 @@ -236,9 +236,9 @@ The default is 6 bytes. The .Nm driver issues a CAM Path Inquiry CCB at probe time to determine whether the -protocol the device in question speaks (e.g.\& ATAPI) typically doesn't allow +protocol the device in question speaks (e.g.\& ATAPI) typically does not allow 6 byte commands. -If it doesn't, the +If it does not, the .Nm driver will default to using at least 10 byte CDBs. If a 6 byte READ or WRITE fails with an ILLEGAL REQUEST error, the diff --git a/share/man/man4/dc.4 b/share/man/man4/dc.4 index 0e3a998..a81b735 100644 --- a/share/man/man4/dc.4 +++ b/share/man/man4/dc.4 @@ -314,7 +314,7 @@ mode when shutting down, and some PCI BIOSes fail to bring the chip out of this state before configuring it. The controller loses all of its PCI configuration in the D3 state, so if the BIOS does not set -it back to full power mode in time, it won't be able to configure it +it back to full power mode in time, it will not be able to configure it correctly. The driver tries to detect this condition and bring the adapter back to the D0 (full power) state, but this may not be diff --git a/share/man/man4/ddb.4 b/share/man/man4/ddb.4 index e53787f..17150be 100644 --- a/share/man/man4/ddb.4 +++ b/share/man/man4/ddb.4 @@ -99,7 +99,7 @@ a hexadecimal format at a prompt. Examine and write commands update `dot' to the address of the last line examined or the last location modified, and set `next' to the address of the next location to be examined or changed. -Other commands don't change `dot', and set `next' to be the same as `dot'. +Other commands do not change `dot', and set `next' to be the same as `dot'. .Pp The general command syntax is: .Cm command Ns Op Li \&/ Ns Ar modifier @@ -394,8 +394,8 @@ only if the machine dependent code supports it. Search memory for .Ar value . This command might fail in interesting -ways if it doesn't find the searched-for value. -This is because ddb doesn't always recover from touching bad memory. +ways if it does not find the searched-for value. +This is because ddb does not always recover from touching bad memory. The optional .Ar count argument limits the search. diff --git a/share/man/man4/digi.4 b/share/man/man4/digi.4 index e3324cf..e33e365 100644 --- a/share/man/man4/digi.4 +++ b/share/man/man4/digi.4 @@ -72,7 +72,7 @@ Meaning of .It 0x0001 use alternate pinout (exchange DCD and DSR lines) .It 0x0002 -don't use 8K window mode of PC/Xe +do not use 8K window mode of PC/Xe .El .Pp Device numbering: @@ -100,7 +100,7 @@ Input and output for each line may set to one of following baud rates; 50, 75, 110, 134.5, 150, 300, 600, 1200, 1800, 2400, 4800, 9600, 19200, 38400, 57600, or for newer versions of cards 115200. .Pp -The driver doesn't use any interrupts, it is +The driver does not use any interrupts, it is .Dq polling-based . This means that it uses clock interrupts instead of interrupts generated by DigiBoard cards and @@ -126,7 +126,7 @@ to change the pinout of the interface or to use new PC/Xe cards which can work with an 8K memory window in compatibility mode (with a 64K memory window). Note -that using 8K memory window doesn't mean shorter input/output buffers, it means +that using 8K memory window does not mean shorter input/output buffers, it means only that all buffers will be mapped to the same memory address and switched as needed. .Pp @@ -237,13 +237,13 @@ locked to prevent buggy programs from changing them. E.g., .Dv CRTSCTS should be locked on for devices that support -RTS/CTS handshaking at all times and off for devices that don't +RTS/CTS handshaking at all times and off for devices that do not support it at all. .Dv CLOCAL should be locked on for devices -that don't support carrier. +that do not support carrier. .Dv HUPCL -may be locked off if you don't +may be locked off if you do not want to hang up for some reason. In general, very bad things happen if something is locked to the wrong state, and things should not diff --git a/share/man/man4/divert.4 b/share/man/man4/divert.4 index 0180ef3..0898362 100644 --- a/share/man/man4/divert.4 +++ b/share/man/man4/divert.4 @@ -176,7 +176,7 @@ could be cleaner, and it's too dependent on It's questionable whether incoming fragments should be reassembled before being diverted. For example, if only some fragments of a -packet destined for another machine don't get routed through the +packet destined for another machine do not get routed through the local machine, the packet is lost. This should probably be a settable socket option in any case. diff --git a/share/man/man4/ed.4 b/share/man/man4/ed.4 index 7ef74b4..cc2e902 100644 --- a/share/man/man4/ed.4 +++ b/share/man/man4/ed.4 @@ -87,7 +87,7 @@ lossage). Some .No ( non- Ns Fx :-)) machines have terrible Ethernet performance -and simply can't cope with 1100K+ data rates. +and simply cannot cope with 1100K+ data rates. Use of this flag also provides one more packet worth of receiver buffering, and on 8bit cards, this may help reduce receiver lossage. @@ -262,7 +262,7 @@ This is most commonly caused by a BIOS extension ROM being configured in the same address space as the Ethernet card's shared memory. Either find the offending card and change its BIOS -ROM to be at an address that doesn't conflict, or change the +ROM to be at an address that does not conflict, or change the .Cd iomem option in the kernel config file so that the card's shared memory is mapped at a non-conflicting address. @@ -279,7 +279,7 @@ the card is defective. Indicates a logic problem in the driver. Should never happen. .It "ed%d: device timeout" -Indicates that an expected transmitter interrupt didn't occur. +Indicates that an expected transmitter interrupt did not occur. Usually caused by an interrupt conflict with another card on the ISA bus. This condition could also be caused if the kernel is configured for a diff --git a/share/man/man4/icmp.4 b/share/man/man4/icmp.4 index 252537f..af5c1df 100644 --- a/share/man/man4/icmp.4 +++ b/share/man/man4/icmp.4 @@ -147,7 +147,7 @@ already has one, or when trying to send a datagram with the destination address specified and the socket is already connected; .It Bq Er ENOTCONN when trying to send a datagram, but -no destination address is specified, and the socket hasn't been +no destination address is specified, and the socket has not been connected; .It Bq Er ENOBUFS when the system runs out of memory for diff --git a/share/man/man4/intpm.4 b/share/man/man4/intpm.4 index 3553844..5e015a8 100644 --- a/share/man/man4/intpm.4 +++ b/share/man/man4/intpm.4 @@ -60,4 +60,4 @@ This device requires IRQ 9 exclusively. To use this, you should enable ACPI function in BIOS configuration, or PnP mechanism assigns conflicted IRQ for PnP ISA card. -And don't use IRQ 9 for Non-PnP ISA cards. +And do not use IRQ 9 for Non-PnP ISA cards. diff --git a/share/man/man4/ip.4 b/share/man/man4/ip.4 index bbf9c17..dd86514 100644 --- a/share/man/man4/ip.4 +++ b/share/man/man4/ip.4 @@ -564,7 +564,7 @@ already has one, or when trying to send a datagram with the destination address specified and the socket is already connected; .It Bq Er ENOTCONN when trying to send a datagram, but -no destination address is specified, and the socket hasn't been +no destination address is specified, and the socket has not been connected; .It Bq Er ENOBUFS when the system runs out of memory for diff --git a/share/man/man4/ip6.4 b/share/man/man4/ip6.4 index c7a531e..174e45f 100644 --- a/share/man/man4/ip6.4 +++ b/share/man/man4/ip6.4 @@ -611,7 +611,7 @@ already has one or when trying to send a datagram with the destination address specified and the socket is already connected. .It Bq Er ENOTCONN when trying to send a datagram, but -no destination address is specified, and the socket hasn't been +no destination address is specified, and the socket has not been connected. .It Bq Er ENOBUFS when the system runs out of memory for diff --git a/share/man/man4/isp.4 b/share/man/man4/isp.4 index d3a6448..f28c1ba 100644 --- a/share/man/man4/isp.4 +++ b/share/man/man4/isp.4 @@ -185,13 +185,13 @@ driver was written by Matthew Jacob for NASA/Ames Research Center. .Sh BUGS The driver currently ignores some NVRAM settings. .Pp -The driver currently doesn't do error recovery for timed out commands +The driver currently does not do error recovery for timed out commands very gracefully. .Pp -Target mode support isn't completely debugged yet. +Target mode support is not completely debugged yet. It works reasonably well for Fibre Channel, somewhat well for Qlogic 1040 cards, but -doesn't yet work for the other cards (due to last minute unannounced +does not yet work for the other cards (due to last minute unannounced changes in firmware interfaces). .Pp Sometimes, when booting, the driver gets stuck waiting for the diff --git a/share/man/man4/man4.i386/apm.4 b/share/man/man4/man4.i386/apm.4 index e2c33e4..e5e5c6a 100644 --- a/share/man/man4/man4.i386/apm.4 +++ b/share/man/man4/man4.i386/apm.4 @@ -128,7 +128,7 @@ Many, if not most, of the implementations of APM-bios in laptops today are buggy. You may be putting your LCD-display and batteries at a risk by using this interface. -(The reason this isn't a problem for +(The reason this is not a problem for MS-Windows is that they use the real-mode interface.) If you see any weird behavior from your system with this code in use, unplug the diff --git a/share/man/man4/man4.i386/lnc.4 b/share/man/man4/man4.i386/lnc.4 index 37eed70..6f41333 100644 --- a/share/man/man4/man4.i386/lnc.4 +++ b/share/man/man4/man4.i386/lnc.4 @@ -104,7 +104,7 @@ The driver assumes the memory it allocates is within the lower 16Mb range. This is not a very valid assumption but there's nothing that can be done about it yet. -For shared memory NICs this isn't relevant. +For shared memory NICs this is not relevant. .It "lnc%d: Device timeout -- Resetting" The device has stopped responding to the network, or there is a problem with the network connection (cable). diff --git a/share/man/man4/man4.i386/mcd.4 b/share/man/man4/man4.i386/mcd.4 index 532e3a4..84b47e4 100644 --- a/share/man/man4/man4.i386/mcd.4 +++ b/share/man/man4/man4.i386/mcd.4 @@ -147,7 +147,7 @@ features of the interface board, although it has an interrupt handler for any IRQ requests that are generated. Until the DMA features are supported, the only interrupts that the board generates are those that -aren't supported by the driver anyway. +are not supported by the driver anyway. .Sh SEE ALSO .In sys/cdio.h .Sh HISTORY diff --git a/share/man/man4/man4.i386/mse.4 b/share/man/man4/man4.i386/mse.4 index c3b07c8..bd4500e 100644 --- a/share/man/man4/man4.i386/mse.4 +++ b/share/man/man4/man4.i386/mse.4 @@ -126,7 +126,7 @@ minor = (`unit' << 1) | `non-blocking' .Ed .Pp where `unit' is the device number (usually 0) and the `non-blocking' bit -is set to indicate ``don't block waiting for mouse input, +is set to indicate ``do not block waiting for mouse input, return immediately''. The `non-blocking' bit should be set for \fIXFree86\fP, therefore the minor device number usually used for \fIXFree86\fP is 1. @@ -307,7 +307,7 @@ and are modifiable by the .Dv MOUSE_SETMODE command. -Changing the other field doesn't cause error, but has no effect. +Changing the other field does not cause error, but has no effect. .Pp .It Dv MOUSE_SETMODE Ar mousemode_t *mode The command changes the current operation parameters of the mouse driver diff --git a/share/man/man4/man4.i386/ray.4 b/share/man/man4/man4.i386/ray.4 index f7e5c78..aecbfbe 100644 --- a/share/man/man4/man4.i386/ray.4 +++ b/share/man/man4/man4.i386/ray.4 @@ -381,7 +381,7 @@ memory maps correctly - it works around and then throws it all away assuming the card is an .Xr ed 4 driver...). -Note that this could be dangerous (because it doesn't interact with +Note that this could be dangerous (because it does not interact with .Xr pccardd 8 ) if you use other memory mapped cards at the same time or have SCSI cards with on-board BIOS. diff --git a/share/man/man4/man4.i386/sr.4 b/share/man/man4/man4.i386/sr.4 index 3761ece..899cce1 100644 --- a/share/man/man4/man4.i386/sr.4 +++ b/share/man/man4/man4.i386/sr.4 @@ -84,7 +84,7 @@ The specification in .Pa /boot/device.hints is optional. -If it isn't specified, the driver will +If it is not specified, the driver will assume the following: .Pp .Bl -hang -offset indent diff --git a/share/man/man4/natm.4 b/share/man/man4/natm.4 index 19dd592..a70e67f 100644 --- a/share/man/man4/natm.4 +++ b/share/man/man4/natm.4 @@ -14,7 +14,7 @@ ATM software comes with a which provides socket level access to AAL0 and AAL5 virtual circuits. To enable this protocol layer, add .Dl options NATM -to your kernel configuration file and re-make the kernel (don't forget +to your kernel configuration file and re-make the kernel (do not forget to do .Dq make clean ) . .Sh NATM API diff --git a/share/man/man4/ng_ppp.4 b/share/man/man4/ng_ppp.4 index 6882c44..26a9e22 100644 --- a/share/man/man4/ng_ppp.4 +++ b/share/man/man4/ng_ppp.4 @@ -202,7 +202,7 @@ is disabled, over the (single) PPP link. Typically when the controlling entity receives an unexpected packet on the .Dv bypass hook it responds either by dropping the frame (if it's not ready for -the protocol) or with an LCP protocol reject (if it doesn't recognize +the protocol) or with an LCP protocol reject (if it does not recognize or expect the protocol). .Sh MULTILINK OPERATION To enable multi-link PPP, the corresponding configuration flag must be set diff --git a/share/man/man4/pci.4 b/share/man/man4/pci.4 index eb3b01a..ccc6b94 100644 --- a/share/man/man4/pci.4 +++ b/share/man/man4/pci.4 @@ -131,7 +131,7 @@ A device must match all specified fields in order to be returned. The match flags are enumerated in the .Va pci_getconf_flags structure. -Hopefully the flag values are obvious enough that they don't need to +Hopefully the flag values are obvious enough that they do not need to described in detail. .El .It match_buf_len @@ -315,11 +315,11 @@ Kenneth Merry, and first appeared in .Sh AUTHORS .An Kenneth Merry Aq ken@FreeBSD.org .Sh BUGS -It isn't possible for users to specify an accurate offset into the device +It is not possible for users to specify an accurate offset into the device list without calling the .Dv PCIOCGETCONF at least once, since they have no way of knowing the current generation number otherwise. -This probably isn't a serious problem, though, since +This probably is not a serious problem, though, since users can easily narrow their search by specifying a pattern or patterns for the kernel to match against. diff --git a/share/man/man4/ppbus.4 b/share/man/man4/ppbus.4 index 73a85e3..6e18ac3 100644 --- a/share/man/man4/ppbus.4 +++ b/share/man/man4/ppbus.4 @@ -248,7 +248,7 @@ characteristics of the standard. IEEE1284 interacts with the ppbus system as little as possible. That means you still have to request the ppbus when you want to access it, the negotiate -function doesn't do it for you. +function does not do it for you. And of course, release it later. .Sh ARCHITECTURE .Ss adapter, ppbus and device layers diff --git a/share/man/man4/psm.4 b/share/man/man4/psm.4 index bfeb594..3e9c419 100644 --- a/share/man/man4/psm.4 +++ b/share/man/man4/psm.4 @@ -87,7 +87,7 @@ The PS/2 style pointing device typically supports 10, 20, 40, 60, 80, 100 and 200 reports per second. 60 or 100 appears to be the default value for many devices. Note that when there is no movement and no button has changed its state, -the device won't send anything to the host system. +the device will not send anything to the host system. The report rate can be changed via an ioctl call. .Ss Operation Levels The @@ -186,7 +186,7 @@ minor = (`unit' << 1) | `non-blocking' .Ed .Pp where `unit' is the device number (usually 0) and the `non-blocking' bit -is set to indicate ``don't block waiting for mouse input, +is set to indicate ``do not block waiting for mouse input, return immediately''. The `non-blocking' bit should be set for \fIXFree86\fP, therefore the minor device number usually used for \fIXFree86\fP is 1. @@ -293,14 +293,14 @@ driver will not try to identify the model of the pointing device and will not carry out model-specific initialization. The device should always act like a standard PS/2 mouse without such initialization. -Extra features, such as wheels and additional buttons, won't be +Extra features, such as wheels and additional buttons, will not be recognized by the .Nm driver. .It bit 10 NORESET When this flag is set, the .Nm -driver won't reset the pointing device when initializing the device. +driver will not reset the pointing device when initializing the device. If the .Fx kernel diff --git a/share/man/man4/rl.4 b/share/man/man4/rl.4 index a5047a9..97ef935 100644 --- a/share/man/man4/rl.4 +++ b/share/man/man4/rl.4 @@ -209,7 +209,7 @@ mode when shutting down, and some PCI BIOSes fail to bring the chip out of this state before configuring it. The controller loses all of its PCI configuration in the D3 state, so if the BIOS does not set -it back to full power mode in time, it won't be able to configure it +it back to full power mode in time, it will not be able to configure it correctly. The driver tries to detect this condition and bring the adapter back to the D0 (full power) state, but this may not be diff --git a/share/man/man4/rp.4 b/share/man/man4/rp.4 index a9d1b60..dbdf77b 100644 --- a/share/man/man4/rp.4 +++ b/share/man/man4/rp.4 @@ -191,5 +191,5 @@ or in the tty layer. .\" (Although my bet is that it's in the higher-level tty layer; .\" given the bugs I found while writing this driver, it's clear -.\" the BSD software flow control code hasn't been tested very much +.\" the BSD software flow control code has not been tested very much .\" at all! -- TYT) diff --git a/share/man/man4/sa.4 b/share/man/man4/sa.4 index e1fc4dc..0a6da7c 100644 --- a/share/man/man4/sa.4 +++ b/share/man/man4/sa.4 @@ -169,7 +169,7 @@ If a rewind is requested after a write, then the driver assumes that the last file on the tape has been written, and ensures that there are two file marks written to the tape. The exception to -this is that there seems to be a standard (which we follow, but don't +this is that there seems to be a standard (which we follow, but do not understand why) that certain types of tape do not actually write two file marks to tape, but when read, report a `phantom' file mark when the last file is read. @@ -235,7 +235,7 @@ Additionally, certain tapes (QIC tapes mostly) that were written under .Fx 2.X -aren't automatically read correctly with this driver: you may need to +are not automatically read correctly with this driver: you may need to explicitly set variable block mode or set to the blocksize that works best for your device in order to read tapes written under .Fx diff --git a/share/man/man4/scsi.4 b/share/man/man4/scsi.4 index 743a036..0aaafb5 100644 --- a/share/man/man4/scsi.4 +++ b/share/man/man4/scsi.4 @@ -75,7 +75,7 @@ subsystem: .Bl -tag -width SCSI_NO_SENSE_STRINGS .It Dv CAMDEBUG This option enables the CAM debugging printf code. -This won't actually +This will not actually cause any debugging information to be printed out when included by itself. Enabling printouts requires additional configuration. See below for details. @@ -105,7 +105,7 @@ In most cases, though, this should be enabled, since it speeds the interpretation of .Tn SCSI error messages. -Don't let the "kernel bloat" zealots get to you -- leave +Do not let the "kernel bloat" zealots get to you -- leave the sense descriptions in your kernel! .It Dv SCSI_NO_OP_STRINGS This disables text descriptions of each @@ -113,7 +113,7 @@ This disables text descriptions of each opcode. This option, like the sense string option above, is primarily useful for environments like a boot floppy where kernel size is critical. -Enabling this option for normal use isn't recommended, since it slows +Enabling this option for normal use is not recommended, since it slows debugging of .Tn SCSI problems. @@ -137,7 +137,7 @@ Newer disks may need as little as 100ms, while old, slow devices may need much longer. If the .Dv SCSI_DELAY -isn't specified, it defaults to 2 seconds. +is not specified, it defaults to 2 seconds. The minimum allowable value for .Dv SCSI_DELAY is "100", or 100ms. @@ -268,10 +268,10 @@ Some of these flags, most notably and .Dv CAM_DEBUG_SUBTRACE will produce kernel printfs in EXTREME numbers, -and because of that, they aren't especially useful. -There aren't many things logged at the +and because of that, they are not especially useful. +There are not many things logged at the .Dv CAM_DEBUG_INFO -level, so it isn't especially useful. +level, so it is not especially useful. The most useful debugging flag is the .Dv CAM_DEBUG_CDB flag. diff --git a/share/man/man4/sio.4 b/share/man/man4/sio.4 index b7f4f25..d9f4f91 100644 --- a/share/man/man4/sio.4 +++ b/share/man/man4/sio.4 @@ -229,7 +229,7 @@ port. The driver supports controller based PCI modems. The 3Com FaxModem PCI and the Advantec 56k Voice Messaging PCI FaxModem are the only cards supported. -WinModems, softmodems, hfc modems and any other modems that aren't +WinModems, softmodems, hfc modems and any other modems that are not controller based are not supported. .Pp The @@ -330,10 +330,10 @@ In particular, the initial states for non (POSIX) standard flags should be set to suit the devices attached and may need to be locked to prevent buggy programs from changing them. E.g., CRTSCTS should be locked on for devices that support -RTS/CTS handshaking at all times and off for devices that don't +RTS/CTS handshaking at all times and off for devices that do not support it at all. -CLOCAL should be locked on for devices that don't support carrier. -HUPCL may be locked off if you don't +CLOCAL should be locked on for devices that do not support carrier. +HUPCL may be locked off if you do not want to hang up for some reason. In general, very bad things happen if something is locked to the wrong state, and things should not diff --git a/share/man/man4/sppp.4 b/share/man/man4/sppp.4 index 32acec1..22b238a 100644 --- a/share/man/man4/sppp.4 +++ b/share/man/man4/sppp.4 @@ -78,7 +78,7 @@ signals an event (rise of .Dq carrier ) . This can be used by lower layers to support -a dialin connection where the physical layer isn't available +a dialin connection where the physical layer is not available immediately at startup, but only after some external event arrives. Receipt of a .Em Down @@ -134,7 +134,7 @@ wrong assumptions. In a similar spirit the remote address can be set to the magical value .Li 0.0.0. Ns Em * -which means that we don't care what address the remote +which means that we do not care what address the remote side will use, as long as it is not 0.0.0.0. This is useful if your ISP has several dial-in servers. @@ -227,7 +227,7 @@ for authentication and link quality reporting. .Pp Negotiation loop avoidance is not fully implemented. If the negotiation -doesn't converge, this can cause an endless loop. +does not converge, this can cause an endless loop. .Pp The various parameters that should be adjustable per RFC 1661 are currently hard-coded into the kernel, and should be made accessible diff --git a/share/man/man4/ste.4 b/share/man/man4/ste.4 index 200c1f3..9a93610 100644 --- a/share/man/man4/ste.4 +++ b/share/man/man4/ste.4 @@ -136,7 +136,7 @@ mode when shutting down, and some PCI BIOSes fail to bring the chip out of this state before configuring it. The controller loses all of its PCI configuration in the D3 state, so if the BIOS does not set -it back to full power mode in time, it won't be able to configure it +it back to full power mode in time, it will not be able to configure it correctly. The driver tries to detect this condition and bring the adapter back to the D0 (full power) state, but this may not be diff --git a/share/man/man4/sysmouse.4 b/share/man/man4/sysmouse.4 index db5b724..a1b2459 100644 --- a/share/man/man4/sysmouse.4 +++ b/share/man/man4/sysmouse.4 @@ -57,7 +57,7 @@ mouse data from the device via .Xr read 2 . Make sure that .Xr moused 8 -is running, otherwise the user process won't see any data coming from +is running, otherwise the user process will not see any data coming from the mouse. .Pp .Ss Operation Levels diff --git a/share/man/man4/tap.4 b/share/man/man4/tap.4 index c05bff6..6932b79 100644 --- a/share/man/man4/tap.4 +++ b/share/man/man4/tap.4 @@ -139,7 +139,7 @@ this stores the internal debugging variable's value into it. .It Dv FIONBIO Turn non-blocking I/O for reads off or on, according as the argument .Va int Ns 's -value is or isn't zero +value is or is not zero (Writes are always nonblocking). .It Dv FIOASYNC Turn asynchronous I/O for reads @@ -148,7 +148,7 @@ Turn asynchronous I/O for reads when data is available to be read) off or on, according as the argument .Va int Ns 's -value is or isn't zero. +value is or is not zero. .It Dv FIONREAD If any frames are queued to be read, store the size of the first one into the argument .Va int ; diff --git a/share/man/man4/termios.4 b/share/man/man4/termios.4 index 1a9d846..f6cf216 100644 --- a/share/man/man4/termios.4 +++ b/share/man/man4/termios.4 @@ -119,7 +119,7 @@ sets the process group of the terminal back to its own process group (it puts itself into the foreground). If the job is to be started in the background (as denoted by the shell operator "&"), -it never changes the process group of the terminal and doesn't +it never changes the process group of the terminal and does not wait for the job to complete (that is, it immediately attempts to read the next command). If the job is started in the foreground, the user may @@ -136,7 +136,7 @@ and for placing stopped or background jobs into the foreground. An orphaned process group is a process group that has no process whose parent is in a different process group, yet is in the same session. -Conceptually it means a process group that doesn't have +Conceptually it means a process group that does not have a parent that could do anything if it were to be stopped. For example, the initial login shell is typically in an orphaned process group. diff --git a/share/man/man4/tty.4 b/share/man/man4/tty.4 index cade15a..393b420 100644 --- a/share/man/man4/tty.4 +++ b/share/man/man4/tty.4 @@ -258,14 +258,14 @@ Pretend as if the terminal received the character pointed to by .Fa cp . .It Dv TIOCNOTTY Fa void This call is obsolete but left for compatibility. -In the past, when a process that didn't have a controlling terminal (see +In the past, when a process that did not have a controlling terminal (see .Em The Controlling Terminal in .Xr termios 4 ) first opened a terminal device, it acquired that terminal as its controlling terminal. For some programs this was a hazard as they -didn't want a controlling terminal in the first place, and this +did not want a controlling terminal in the first place, and this provided a mechanism to disassociate the controlling terminal from the calling process. It diff --git a/share/man/man4/tun.4 b/share/man/man4/tun.4 index 955d3dd..4754e2c 100644 --- a/share/man/man4/tun.4 +++ b/share/man/man4/tun.4 @@ -229,7 +229,7 @@ mode, and zero otherwise. .It Dv FIONBIO Turn non-blocking I/O for reads off or on, according as the argument .Vt int Ns 's -value is or isn't zero. +value is or is not zero. (Writes are always non-blocking.) .It Dv FIOASYNC Turn asynchronous I/O for reads @@ -238,7 +238,7 @@ Turn asynchronous I/O for reads when data is available to be read) off or on, according as the argument .Vt int Ns 's -value is or isn't zero. +value is or is not zero. .It Dv FIONREAD If any packets are queued to be read, store the size of the first one into the argument diff --git a/share/man/man4/udp.4 b/share/man/man4/udp.4 index 4ae65ed..03d6db2 100644 --- a/share/man/man4/udp.4 +++ b/share/man/man4/udp.4 @@ -112,7 +112,7 @@ already has one, or when trying to send a datagram with the destination address specified and the socket is already connected; .It Bq Er ENOTCONN when trying to send a datagram, but -no destination address is specified, and the socket hasn't been +no destination address is specified, and the socket has not been connected; .It Bq Er ENOBUFS when the system runs out of memory for diff --git a/share/man/man4/vr.4 b/share/man/man4/vr.4 index 55b06cd..43a1fc3 100644 --- a/share/man/man4/vr.4 +++ b/share/man/man4/vr.4 @@ -144,7 +144,7 @@ mode when shutting down, and some PCI BIOSes fail to bring the chip out of this state before configuring it. The controller loses all of its PCI configuration in the D3 state, so if the BIOS does not set -it back to full power mode in time, it won't be able to configure it +it back to full power mode in time, it will not be able to configure it correctly. The driver tries to detect this condition and bring the adapter back to the D0 (full power) state, but this may not be @@ -188,7 +188,7 @@ driver always copies transmit mbuf chains into longword-aligned buffers prior to transmission in order to pacify the Rhine chips. If buffers are not aligned correctly, the chip will round the supplied buffer address and begin DMAing from the wrong location. -This buffer copying impairs transmit performance on slower systems but can't +This buffer copying impairs transmit performance on slower systems but cannot be avoided. On faster machines (e.g.\& a Pentium II), the performance impact is much less noticeable. diff --git a/share/man/man4/wb.4 b/share/man/man4/wb.4 index 84e60cc..d34b910 100644 --- a/share/man/man4/wb.4 +++ b/share/man/man4/wb.4 @@ -139,7 +139,7 @@ mode when shutting down, and some PCI BIOSes fail to bring the chip out of this state before configuring it. The controller loses all of its PCI configuration in the D3 state, so if the BIOS does not set -it back to full power mode in time, it won't be able to configure it +it back to full power mode in time, it will not be able to configure it correctly. The driver tries to detect this condition and bring the adapter back to the D0 (full power) state, but this may not be diff --git a/share/man/man4/worm.4 b/share/man/man4/worm.4 index 72e74b8..67cff79 100644 --- a/share/man/man4/worm.4 +++ b/share/man/man4/worm.4 @@ -60,9 +60,9 @@ by a CAM-compliant layer. The new .Tn SCSI -layer doesn't include a +layer does not include a .Nm -driver, and isn't likely to include one in the future. +driver, and is not likely to include one in the future. Future in-kernel support for CD-R/CD-RW/DVD drives will likely be implemented through the .Xr cd 4 diff --git a/share/man/man4/xl.4 b/share/man/man4/xl.4 index 1604012..ec8c858 100644 --- a/share/man/man4/xl.4 +++ b/share/man/man4/xl.4 @@ -205,7 +205,7 @@ mode when shutting down, and some PCI BIOSes fail to bring the chip out of this state before configuring it. The 3c905B loses all of its PCI configuration in the D3 state, so if the BIOS does not set -it back to full power mode in time, it won't be able to configure it +it back to full power mode in time, it will not be able to configure it correctly. The driver tries to detect this condition and bring the adapter back to the D0 (full power) state, but this may not be diff --git a/share/man/man5/fs.5 b/share/man/man5/fs.5 index 368f11c..3754d45 100644 --- a/share/man/man5/fs.5 +++ b/share/man/man5/fs.5 @@ -242,7 +242,7 @@ The file system records space availability at the fragment level; to determine block availability, aligned fragments are examined. .Pp The root inode is the root of the file system. -Inode 0 can't be used for normal purposes and +Inode 0 cannot be used for normal purposes and historically bad blocks were linked to inode 1, thus the root inode is 2 (inode 1 is no longer used for this purpose, however numerous dump tapes make this diff --git a/share/man/man5/nsswitch.conf.5 b/share/man/man5/nsswitch.conf.5 index 31987d0..91c8a6c 100644 --- a/share/man/man5/nsswitch.conf.5 +++ b/share/man/man5/nsswitch.conf.5 @@ -210,7 +210,7 @@ and Historically, many of the databases had enumeration functions, often of the form .Fn getXXXent . -These made sense when the databases were in local files, but don't make +These made sense when the databases were in local files, but do not make sense or have lesser relevance when there are possibly multiple sources, each of an unknown size. The interfaces are still provided for compatibility, but the source @@ -224,7 +224,7 @@ source must appear alone for a given database. .Ss Default source lists If, for any reason, .Nm -doesn't exist, or it has missing or corrupt entries, +does not exist, or it has missing or corrupt entries, .Xr nsdispatch 3 will default to an entry of .Dq files @@ -271,7 +271,7 @@ nis [notfound=return] files .Pp The criteria .Dq [notfound=return] -sets a policy of "if the user is notfound in nis, don't try files." +sets a policy of "if the user is notfound in nis, do not try files." This treats nis as the authoritative source of information, except when the server is down. .Sh SEE ALSO diff --git a/share/man/man7/firewall.7 b/share/man/man7/firewall.7 index 1bb5cb5..8920fca 100644 --- a/share/man/man7/firewall.7 +++ b/share/man/man7/firewall.7 @@ -150,7 +150,7 @@ Internet-routed IP addresses. In our example, 192.100.5.x represents the Internet-routed IP block while 10.x.x.x represents the internal networks. -While it isn't relevant to the example, 10.0.1.x is +While it is not relevant to the example, 10.0.1.x is assigned as the internal address block for the LAN on fxp0, 10.0.2.x for the LAN on fxp1, and 10.0.3.x for the LAN on fxp2. .Pp @@ -284,7 +284,7 @@ add 01001 allow all from any to any out via fxp2 # internal networks. Packets received via fxp1 MUST come from # 10.0.1.x. Packets received via fxp2 MUST come from 10.0.2.x. # Packets received via fxp0 cannot come from the LAN1 or LAN2 -# blocks. We can't protect 10.0.0.x here, the Internet router +# blocks. We cannot protect 10.0.0.x here, the Internet router # must do that for us. # add 01500 deny all from not 10.0.1.0/24 in via fxp1 @@ -315,7 +315,7 @@ add 01501 deny all from 10.0.2.0/24 in via fxp0 # access to specific services running on the firewall itself. # In this case we assume LAN1 needs access to filesharing running # on the firewall. If using a less restrictive firewall -# (allowing rule 01010), you don't need these rules. +# (allowing rule 01010), you do not need these rules. # add 01012 allow tcp from 10.0.1.0/8 to 10.0.1.1 139 add 01012 allow udp from 10.0.1.0/8 to 10.0.1.1 137,138 @@ -376,7 +376,7 @@ add 03000 allow tcp from any to any auth,pop3,ftp,ftp-data add 04000 allow icmp from any to any icmptypes 0,3,8,11,12,13,14 # log any remaining fragments that get through. Might be useful, -# otherwise don't bother. Have a final deny rule as a safety to +# otherwise do not bother. Have a final deny rule as a safety to # guarantee that your firewall is inclusive no matter how the kernel # is configured. # @@ -385,7 +385,7 @@ add 06000 deny all from any to any .Ed .Sh PORT BINDING INTERNAL AND EXTERNAL SERVICES We've mentioned multi-homing hosts and binding services to internal or -external addresses but we haven't really explained it. +external addresses but we have not really explained it. When you have a host with multiple IP addresses assigned to it, you can bind services run on that host to specific IPs or interfaces rather than all IPs. diff --git a/share/man/man7/release.7 b/share/man/man7/release.7 index ec7f7e2..231bb9b 100644 --- a/share/man/man7/release.7 +++ b/share/man/man7/release.7 @@ -194,7 +194,7 @@ The directory to be used as the environment for the entire release build. .\" XXX: I recommend against hardcoding specific numbers like "2.3" here; .\" XXX: perhaps it should be replaced with something to the effect of -.\" XXX: "we don't know how much space you'll need, but make sure you have +.\" XXX: "we do not know how much space you'll need, but make sure you have .\" XXX: at least 3 GB to be safe" (I know i'm still hardcoding a number, .\" XXX: but at least it looks less like a decree and more like an estimate. This file system should have at least 3.2 gigabytes of free space on the diff --git a/share/man/man9/VFS.9 b/share/man/man9/VFS.9 index 457c794..a9dae27 100644 --- a/share/man/man9/VFS.9 +++ b/share/man/man9/VFS.9 @@ -37,7 +37,7 @@ .Sh DESCRIPTION Calls used to set or query file systems for settings or information. .Pp -File systems that don't implement a VFS operation should use the appropriate +File systems that do not implement a VFS operation should use the appropriate .Fa vfs_std function from .Pa src/sys/kern/vfs_default.c diff --git a/share/man/man9/VOP_LOCK.9 b/share/man/man9/VOP_LOCK.9 index f5068a6..5b7472d 100644 --- a/share/man/man9/VOP_LOCK.9 +++ b/share/man/man9/VOP_LOCK.9 @@ -107,7 +107,7 @@ will unlock the simple lock after getting the lock). .It Dv LK_RETRY Retry until locked. .It Dv LK_NOOBJ -Don't create object. +Do not create object. .El .It Fa td Thread context to use for the locks. diff --git a/share/man/man9/bus_release_resource.9 b/share/man/man9/bus_release_resource.9 index e4322af..85e777b 100644 --- a/share/man/man9/bus_release_resource.9 +++ b/share/man/man9/bus_release_resource.9 @@ -83,7 +83,7 @@ is returned, if the device has no parent, .Dv 0 otherwise. -The kernel will panic, if it can't release the resource. +The kernel will panic, if it cannot release the resource. .Sh EXAMPLES .Bd -literal /* deactivate IRQ */ diff --git a/share/man/man9/cd.9 b/share/man/man9/cd.9 index 96a4504..59f796d 100644 --- a/share/man/man9/cd.9 +++ b/share/man/man9/cd.9 @@ -100,7 +100,7 @@ byte version of the command instead. The only reason you would need a quirk is if your drive uses a protocol (e.g., .Tn SCSI ) -that typically doesn't have a problem with 6 byte commands. +that typically does not have a problem with 6 byte commands. .El .Sh FILES .Bl -tag -width /sys/cam/scsi/scsi_cd.c -compact diff --git a/share/man/man9/devstat.9 b/share/man/man9/devstat.9 index ceaec6e..45e17b7 100644 --- a/share/man/man9/devstat.9 +++ b/share/man/man9/devstat.9 @@ -392,7 +392,7 @@ The transaction had a head of queue tag. .It DEVSTAT_TAG_ORDERED The transaction had an ordered tag. .It DEVSTAT_TAG_NONE -The device doesn't support tags. +The device does not support tags. .El .Pp The tag type values correspond to the lower four bits of the diff --git a/share/man/man9/intro.9 b/share/man/man9/intro.9 index 0d927e9..0e0fe81 100644 --- a/share/man/man9/intro.9 +++ b/share/man/man9/intro.9 @@ -49,19 +49,19 @@ If your code compiles cleanly with .Nm cc .Ar -Wall we would feel happy about it. -It is important to understand that this isn't a question of just shutting up +It is important to understand that this is not a question of just shutting up .Nm cc , it is a question about avoiding the things it complains about. -To put it bluntly, don't hide the problem by casting and other +To put it bluntly, do not hide the problem by casting and other obfuscating practices, solve the problem. .Sh INDENTATION AND STYLE Believe it or not, there actually exists a guide for indentation and style. -It isn't generally applied though. +It is not generally applied though. .Pp We would appreciate if people would pay attention to it, and at least not violate it blatantly. .Pp -We don't mind it too badly if you have your own style, but please make +We do not mind it too badly if you have your own style, but please make sure we can read it too. .Pp Please take time to read @@ -92,7 +92,7 @@ There are several reasons for this policy, the main one is that the kernel is one monolithic name-space, and pollution is not a good idea here either. .Pp -For device drivers and other modules that don't add new internal interfaces +For device drivers and other modules that do not add new internal interfaces to the kernel, the entire source should be in one file if possible. That way all symbols can be made static. .Pp diff --git a/share/man/man9/mbuf.9 b/share/man/man9/mbuf.9 index 964a380..75a9762 100644 --- a/share/man/man9/mbuf.9 +++ b/share/man/man9/mbuf.9 @@ -408,7 +408,7 @@ to .Fa mbuf . If the macro fails, the .Dv M_EXT -flag won't be set in +flag will not be set in .Fa mbuf . .It Fn M_ALIGN mbuf len Set the pointer @@ -602,7 +602,7 @@ handle .Dv M_PKTHDR properly. .Sy Note : -It doesn't allocate any +It does not allocate any .Vt mbuf clusters , so .Fa len @@ -632,7 +632,7 @@ on failure .Vt mbuf chain is freed in this case). .Sy Note : -It doesn't allocate any +It does not allocate any .Vt mbuf clusters , so .Fa len @@ -704,7 +704,7 @@ extending the .Vt mbuf chain if necessary. .Sy Note : -It doesn't allocate any +It does not allocate any .Vt mbuf clusters , just adds .Vt mbufs diff --git a/share/man/man9/mutex.9 b/share/man/man9/mutex.9 index c4c11cb..b4596cf 100644 --- a/share/man/man9/mutex.9 +++ b/share/man/man9/mutex.9 @@ -117,7 +117,7 @@ As a machine dependent optimization they may spin for some amount of time before context switching. It is important to remember that since a process may be preempted at any time, the possible context switch introduced by acquiring a mutex is guaranteed -to not break anything that isn't already broken. +to not break anything that is not already broken. .Pp Mutexes which do not context switch are .Dv MTX_SPIN diff --git a/share/man/man9/uio.9 b/share/man/man9/uio.9 index b567067..605fcc1 100644 --- a/share/man/man9/uio.9 +++ b/share/man/man9/uio.9 @@ -96,7 +96,7 @@ The I/O vector points into a process's address space. .It Dv UIO_SYSSPACE The I/O vector points into the kernel address space. .It Dv UIO_NOCOPY -Don't copy, already in object. +Do not copy, already in object. .El .It Va uio_rw The direction of the desired transfer, either @@ -125,7 +125,7 @@ The idea is that the driver maintains a private buffer for its data, and processes the request in chunks of maximal the size of this buffer. Note that the buffer handling below is very simplified and -won't work (the buffer pointer is not being advanced in case of a +will not work (the buffer pointer is not being advanced in case of a partial read), it's just here to demonstrate the .Nm handling. diff --git a/share/man/man9/vnode.9 b/share/man/man9/vnode.9 index e568c75..8a8e730 100644 --- a/share/man/man9/vnode.9 +++ b/share/man/man9/vnode.9 @@ -132,10 +132,10 @@ A character device. A symbolic link. .It Dv VSOCK A socket. -Advisory locking won't work on this. +Advisory locking will not work on this. .It Dv VFIFO A FIFO (named pipe). -Advisory locking won't work on this. +Advisory locking will not work on this. .It Dv VBAD An old style bad sector map .El diff --git a/share/termcap/termcap.5 b/share/termcap/termcap.5 index f981899..bb5b512 100644 --- a/share/termcap/termcap.5 +++ b/share/termcap/termcap.5 @@ -161,11 +161,11 @@ move_standout_mode ms safe to move while in standout mode over_strike os terminal can overstrike status_line_esc_ok es escape can be used on the status line dest_tabs_magic_smso xt tabs destructive, magic so char (t1061) -tilde_glitch hz can't print ~'s (hazeltine) +tilde_glitch hz cannot print ~'s (hazeltine) transparent_underline ul underline character overstrikes xon_xoff xo terminal uses xon/xoff handshaking -needs_xon_xoff nx padding won't work, xon/xoff required -prtr_silent 5i printer won't echo on screen +needs_xon_xoff nx padding will not work, xon/xoff required +prtr_silent 5i printer will not echo on screen hard_cursor HC cursor is hard to see non_rev_rmcup NR enter_ca_mode does not reverse exit_ca_mode no_pad_char NP pad character does not exist @@ -211,7 +211,7 @@ magic_cookie_glitch_ul ug number of blanks left by underline # max_colors Co maximum numbers of colors on screen max_pairs pa maximum number of color-pairs on the screen -no_color_video NC video attributes that can't be used with +no_color_video NC video attributes that cannot be used with colors # # The following numeric capabilities are present in the SVr4.0 term |
