[SCM] libav/experimental: spelling/grammar/wording

[siretart at users.alioth.debian.org]

The following commit has been merged in the experimental branch:
commit e180129f635a84278f02a613351a9968ea2c358f
Author: Diego Biurrun <diego at biurrun.de>
Date:   Mon Sep 12 15:51:29 2005 +0000

    spelling/grammar/wording
    
    Originally committed as revision 4589 to svn://svn.ffmpeg.org/ffmpeg/trunk

diff --git a/doc/faq.texi b/doc/faq.texi
index 93867fc..50bf36c 100644
--- a/doc/faq.texi
+++ b/doc/faq.texi
@@ -182,25 +182,25 @@ The build process creates ffmpeg_g, ffplay_g, etc. which contain full debug
 information. Those binaries are strip'd to create ffmpeg, ffplay, etc. If
 you need the debug information, used the *_g versions.
 
- at section I do not like the LGPL, can I contribute code under the GPL instead
+ at section I do not like the LGPL, can I contribute code under the GPL instead ?
 
-yes, as long as the code is optional and can easily and cleanly be placed under 
-#ifdef CONFIG_GPL without breaking anythng, so for example
-a new codec or filter would be ok under GPL while a bugfix to LGPL code wont
+Yes, as long as the code is optional and can easily and cleanly be placed
+under #ifdef CONFIG_GPL without breaking anything. So for example a new codec
+or filter would be OK under GPL while a bugfix to LGPL code would not.
 
- at section I want to compile xyz.c alone but my compier produced many errors
+ at section I want to compile xyz.c alone but my compiler produced many errors.
 
-common code is in its own files in libav* and is used by the individual
-codecs, they will not work without the common parts, you have to compile
-the whole libav* and if you wish disable some parts with configure
-switches, you can also try to hack it and remove more but if you seriously
-wanted to ask the question above then you are not qualified for this
+Common code is in its own files in libav* and is used by the individual
+codecs. They will not work without the common parts, you have to compile
+the whole libav*. If you wish, disable some parts with configure switches.
+You can also try to hack it and remove more, but if you had problems fixing
+the compilation failure then you are probably not qualified for this.
 
- at section visual c++ produced many errors
+ at section Visual c++ produces many errors.
 
-you need a c compiler (visual c++ is not compliant to the c standard)
-if you wish for whatever weird reason use visual c++ for your project
-then you can link the visual c++ code with libav* as long as you compile
-the later with a working c compiler
+You need a C compiler (visual C++ is not compliant to the C standard).
+If you wish - for whatever weird reason - to use visual C++ for your
+project then you can link the visual C++ code with libav* as long as
+you compile the latter with a working C compiler.
 
 @bye

-- 
Libav/FFmpeg packaging