smithj      05/07/16 15:08:25

  Modified:    xml/htdocs/doc/en gentoo-amd64-faq.xml
  Log:
  grammer fixes (cleaning up after neysx ;-)

Revision  Changes    Path
1.2       +24 -23    xml/htdocs/doc/en/gentoo-amd64-faq.xml

file : 
http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/gentoo-amd64-faq.xml?rev=1.2&content-type=text/x-cvsweb-markup&cvsroot=gentoo
plain: 
http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/gentoo-amd64-faq.xml?rev=1.2&content-type=text/plain&cvsroot=gentoo
diff : 
http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/gentoo-amd64-faq.xml.diff?r1=1.1&r2=1.2&cvsroot=gentoo

Index: gentoo-amd64-faq.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/gentoo-amd64-faq.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- gentoo-amd64-faq.xml        16 Jul 2005 09:44:33 -0000      1.1
+++ gentoo-amd64-faq.xml        16 Jul 2005 15:08:25 -0000      1.2
@@ -1,6 +1,6 @@
 <?xml version="1.0" encoding="UTF-8"?>
 <!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/gentoo-amd64-faq.xml,v 1.1 
2005/07/16 09:44:33 neysx Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/gentoo-amd64-faq.xml,v 1.2 
2005/07/16 15:08:25 smithj Exp $ -->
 
 <guide link="/doc/en/gentoo-amd64-faq.xml">
 <title>Gentoo Linux/AMD64 Frequently Asked Questions</title>
@@ -38,7 +38,7 @@
 <p>
 This document contains the most commonly asked questions about Gentoo/AMD64. We
 intend to help and provide useful information about Gentoo/AMD64. Some of these
-questions can be found in forums, irc or mailing lists. If you have suggestions
+questions can be found in forums, irc, or mailing lists. If you have 
suggestions
 or questions about this FAQ, you are welcome to send an e-mail to the authors
 explaining the problem.
 </p>
@@ -142,7 +142,7 @@
 For example, you should use <c>CFLAGS="-march=k8 -O2 -pipe"</c> for Athlon64 or
 Opteron and <c>CFLAGS="-march=nocona -O2 -pipe"</c> for a EM64T processor. If
 you plan to use a 32-bit chroot, you should use <c>CFLAGS="-march=athlon-xp
--O2 -pipe -msse2"</c> for a AMD64 processor and for a EM64T, you should use
+-O2 -pipe -msse2"</c> for a AMD64 processor; for a EM64T, you should use
 <c>CFLAGS="-march=pentium4 -O2 -pipe"</c> <e>inside the chroot</e>.
 </p>
 
@@ -152,7 +152,7 @@
 </note>
 
 <warn>
-You should <e>never</e> stick <c>-fPIC</c>, <c>-m32</c> or <c>-m64</c> into
+You should <e>never</e> place <c>-fPIC</c>, <c>-m32</c> or <c>-m64</c> in
 your <c>CFLAGS</c>. They are automatically added whenever they are needed.
 Please also note that the <c>-Os</c> flag is currently not supported.
 </warn>
@@ -164,16 +164,16 @@
 <body>
 
 <p>
-You can use almost all kernel sources available in Portage. We recommend to use
-<c>gentoo-sources</c> because it is a special flavor kernel designed for Gentoo
-Linux. It contains lots of AMD64-specific patches and therefore is the only
-flavor supported by Gentoo/AMD64. You can try <c>vanilla-sources</c> as well.
-If you feel brave or you need extra hardware support, you can always try the
-experimental kernel from Andrew Morton called <c>mm-sources</c>.
+You can use almost all kernel sources available in Portage. We recommend using
+<c>gentoo-sources</c> because it is a special kernel designed for Gentoo Linux.
+It contains lots of AMD64-specific patches and therefore is the only kernel
+officially supported by Gentoo/AMD64. You can try <c>vanilla-sources</c> as
+well. If you feel brave or you need extra hardware support, you can always try
+the experimental kernel from Andrew Morton called <c>mm-sources</c>.
 </p>
 
 <warn>
-You should watch out for some kernel features which are not tested well, such
+You should watch out for some kernel features which are not well tested, such
 as <c>PREEMPT</c>.
 </warn>
 
@@ -233,18 +233,19 @@
 <body>
 
 <p>
-Right now, every AMD64 processor is able to run 32-bit code as well as 64-bit
-code. However, when you have a 32-bit application, you are unable to mix it
-with 64-bit libraries or vice versa. However, you can natively run 32-bit
-applications if all shared libraries it needs are available as 32-bit objects
-too. You can choose whether you want multilib support or not by selecting the
+Every AMD64 processor is able to run 32-bit code as well as 64-bit code.
+However, when you have a 32-bit application, you are unable to mix it with
+64-bit libraries or vice versa. You can, however, natively run 32-bit
+applications if all shared libraries it needs are available as 32-bit objects.
+You can choose whether you want multilib support or not by selecting the
 according profile. The default is a multilib-enabled profile.
 </p>
 
 <note>
-If you use an old profile (2004.3 or older), please upgrade to 2005.0 and read
-the <uri link="/proj/en/base/amd64/howtos/index.xml?part=1&amp;chap=1">2005.0
-Upgrade Guide</uri> carefully.
+If you are using an old profile (2004.3 or older), please upgrade to 2005.0 and
+read the <uri
+link="/proj/en/base/amd64/howtos/index.xml?part=1&amp;chap=1">2005.0 Upgrade
+Guide</uri> carefully.
 </note>
 
 </body>
@@ -268,7 +269,7 @@
 <p>
 Due to several differences between an <c>x86</c> and an <c>amd64</c>
 installation, it is impossible to upgrade. Please perform a fresh install. The
-installation is slightly different than an x86 one, therefore please use the
+installation is slightly different than an x86 one, so please use the
 <uri link="/doc/en/handbook/handbook-amd64.xml">AMD64 Handbook</uri>.
 </p>
 
@@ -309,7 +310,7 @@
 
 <p>
 You have to compile your kernel with support for these features. You just need
-to enable these features below:
+to enable the features below:
 </p>
 
 <pre caption="Kernel options for Cool'n'Quiet/Powernow">
@@ -336,8 +337,8 @@
 </pre>
 
 <p>
-Now you only have to run <c>rc-update add cpudyn default</c> to make sure it
-gets started every time you boot.
+Now you only have to run <c>rc-update add cpudyn default</c> to make sure it is
+started every time you boot.
 </p>
 
 </body>



-- 
[email protected] mailing list

Reply via email to