From 9c0ef6d5b844fbcf890bd4a959fb390e4ef5efcd Mon Sep 17 00:00:00 2001 From: Oliver Fromme Date: Thu, 5 Aug 2010 16:28:17 +0000 Subject: [PATCH] Fix a bunch of errors (spelling and similar). As des noted, the section on SCTP would benefit from a rewrite by a native speaker (which I am not). Any volunteers? Approved by: des (mentor) MFC after: 1 week --- sys/conf/NOTES | 50 ++++++++++++++++++++++++-------------------------- 1 file changed, 24 insertions(+), 26 deletions(-) diff --git a/sys/conf/NOTES b/sys/conf/NOTES index 2cf18f1cef2a..0a44e1c7ab92 100644 --- a/sys/conf/NOTES +++ b/sys/conf/NOTES @@ -195,7 +195,7 @@ options ROOTDEVNAME=\"ufs:da0s2e\" # workloads on SMP machines. It supports cpu-affinity, per-cpu runqueues # and scheduler locks. It also has a stronger notion of interactivity # which leads to better responsiveness even on uniprocessor machines. This -# will eventually become the default scheduler. +# is the default scheduler. # # SCHED_STATS is a debugging option which keeps some stats in the sysctl # tree at 'kern.sched.stats' and is useful for debugging scheduling decisions. @@ -501,7 +501,7 @@ options REGRESSION #options RESTARTABLE_PANICS # -# This option let some drivers co-exist that can't co-exist in a running +# This option lets some drivers co-exist that can't co-exist in a running # system. This is used to be able to compile all kernel code in one go for # quality assurance purposes (like this file, which the option takes it name # from.) @@ -521,7 +521,7 @@ options STACK # # The hwpmc driver that allows the use of in-CPU performance monitoring -# counters for performance monitoring. The base kernel needs to configured +# counters for performance monitoring. The base kernel needs to be configured # with the 'options' line, while the hwpmc device can be either compiled # in or loaded as a loadable kernel module. # @@ -592,12 +592,12 @@ options FLOWTABLE # soon to have a new base RFC and many many more # extensions. This release supports all the extensions # including many drafts (most about to become RFC's). -# It is the premeier SCTP implementation in the NET +# It is the reference implementation of SCTP # and is quite well tested. # # Note YOU MUST have both INET and INET6 defined. -# you don't have to enable V6, but SCTP is -# dual stacked and so far we have not teased apart +# You don't have to enable V6, but SCTP is +# dual stacked and so far we have not torn apart # the V6 and V4.. since an association can span # both a V6 and V4 address at the SAME time :-) # @@ -605,7 +605,7 @@ options SCTP # There are bunches of options: # this one turns on all sorts of # nastly printing that you can -# do. Its all controled by a +# do. It's all controlled by a # bit mask (settable by socket opt and # by sysctl). Including will not cause # logging until you set the bits.. but it @@ -615,9 +615,9 @@ options SCTP # faster.. if you are not debugging don't use. options SCTP_DEBUG # -# This option turns off the CRC32c checksum. Basically -# You will not be able to talk to anyone else that -# has not done this. Its more for expermentation to +# This option turns off the CRC32c checksum. Basically, +# you will not be able to talk to anyone else who +# has not done this. Its more for experimentation to # see how much CPU the CRC32c really takes. Most new # cards for TCP support checksum offload.. so this # option gives you a "view" into what SCTP would be @@ -636,13 +636,13 @@ options SCTP_WITH_NO_CSUM # see. I have used this to produce interesting # charts and graphs as well :-> # -# I have not yet commited the tools to get and print +# I have not yet committed the tools to get and print # the logs, I will do that eventually .. before then # if you want them send me an email rrs@freebsd.org # You basically must have ktr(4) enabled for these # and you then set the sysctl to turn on/off various # logging bits. Use ktrdump(8) to pull the log and run -# it through a dispaly program.. and graphs and other +# it through a display program.. and graphs and other # things too. # options SCTP_LOCK_LOGGING @@ -798,8 +798,7 @@ device sppp # The `bpf' device enables the Berkeley Packet Filter. Be # aware of the legal and administrative consequences of enabling this -# option. The number of devices determines the maximum number of -# simultaneous BPF clients programs runnable. DHCP requires bpf. +# option. DHCP requires bpf. device bpf # The `disc' device implements a minimal network interface, @@ -938,7 +937,7 @@ options TCPDEBUG options MBUF_STRESS_TEST options MBUF_PROFILING -# Statically Link in accept filters +# Statically link in accept filters options ACCEPT_FILTER_DATA options ACCEPT_FILTER_DNS options ACCEPT_FILTER_HTTP @@ -996,7 +995,7 @@ options NFSSERVER #Network File System server options NFSLOCKD #Network Lock Manager options NFSCL #experimental NFS client with NFSv4 options NFSD #experimental NFS server with NFSv4 -options KGSSAPI #Kernel GSSAPI implementaion +options KGSSAPI #Kernel GSSAPI implementation # NT File System. Read-mostly, see mount_ntfs(8) for details. # For a full read-write NTFS support consider sysutils/fusefs-ntfs @@ -1059,7 +1058,7 @@ options QUOTA #enable disk quotas # if you let these users run programs, so confine it to file-servers # (but it'll save you lots of headaches in those cases). Root owned # directories are exempt and X bits are cleared. The suid bit must be -# set on the directory as well; see chmod(1) PC owners can't see/set +# set on the directory as well; see chmod(1). PC owners can't see/set # ownerships so they keep getting their toes trodden on. This saves # you all the support calls as the filesystem it's used on will act as # they expect: "It's my dir so it must be my file". @@ -1338,8 +1337,7 @@ options SCSI_PT_DEFAULT_TIMEOUT=60 # # Normally disabled because a lot of newer SCSI disks report themselves # as having SES capabilities, but this can then clot up attempts to build -# build a topology with the SES device that's on the box these drives -# are in.... +# a topology with the SES device that's on the box these drives are in.... options SES_ENABLE_PASSTHROUGH @@ -1601,7 +1599,7 @@ options ISP_DEFAULT_ROLES=2 # instruments are enabled. The tools in # /usr/sbin/dpt_* assume these to be enabled. # DPT_HANDLE_TIMEOUTS Normally device timeouts are handled by the DPT. -# If you ant the driver to handle timeouts, enable +# If you want the driver to handle timeouts, enable # this option. If your system is very busy, this # option will create more trouble than solve. # DPT_TIMEOUT_FACTOR Used to compute the excessive amount of time to @@ -1747,7 +1745,7 @@ hint.ata.1.irq="15" # ATA_CAM: Turn ata(4) subsystem controller drivers into cam(4) # interface modules. This deprecates all ata(4) # peripheral device drivers (atadisk, ataraid, atapicd, -# atapifd. atapist, atapicam) and all user-level APIs. +# atapifd, atapist, atapicam) and all user-level APIs. # cam(4) drivers and APIs will be connected instead. options ATA_STATIC_ID @@ -1822,7 +1820,7 @@ options BREAK_TO_DEBUGGER # A BREAK on a serial console goes to # Solaris implements a new BREAK which is initiated by a character # sequence CR ~ ^b which is similar to a familiar pattern used on -# Sun servers by the Remote Console. There are FreeBSD extentions: +# Sun servers by the Remote Console. There are FreeBSD extensions: # CR ~ ^p requests force panic and CR ~ ^r requests a clean reboot. options ALT_BREAK_TO_DEBUGGER @@ -2189,7 +2187,7 @@ device sound # # snd_*: Device-specific drivers. # -# The flags of the device tells the device a bit more info about the +# The flags of the device tell the device a bit more info about the # device that normally is obtained through the PnP interface. # bit 2..0 secondary DMA channel; # bit 4 set if the board uses two dma channels; @@ -2386,7 +2384,7 @@ device cmx # crystal, e.g. some new Bt878 cards. # # options BKTR_GPIO_ACCESS -# This enable IOCTLs which give user level access to the GPIO port. +# This enables IOCTLs which give user level access to the GPIO port. # # options BKTR_NO_MSP_RESET # Prevents the MSP34xx reset. Good if you initialise the MSP in another OS first @@ -2594,7 +2592,7 @@ options NSFBUFS=1024 # # Enable extra debugging code for locks. This stores the filename and -# line of whatever acquired the lock in the lock itself, and change a +# line of whatever acquired the lock in the lock itself, and changes a # number of function calls to pass around the relevant data. This is # not at all useful unless you are debugging lock code. Also note # that it is likely to break e.g. fstat(1) unless you recompile your @@ -2870,7 +2868,7 @@ options NSWBUF_MIN=120 ##################################################################### # More undocumented options for linting. -# Note that documenting these are not considered an affront. +# Note that documenting these is not considered an affront. options CAM_DEBUG_DELAY