diff options
| author | Diego Biurrun <diego@biurrun.de> | 2005-09-13 23:33:53 +0000 |
|---|---|---|
| committer | Diego Biurrun <diego@biurrun.de> | 2005-09-13 23:33:53 +0000 |
| commit | 9fcfac15bafc9ff19a56d09e5a029f04608c6c5b (patch) | |
| tree | bc72ab4b3343067ea7dc6198258e34bf9da09fee /doc/faq.texi | |
| parent | fac862c659ee9f5a2389de968a582b2860913892 (diff) | |
minor typo fixes
Originally committed as revision 4593 to svn://svn.ffmpeg.org/ffmpeg/trunk
Diffstat (limited to 'doc/faq.texi')
| -rw-r--r-- | doc/faq.texi | 8 |
1 files changed, 4 insertions, 4 deletions
diff --git a/doc/faq.texi b/doc/faq.texi index 50bf36c090..438f5e646f 100644 --- a/doc/faq.texi +++ b/doc/faq.texi @@ -196,11 +196,11 @@ 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. -@section Visual c++ produces many errors. +@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 - to use visual C++ for your -project then you can link the visual C++ code with libav* as long as +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 |