From 78a3c678f62981ecd9a2be7ce70746c43c2f8e86 Mon Sep 17 00:00:00 2001 From: Diego Biurrun Date: Mon, 16 Jul 2007 08:54:59 +0000 Subject: [PATCH] spelling/grammar/wording Originally committed as revision 9694 to svn://svn.ffmpeg.org/ffmpeg/trunk --- doc/faq.texi | 8 ++++---- doc/ffmpeg-doc.texi | 6 +++--- 2 files changed, 7 insertions(+), 7 deletions(-) diff --git a/doc/faq.texi b/doc/faq.texi index 01db96e..d26c6b5 100644 --- a/doc/faq.texi +++ b/doc/faq.texi @@ -419,12 +419,12 @@ see @url{http://www.iversenit.dk/dev/ffmpeg-headers/} see @url{http://svn.mplayerhq.hu/michael/trunk/docs/} -@section how do i feed rtp-h263 (and likely other rtp bastardizations of codecs) to libavcodec? +@section how do I feed H.263-RTP (and likely other RTP bastardizations of codecs) to libavcodec? -Remove _ALL_ rtp trash and either feed the fragments through a AVParser and +Remove _ALL_ RTP trash and either feed the fragments through an AVParser and then into the decoder or merge the fragments yourself into proper frames and -feed them into the decoder. Note! the payload of h263-rtp is is not valid -h263 you at least have to merge the first and last bytes discarding rtp trash +feed them into the decoder. Note: The payload of H.263-RTP is not valid +H.263 you at least have to merge the first and last bytes discarding RTP trash from them, possibly more. @bye diff --git a/doc/ffmpeg-doc.texi b/doc/ffmpeg-doc.texi index c759e87..cec71f9 100644 --- a/doc/ffmpeg-doc.texi +++ b/doc/ffmpeg-doc.texi @@ -1503,8 +1503,8 @@ The TAB character is forbidden outside of Makefiles as is any form of trailing whitespace. Commits containing either will be rejected by the Subversion repository. -Main priority in FFmpeg is simplicity and small code size (=less -bugs). +The main priority in FFmpeg is simplicity and small code size in order to +minimize the bug count. Comments: Use the JavaDoc/Doxygen format (see examples below) so that code documentation @@ -1689,7 +1689,7 @@ It also helps quite a bit if you tell us what the patch does (for example 'replaces lrint by lrintf'), and why (for example '*BSD isn't C99 compliant and has no lrint()') -Also please if you send several patches, send each patch as separate mail, +Also please if you send several patches, send each patch as a separate mail, do not attach several unrelated patches to the same mail. @section patch submission checklist -- 2.7.4