path: root/en_US.ISO8859-1/books/developers-handbook
diff options
Diffstat (limited to 'en_US.ISO8859-1/books/developers-handbook')
4 files changed, 8 insertions, 8 deletions
diff --git a/en_US.ISO8859-1/books/developers-handbook/ipv6/chapter.xml b/en_US.ISO8859-1/books/developers-handbook/ipv6/chapter.xml
index 568cc8ba35..6a51621e89 100644
--- a/en_US.ISO8859-1/books/developers-handbook/ipv6/chapter.xml
+++ b/en_US.ISO8859-1/books/developers-handbook/ipv6/chapter.xml
@@ -822,16 +822,16 @@ fe80:2::%ep0/64 link#2 UC ep0</screen>
packet processing code in the way BSD IPv4 code is
implemented, kernel stack may overflow due to long function
call chain. sys/netinet6 code is carefully designed to
- avoid kernel stack overflow. Because of this, sys/netinet6
+ avoid kernel stack overflow, so sys/netinet6
code defines its own protocol switch structure, as "struct
ip6protosw" (see
<filename>netinet6/ip6protosw.h</filename>). There is no
such update to IPv4 part (sys/netinet) for compatibility,
but small change is added to its pr_input() prototype. So
- "struct ipprotosw" is also defined. Because of this, if you
+ "struct ipprotosw" is also defined. As a result, if you
receive IPsec-over-IPv4 packet with massive number of IPsec
headers, kernel stack may blow up. IPsec-over-IPv6 is okay.
- (Off-course, for those all IPsec headers to be processed,
+ (Of-course, for those all IPsec headers to be processed,
each such IPsec header must pass each IPsec check. So an
anonymous attacker will not be able to do such an
diff --git a/en_US.ISO8859-1/books/developers-handbook/kerneldebug/chapter.xml b/en_US.ISO8859-1/books/developers-handbook/kerneldebug/chapter.xml
index 8fd50f0d68..793d728368 100644
--- a/en_US.ISO8859-1/books/developers-handbook/kerneldebug/chapter.xml
+++ b/en_US.ISO8859-1/books/developers-handbook/kerneldebug/chapter.xml
@@ -679,7 +679,7 @@ options DIAGNOSTIC</programlisting>
&man.dcons.4; provides similar functionality as a serial
console. It emulates two serial ports, one for the console
and <acronym>DDB</acronym>, the other for
- <acronym>GDB</acronym>. Because remote memory access is fully
+ <acronym>GDB</acronym>. Since remote memory access is fully
handled by the hardware, the &man.dcons.4; buffer is
accessible even when the system crashes.</para>
diff --git a/en_US.ISO8859-1/books/developers-handbook/secure/chapter.xml b/en_US.ISO8859-1/books/developers-handbook/secure/chapter.xml
index 8e00147c82..02b062f20c 100644
--- a/en_US.ISO8859-1/books/developers-handbook/secure/chapter.xml
+++ b/en_US.ISO8859-1/books/developers-handbook/secure/chapter.xml
@@ -310,7 +310,7 @@ int main() {
<para>There are at least 6 different IDs associated with any
- given process. Because of this you have to be very careful with
+ given process, and you must therefore be very careful with
the access that your process has at any given time. In
particular, all seteuid applications should give up their
privileges as soon as it is no longer required.</para>
diff --git a/en_US.ISO8859-1/books/developers-handbook/sockets/chapter.xml b/en_US.ISO8859-1/books/developers-handbook/sockets/chapter.xml
index 6173905a07..43b32f9b78 100644
--- a/en_US.ISO8859-1/books/developers-handbook/sockets/chapter.xml
+++ b/en_US.ISO8859-1/books/developers-handbook/sockets/chapter.xml
@@ -101,7 +101,7 @@
computer at speeds approaching the speed of light, it often
travels considerably slower between two computers.</para>
- <para>Because the languages used in data communications are so
+ <para>As the languages used in data communications are so
terse, we usually refer to them as
<emphasis>protocols</emphasis> rather than languages.</para>
@@ -337,7 +337,7 @@
extract the <emphasis><acronym>PNG</acronym> file</emphasis>
from it.</para>
- <para>Because of the complexity of internetworking, we cannot just
+ <para>Due to the complexity of internetworking, we cannot just
use the <function role="syscall">open</function> system call, or
the <function>open()</function> C function. Instead, we need to
take several steps to <quote>opening</quote> a socket.</para>
@@ -1381,7 +1381,7 @@ int main() {
<para>Not all protocols are that simple. Many receive a
request from the client, reply to it, then receive another
- request from the same client. Because of that, they do
+ request from the same client. As a result, they do
not know in advance how long they will be serving the
client. Such servers usually start a new process for each
client. While the new process is serving its client, the