aboutsummaryrefslogtreecommitdiffstats
path: root/doc
diff options
context:
space:
mode:
authorDiego Biurrun <diego@biurrun.de>2007-09-13 13:45:49 +0000
committerDiego Biurrun <diego@biurrun.de>2007-09-13 13:45:49 +0000
commit2956957151ff4bd1975c13ff5c8df3024329a643 (patch)
treeddaa5bc423671053bf48ff4907c7af70580f392b /doc
parent411f5c6abdb0eca9d2e51f690e8b8fe5f91c6c3f (diff)
downloadffmpeg-2956957151ff4bd1975c13ff5c8df3024329a643.tar.gz
misc wording/grammar/spelling improvements
Originally committed as revision 10488 to svn://svn.ffmpeg.org/ffmpeg/trunk
Diffstat (limited to 'doc')
-rw-r--r--doc/faq.texi10
1 files changed, 5 insertions, 5 deletions
diff --git a/doc/faq.texi b/doc/faq.texi
index daa2dc3451..8e27780a11 100644
--- a/doc/faq.texi
+++ b/doc/faq.texi
@@ -447,18 +447,18 @@ see @url{http://www.iversenit.dk/dev/ffmpeg-headers/}
see @url{http://svn.mplayerhq.hu/michael/trunk/docs/}
-@section how do I feed H.263-RTP (and other codecs in RTP) to libavcodec?
+@section How do I feed H.263-RTP (and other codecs in RTP) to libavcodec?
Even if peculiar since it is network oriented, RTP is a container like any
other. You have to @emph{demux} RTP before feeding the payload to libavcodec.
In this specific case please look at RFC 4629 to see how it should be done.
-@section AVStream.r_frame_rate is wrong, its much larger than the frame rate
+@section AVStream.r_frame_rate is wrong, it is much larger than the framerate.
r_frame_rate is NOT the average framerate, it is the smallest framerate
-with which all timestamps can be accurately represented, so no it is not
-wrong if its larger than the average!
-for example if you have 25 and 30 fps content mixed then r_frame_rate
+that can accurately represent all timestamps. So no, it is not
+wrong if it is larger than the average!
+For example, if you have mixed 25 and 30 fps content, then r_frame_rate
will be 150.
@bye