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

Minor typo corrections.

Browse source 
Approved by:	murray
This commit is contained in:
Eric Melville 2001-06-03 00:37:08 +00:00
parent 9b91b763ca
commit 5284d9ba77
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/head/; revision=9534
2 changed files with 8 additions and 8 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

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

@ -1,7 +1,7 @@
<!--
The FreeBSD Documentation Project
$FreeBSD: doc/en_US.ISO_8859-1/books/developers-handbook/secure/chapter.sgml,v 1.5 2001/05/17 01:03:07 murray Exp $
$FreeBSD: doc/en_US.ISO_8859-1/books/developers-handbook/secure/chapter.sgml,v 1.6 2001/06/02 23:24:10 dd Exp $
-->
<chapter id="secure">
@ -23,7 +23,7 @@
<para>Writing secure applications takes a very scrutinous and
pessimistic outlook on life. Applications should be run with
the principle of <quote>least privilege</quote> so that no
process is ever running than more with the bare minimum access
process is ever running with more than the bare minimum access
that it needs to accomplish its function. Previously tested
code should be reused whenever possible to avoid common
mistakes that others may have already fixed.</para>
@ -230,7 +230,7 @@ int main() {
more information about these functions see <xref
linkend="OpenBSD">. The OpenBSD <function>strlcpy</function> and
<function>strlcat</function> instructions have been in FreeBSD
since 3.5.</para>
since 3.3.</para>
<indexterm>
<primary>string copy functions</primary>
@ -357,7 +357,7 @@ int main() {
<indexterm><primary>chroot()</primary></indexterm>
<para>The traditional method of restricting access to a process
<para>The traditional method of restricting a process
is with the <function>chroot()</function> system call. This
system call changes the root directory from which all other
paths are referenced for a process and any child processes. For

8
en_US.ISO_8859-1/books/developers-handbook/secure/chapter.sgml
View file

@ -1,7 +1,7 @@
<!--
The FreeBSD Documentation Project
$FreeBSD: doc/en_US.ISO_8859-1/books/developers-handbook/secure/chapter.sgml,v 1.5 2001/05/17 01:03:07 murray Exp $
$FreeBSD: doc/en_US.ISO_8859-1/books/developers-handbook/secure/chapter.sgml,v 1.6 2001/06/02 23:24:10 dd Exp $
-->
<chapter id="secure">
@ -23,7 +23,7 @@
<para>Writing secure applications takes a very scrutinous and
pessimistic outlook on life. Applications should be run with
the principle of <quote>least privilege</quote> so that no
process is ever running than more with the bare minimum access
process is ever running with more than the bare minimum access
that it needs to accomplish its function. Previously tested
code should be reused whenever possible to avoid common
mistakes that others may have already fixed.</para>
@ -230,7 +230,7 @@ int main() {
more information about these functions see <xref
linkend="OpenBSD">. The OpenBSD <function>strlcpy</function> and
<function>strlcat</function> instructions have been in FreeBSD
since 3.5.</para>
since 3.3.</para>
<indexterm>
<primary>string copy functions</primary>
@ -357,7 +357,7 @@ int main() {
<indexterm><primary>chroot()</primary></indexterm>
<para>The traditional method of restricting access to a process
<para>The traditional method of restricting a process
is with the <function>chroot()</function> system call. This
system call changes the root directory from which all other
paths are referenced for a process and any child processes. For