Gentoo Archives: gentoo-doc-cvs

From:	Joshua Saddler <nightmorph@××××××××××××.org>
To:	gentoo-doc-cvs@l.g.o
Subject:	[gentoo-doc-cvs] cvs commit: faq.xml
Date:	Sun, 13 Jul 2008 03:52:53
Message-Id:	`E1KHsdl-0001h7-JM@stork.gentoo.org`

1	nightmorph 08/07/13 03:52:49
2
3	Modified: faq.xml
4	Log:
5	typo fix, no content change
6
7	Revision Changes Path
8	1.113 xml/htdocs/doc/en/faq.xml
9
10	file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/faq.xml?rev=1.113&view=markup
11	plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/faq.xml?rev=1.113&content-type=text/plain
12	diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/faq.xml?r1=1.112&r2=1.113
13
14	Index: faq.xml
15	===================================================================
16	RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/faq.xml,v
17	retrieving revision 1.112
18	retrieving revision 1.113
19	diff -u -r1.112 -r1.113
20	--- faq.xml 28 Feb 2008 08:25:26 -0000 1.112
21	+++ faq.xml 13 Jul 2008 03:52:49 -0000 1.113
22	@@ -329,7 +329,7 @@
23	<body>
24
25	<p>
26	-First you need to find our what CPU you use. Suppose it's a Pentium-M. Then you
27	+First you need to find out what CPU you use. Suppose it's a Pentium-M. Then you
28	need to find out what CPU it is, instruction-wise, compatible with. You may
29	need to consult the CPU's vendor website for this, although <uri
30	link="http://www.google.com">Google</uri> is at least as efficient :-).
31
32
33
34	--
35	gentoo-doc-cvs@l.g.o mailing list