changeset 12348:9782f90f4f44

typos, wording
author diego
date Thu, 29 Apr 2004 13:02:44 +0000
parents 98c6948a859b
children 1deefcd5428d
files DOCS/xml/en/faq.xml
diffstat 1 files changed, 13 insertions(+), 12 deletions(-) [+]
line wrap: on
line diff
--- a/DOCS/xml/en/faq.xml	Thu Apr 29 11:24:03 2004 +0000
+++ b/DOCS/xml/en/faq.xml	Thu Apr 29 13:02:44 2004 +0000
@@ -443,10 +443,10 @@
 <listitem><para>ct: total A-V sync correction done</para></listitem>
 <listitem><para>frames played (counting from last seek)</para></listitem>
 <listitem><para>frames decoded (counting from last seek)</para></listitem>
-<listitem><para>video codec cpu usage in percent (for slices and DR this includes
+<listitem><para>video codec CPU usage in percent (for slices and DR this includes
 video_out)</para></listitem>
-<listitem><para>video_out cpu usage</para></listitem>
-<listitem><para>audio codec cpu usage in percent</para></listitem>
+<listitem><para>video_out CPU usage</para></listitem>
+<listitem><para>audio codec CPU usage in percent</para></listitem>
 <listitem><para>frames needed to drop to maintain A-V sync</para></listitem>
 <listitem><para>current level of image postprocessing (when using
 <option>-autoq</option>)</para></listitem>
@@ -467,7 +467,7 @@
 
 <qandaentry>
 <question><para>
-Why is video_out cpu usage zero (0%) for some files?
+Why is video_out CPU usage zero (0%) for some files?
 </para></question>
 <answer><para>
 It's not zero, but it's called from the codec and thus cannot be measured
@@ -632,7 +632,7 @@
 How can I solve my problem?
 </para></question>
 <answer><para>
-Just change your video output device. Issue the following comand to get
+Just change your video output device. Issue the following command to get
 a list of available video output drivers:
 <screen>
 mplayer -vo help
@@ -673,7 +673,7 @@
 <filename>~/.mplayer/</filename>, <filename>/etc/</filename>,
 <filename>/usr/local/etc/</filename> or a similar location? Remove it,
 outdated <filename>codecs.conf</filename> files can cause obscure
-problems. <application>MPlayer</application> will use its builtin one instead.
+problems. <application>MPlayer</application> will use its built-in one instead.
 </para></answer>
 </qandaentry>
 
@@ -775,18 +775,18 @@
 patches (for example Solar Designer's OpenWall patch) which forces loading
 libraries to very low addresses. Because <filename>l3codeca.acm</filename> is a
 non-relocatable DLL, it must be loaded to <literal>0x00400000</literal>, we can't
-change this. You should use a non-patched kernel, or use <application>MPlayer's</application>
+change this. You should use a non-patched kernel, or use <application>MPlayer</application>'s
 <option>-afm 1</option> option to disable using <filename>l3codeca.acm</filename>.
 </para></answer>
 </qandaentry>
 
 <qandaentry>
 <question><para>
-My computer plays MS DivX AVIs with resolutions ~ 640x300 and stereo mp3 sound
+My computer plays MS DivX AVIs with resolutions ~ 640x300 and stereo MP3 sound
 too slow. When I use <option>-nosound</option> option, everything is OK (but quiet).
 </para></question>
 <answer><para>
-Your machine is too slow or your soundcard driver is broken. Consult the
+Your machine is too slow or your sound card driver is broken. Consult the
 documentation to see if you can improve performance.
 </para></answer>
 </qandaentry>
@@ -903,7 +903,8 @@
 applications.
 </para></question>
 <answer><para>
-Your card probably misreports its colorspace capacity. Try with YUY2 instead of
+Your card probably reports some colorspaces as supported when in fact
+it does not support them. Try with YUY2 instead of the
 default YV12 (see the <link linkend="tv-input">TV</link> section).
 </para></answer>
 </qandaentry>
@@ -970,7 +971,7 @@
 
 <qandaentry>
 <question><para>
-How can I play MPEG Layer 2 (mp2) audio files?
+How can I play MPEG Layer 2 (MP2) audio files?
 </para></question>
 <answer><para>
 You have to use <option>-rawaudio on:format=0x50</option>.
@@ -1048,7 +1049,7 @@
 </para></question>
 <answer><para>
 The <systemitem>tdfx</systemitem> driver in XFree86 4.0.2/4.0.3 had this bug. This was
-solved by <ulink url="http://www.xfree86.org/cvs/changes_4_1.html">bugfix #621
+solved by <ulink url="http://www.xfree86.org/cvs/changes_4_1.html">bug fix #621
 of the XFree86 4.1.0 CVS log</ulink>. So upgrade to XFree86 4.1.0 or later.
 Alternatively, either download (at least) DRI version 0.6 from the
 <ulink url="http://dri.sourceforge.net">DRI homepage</ulink>, or use CVS DRI.