nightmorph 07/10/18 18:16:02 Modified: xorg-config.xml Log: buncha small coding style fixes and punctuation, spelling, and grammar fixes. no content change.
Revision Changes Path 1.24 xml/htdocs/doc/en/xorg-config.xml file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/xorg-config.xml?rev=1.24&view=markup plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/xorg-config.xml?rev=1.24&content-type=text/plain diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/xorg-config.xml?r1=1.23&r2=1.24 Index: xorg-config.xml =================================================================== RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/xorg-config.xml,v retrieving revision 1.23 retrieving revision 1.24 diff -u -r1.23 -r1.24 --- xorg-config.xml 21 Jun 2007 02:37:46 -0000 1.23 +++ xorg-config.xml 18 Oct 2007 18:16:02 -0000 1.24 @@ -1,11 +1,8 @@ <?xml version='1.0' encoding='UTF-8'?> - -<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/xorg-config.xml,v 1.23 2007/06/21 02:37:46 nightmorph Exp $ --> - <!DOCTYPE guide SYSTEM "/dtd/guide.dtd"> +<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/xorg-config.xml,v 1.24 2007/10/18 18:16:02 nightmorph Exp $ --> <guide link="/doc/en/xorg-config.xml"> - <title>The X Server Configuration HOWTO</title> <author title="Author"> @@ -235,7 +232,7 @@ probing your hardware. If it tells you it failed at some point, you're forced to manually write an <path>xorg.conf</path> file. Assuming that it didn't fail, it will have told you that it has written <path>/root/xorg.conf.new</path> ready -for you to test. So let's test :) +for you to test. So let's test. :) </p> <pre caption="Testing the xorg.conf.new file"> @@ -288,7 +285,7 @@ <p> Let us copy over the <path>xorg.conf.new</path> to <path>/etc/X11/xorg.conf</path> now, so we won't have to continuously run -<c>X -config</c> -- typing just <c>X</c> or <c>startx</c> is far more easy :) +<c>X -config</c> -- typing just <c>X</c> or <c>startx</c> is easier. :) </p> <pre caption="Copying over xorg.conf"> @@ -319,7 +316,7 @@ accordingly (you can set the value of XSESSION in <path>/etc/rc.conf</path> to make it a default for all the users on the system). </li> -<li> + <li> If all of the above fail, it will fall back to a simple window manager, usually <c>twm</c>. </li> @@ -334,7 +331,7 @@ <c>twm</c>. To finish the twm session, type in <c>exit</c> or Ctrl-D in the upcoming xterms. You can also kill the X session using the Ctrl-Alt-Backspace combination. This will however make X exit disgracefully -- something that you -might not always want. It doesn't hurt though :) +might not always want. It doesn't hurt though. :) </p> </body> @@ -395,7 +392,7 @@ </pre> <p> -Run X (<c>startx</c>) to discover it uses the resolution you want :) +Run X (<c>startx</c>) to discover it uses the resolution you want. :) </p> </body> @@ -471,7 +468,7 @@ Run <c>startx</c> and be happy about the result :) Congratulations, you now (hopefully) have a working Xorg on your system. The next step is to remove this ugly lightweight window manager and use a high-feature one (or even a desktop -environment) such as KDE or GNOME, but that's not part of this guide :) +environment) such as KDE or GNOME, but that's not part of this guide. :) </p> </body> @@ -500,7 +497,7 @@ list few of them here, be sure to <uri link="http://www.google.com";>Google</uri> for more :) As <path>xorg.conf</path> and <path>XF86Config</path> (the configuration file for the XFree86 project) use the -same syntaxis for most configuration options and more information about +same syntax for most configuration options and more information about <path>XF86Config</path> is available, we'll list those resources as well. </p> -- [EMAIL PROTECTED] mailing list
