Date: Sun, 27 Jan 2013 12:51:10 +0000 (UTC) From: Eitan Adler <eadler@FreeBSD.org> To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r40762 - head/en_US.ISO8859-1/books/faq Message-ID: <201301271251.r0RCpA6l036526@svn.freebsd.org>
next in thread | raw e-mail | index | archive | help
Author: eadler Date: Sun Jan 27 12:51:10 2013 New Revision: 40762 URL: http://svnweb.freebsd.org/changeset/doc/40762 Log: Simplify some language. Translators may ignore. Approved by: bcr (mentor) Modified: head/en_US.ISO8859-1/books/faq/book.xml Modified: head/en_US.ISO8859-1/books/faq/book.xml ============================================================================== --- head/en_US.ISO8859-1/books/faq/book.xml Sun Jan 27 12:51:07 2013 (r40761) +++ head/en_US.ISO8859-1/books/faq/book.xml Sun Jan 27 12:51:10 2013 (r40762) @@ -524,7 +524,7 @@ on average. Release dates are announced well in advance, so that the people working on the system know when their projects need to be finished and tested. A testing period - precedes each release, in order to ensure that the addition + precedes each release, to ensure that the addition of new features does not compromise the stability of the release. Many users regard this caution as one of the best things about &os;, even though waiting for all the latest @@ -1099,7 +1099,7 @@ url="http://www.BSDCertification.org">their site</ulink>.</para> <para>Any other organizations providing training and support - should contact the Project in order to be listed here.</para> + should contact the Project to be listed here.</para> </answer> </qandaentry> </qandaset> @@ -1272,7 +1272,7 @@ <qandaentry> <question id="need-to-run"> - <para>What do I need in order to run &os;?</para> + <para>What do I need to run &os;?</para> </question> <answer> @@ -2546,7 +2546,7 @@ bindkey ^[[3~ delete-char # for xterm</p address into a hostname. Many servers, including the <application>Telnet</application> and <application>SSH</application> servers that come with &os;, - do this in order to, among other things, store the hostname + do this to store the hostname in a log file for future reference by the administrator.</para> @@ -3018,7 +3018,7 @@ kern.timecounter.hardware: TSC -> i82 <para>The existing implementation is our best effort at meeting as many of these requirements simultaneously as we - can. In order to keep <command>/bin/sh</command> small, + can. To keep <command>/bin/sh</command> small, we have not provided many of the convenience features that other shells have. That is why other more featureful shells like @@ -4225,8 +4225,8 @@ C:\="DOS"</programlisting> <answer> <para>This could happen because the pool is 100% full. - ZFS requires space on the disk in order to write - transaction metadata. In order to restore the pool + ZFS requires space on the disk to write + transaction metadata. To restore the pool to a usable state, truncate a file you want to delete.</para> @@ -4377,7 +4377,7 @@ C:\="DOS"</programlisting> </question> <answer> - <para>This is a security feature. In order to + <para>This is a security feature. To <command>su</command> to <username>root</username> (or any other account with superuser privileges), you must be in the <groupname>wheel</groupname> group. If this feature were @@ -5189,7 +5189,7 @@ options SYSVMSG # enable for <answer> <para>If you are using &man.syscons.4; (the default console driver), you can configure &os; to support a mouse pointer on - each virtual screen. In order to avoid conflicting with X, + each virtual screen. To avoid conflicting with X, &man.syscons.4; supports a virtual device called <devicename>/dev/sysmouse</devicename>. All mouse events received from the real mouse device are written to the @@ -7076,7 +7076,7 @@ CCP: Received Terminate Ack (1) state = </question> <answer> - <para>In order to log all lines of your modem + <para>To log all lines of your modem <quote>conversation</quote>, you must enable the following:</para> @@ -7113,12 +7113,12 @@ CCP: Received Terminate Ack (1) state = line in your config files so that it can interpret strings such as <literal>set phone "123 456 789"</literal> correctly and realize that the number is actually only - <emphasis>one</emphasis> argument. In order to specify a + <emphasis>one</emphasis> argument. To specify a <literal>"</literal> character, you must escape it using a backslash (<literal>\</literal>).</para> <para>When the chat interpreter parses each argument, it - re-interprets the argument in order to find any special + re-interprets the argument to find any special escape sequences such as <literal>\P</literal> or <literal>\T</literal> (see the manual page). As a result of this double-parsing, you must remember to use the correct @@ -8560,10 +8560,10 @@ panic: page fault</programlisting> capture all of them. Using the unstripped kernel image with all the debug symbols should show the exact line of kernel source code where the panic occurred. Usually you have to - read the stack trace from the bottom up in order to trace + read the stack trace from the bottom up to trace the exact sequence of events that lead to the crash. You can also use &man.kgdb.1; to print out the contents of - various variables or structures in order to examine the + various variables or structures to examine the system state at the time of the crash.</para> <tip>
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201301271251.r0RCpA6l036526>