os/doc
3
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity

Spellcheck.

Browse source
This commit is contained in:
Murray Stokely 2005-05-04 14:17:09 +00:00
parent d8d25ac300
commit 40c95a5807
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/head/; revision=24438
3 changed files with 3 additions and 3 deletions
en_US.ISO8859-1/books/developers-handbook
secure
chapter.sgml
sockets
chapter.sgml
x86
chapter.sgml

2
en_US.ISO8859-1/books/developers-handbook/secure/chapter.sgml
View file

@ -9,7 +9,7 @@
<authorgroup>
<author>
<firstname>Murray</firstname>
<surname>Stockely</surname>
<surname>Stokely</surname>
<contrib>Contributed by </contrib>
</author>
</authorgroup>

2
en_US.ISO8859-1/books/developers-handbook/sockets/chapter.sgml
View file

@ -927,7 +927,7 @@ int connect(int s, const struct sockaddr *name, socklen_t namelen);
the value returned by the <function>socket</function>
function. The <varname>name</varname> is a pointer to
<varname>sockaddr</varname>, the structure we have talked
about extensively. Finaly, <varname>namelen</varname>
about extensively. Finally, <varname>namelen</varname>
informs the system how many bytes are in our
<varname>sockaddr</varname> structure.</para>

2
en_US.ISO8859-1/books/developers-handbook/x86/chapter.sgml
View file

@ -2701,7 +2701,7 @@ If you examine your copy of <filename>syscalls.master</filename>,
you will find two separate syscalls named <function role="syscall">mmap</function>.
This is because of evolution of &unix;: There was the traditional
<acronym>BSD</acronym> <function role="syscall">mmap</function>,
syscall 71. That one was superceded by the <acronym>&posix;</acronym> <function role="syscall">mmap</function>,
syscall 71. That one was superseded by the <acronym>&posix;</acronym> <function role="syscall">mmap</function>,
syscall 197. The FreeBSD system supports both because
older programs were written by using the original <acronym>BSD</acronym>
version. But new software uses the <acronym>&posix;</acronym> version,