nightmorph    07/01/03 15:04:27

  Modified:             vdr-guide.xml
  Log:
  more grammar & sentence rephrasing stuff that i should have caught in the 
last update, purely englishification stuff, hence no revbump. thanks to diox 
for catching it and for the patch, bug 159142

Revision  Changes    Path
1.6                  xml/htdocs/doc/en/vdr-guide.xml

file : 
http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/vdr-guide.xml?rev=1.6&view=markup
plain: 
http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/vdr-guide.xml?rev=1.6&content-type=text/plain
diff : 
http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/vdr-guide.xml?r1=1.5&r2=1.6

Index: vdr-guide.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/vdr-guide.xml,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -r1.5 -r1.6
--- vdr-guide.xml       3 Jan 2007 00:58:38 -0000       1.5
+++ vdr-guide.xml       3 Jan 2007 15:04:27 -0000       1.6
@@ -1,5 +1,5 @@
 <?xml version="1.0" encoding="UTF-8"?>
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/vdr-guide.xml,v 1.5 
2007/01/03 00:58:38 nightmorph Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/vdr-guide.xml,v 1.6 
2007/01/03 15:04:27 nightmorph Exp $ -->
 <!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
 
 <guide link="/doc/en/vdr-guide.xml">
@@ -153,11 +153,11 @@
 <body>
 
 <p>
-It's recommended to mark every driver as module, so that you can to add the
+It's recommended to mark every driver as module, so that you can add the
 required module dynamically, especially if you don't know the module name. If
-you know the module name already, select the driver as a built-in driver.
-Compile the kernel, install the modules and boot it. Check to see if your 
kernel
-has successfully detected your card by using <c>dmesg</c>.
+you already know the module name, select the driver as a built-in driver.
+Compile the kernel, install the modules and boot it. You can check if your
+kernel has successfully detected your card by using <c>dmesg</c>.
 </p>
 
 <pre caption="Checking kernel output">
@@ -301,9 +301,9 @@
 </pre>
 
 <p>
-Now it should be possible to watch <c>lircd</c> running and decoding 
key-presses.
-Just run the command <c>irw</c>. Stop it with pressing Ctrl+C when you have
-enough.
+Now it should be possible to watch <c>lircd</c> capturing and decoding key
+presses. Just run the command <c>irw</c>. Stop it by pressing Ctrl+C when you
+have enough.
 </p>
 
 <pre caption="Testing LIRC">
@@ -374,8 +374,8 @@
 </pre>
 
 <p>
-em8300-modules needs some configuration that depends on the exact used
-revision of the card.
+The em8300 module need some configuration that depends on the exact revision of
+that card.
 </p>
 
 <!--
@@ -493,9 +493,9 @@
 </pre>
 
 <p>
-If you only want to use <c>vdr-xineliboutput</c> to view the picture
-on the same PC running VDR you can now
-<uri link="#channel_list">continue with configuring your channel-list</uri>.
+If you only want to use <c>vdr-xineliboutput</c> to view the picture on the 
same
+computer as the one running VDR you can continue with <uri
+link="#channel_list">configuring your channel list</uri>.
 </p>
 
 <p>
@@ -532,13 +532,10 @@
 <body>
 
 <p>
-To make VDR really useful you need to create an appropriate channel list.
-</p>
-
-<p>
-There is more than one way to get a working list of channels (besides
-downloading one). The channel list installed by default is for DVB-S reception
-on Astra on 19.2°E.
+To make VDR really useful you need to create an appropriate channel list. There
+is more than one way to get a working list of channels (besides downloading
+one). The channel list installed by default is for DVB-S reception on Astra on
+19.2°E.
 </p>
 
 </body>



-- 
[email protected] mailing list

Reply via email to