diff options
| author | pfg <pfg@FreeBSD.org> | 2016-05-15 03:15:36 +0000 |
|---|---|---|
| committer | pfg <pfg@FreeBSD.org> | 2016-05-15 03:15:36 +0000 |
| commit | 23f338f31131ff764dde3a562b5d85ef7618ab5b (patch) | |
| tree | 4398e1a36010e89f685e91083a86f92bcb859dc3 /share | |
| parent | 43c202b5d356fab514defa4cbd675902bdb18abd (diff) | |
| download | FreeBSD-src-23f338f31131ff764dde3a562b5d85ef7618ab5b.zip FreeBSD-src-23f338f31131ff764dde3a562b5d85ef7618ab5b.tar.gz | |
MFC r298881, 298882, 298883, 298885:
Minor spelling fixes in:
tools, share, bluetooth, pmcstat, etc
Many of these have user-visible strings.
Diffstat (limited to 'share')
| -rw-r--r-- | share/examples/ipfilter/ipf-howto.txt | 6 | ||||
| -rw-r--r-- | share/examples/kld/cdev/test/Makefile | 2 |
2 files changed, 4 insertions, 4 deletions
diff --git a/share/examples/ipfilter/ipf-howto.txt b/share/examples/ipfilter/ipf-howto.txt index 54187ae..95b69dc 100644 --- a/share/examples/ipfilter/ipf-howto.txt +++ b/share/examples/ipfilter/ipf-howto.txt @@ -1036,11 +1036,11 @@ In this case, the server is running no services. Infact, it's not a server, it's a client. And this client doesn't want unauthorized packets entering its IP stack at all. However, the client wants full access to the internet and -the reply packets that such privledge entails. This simple +the reply packets that such privilege entails. This simple ruleset creates state entries for every new outgoing TCP session. Again, since a state entry is created, these new TCP sessions are free to talk back and forth as they please -without the hinderance or inspection of the firewall rule- +without the hindrance or inspection of the firewall rule- set. We mentioned that this also works for UDP and ICMP: block in quick on tun0 all @@ -1271,7 +1271,7 @@ forgeries and allow fragments: This works because every packet that should be allowed through makes it into the state table before the blocking rules are reached. The only scan this won't detect is a SYN -scan itself. If you're truely worried about that, you might +scan itself. If you're truly worried about that, you might even want to log all initial SYN packets. 3.6. Responding To a Blocked Packet diff --git a/share/examples/kld/cdev/test/Makefile b/share/examples/kld/cdev/test/Makefile index eebf54d..b108a69 100644 --- a/share/examples/kld/cdev/test/Makefile +++ b/share/examples/kld/cdev/test/Makefile @@ -73,7 +73,7 @@ WARNS?= 5 MODSTAT= /sbin/kldstat load: - @echo "This test program will call the sample kld characer device "; + @echo "This test program will call the sample kld character device "; @echo "driver." @echo @echo "The sample driver will display a message on the" |
