[Ffmpeg-cvslog] CVS: ffmpeg/doc ffmpeg-doc.texi,1.87,1.88

[Diego Biurrun CVS]

Update of /cvsroot/ffmpeg/ffmpeg/doc
In directory mail:/var2/tmp/cvs-serv30901/doc

Modified Files:
	ffmpeg-doc.texi 
Log Message:
spelling/grammar/wording


Index: ffmpeg-doc.texi
===================================================================
RCS file: /cvsroot/ffmpeg/ffmpeg/doc/ffmpeg-doc.texi,v
retrieving revision 1.87
retrieving revision 1.88
diff -u -d -r1.87 -r1.88
--- ffmpeg-doc.texi	26 Jul 2005 16:41:34 -0000	1.87
+++ ffmpeg-doc.texi	5 Aug 2005 01:06:04 -0000	1.88
@@ -14,8 +14,9 @@
 a live audio/video source.
   
 The command line interface is designed to be intuitive, in the sense
-that ffmpeg tries to figure out all the parameters, when
-possible. You have usually to give only the target bitrate you want.
+that FFmpeg tries to figure out all parameters that can possibly be
+derived automatically. You usually only have to specify the target
+bitrate you want.
 
 FFmpeg can also convert from any sample rate to any other, and resize
 video on the fly with a high quality polyphase filter.
[...1133 lines suppressed...]
+result file. A 'diff' is launched to compare the reference results and
 the result file.
 
-The regression test then goes on to test the ffserver code with a 
+The regression tests then go on to test the FFserver code with a
 limited set of streams. It is important that this step runs correctly
 as well.
 
 Run 'make test' to test all the codecs and formats.
 
-Run 'make fulltest' to test all the codecs, formats and ffserver.
+Run 'make fulltest' to test all the codecs, formats and FFserver.
 
-[Of course, some patches may change the regression tests results. In
-this case, the regression tests reference results shall be modified
+[Of course, some patches may change the results of the regression tests. In
+this case, the reference results of the regression tests shall be modified
 accordingly].
 
 @bye