clarify previous revision on optimization justification

git-svn-id: file:///var/local/repositories/ffmpeg/trunk@11598 9553f0bf-9b14-0410-a0b8-cfaf0461ba5b

diff --git a/doc/optimization.txt b/doc/optimization.txt
index f5a86a3eeeb2009f2b3bfa73667afff83b550777..27fcbba02fc6dcc911fc6e3802af925af801c894 100644 (file)
--- a/doc/optimization.txt
+++ b/doc/optimization.txt
@@ -30,15 +30,15 @@ NOTE: If you still don't understand some function, ask at our mailing list!!!
 
 When is an optimization justified?
 ----------------------------------
-Normally, clean & simple optimizations on widely used codecs can achieve
-an overall speedup of 0.1%. These speedups accumulate and can make a big
-difference after awhile. Also, if none of the following factors get
-worse due to an optimization -- speed, binary code size, source size,
-source readability -- and at least one factor improves, then an
-optimization is always a good idea even if the overall gain is less than
-0.1%. For obscure codecs that are not often used, the goal is more
-toward keeping the code clean, small, and readable than to make it 1%
-faster.
+Normally, clean and simple optimizations for widely used codecs are
+justified even if they only achieve an overall speedup of 0.1%. These
+speedups accumulate and can make a big difference after awhile. Also, if
+none of the following factors get worse due to an optimization -- speed,
+binary code size, source size, source readability -- and at least one
+factor improves, then an optimization is always a good idea even if the
+overall gain is less than 0.1%. For obscure codecs that are not often
+used, the goal is more toward keeping the code clean, small, and
+readable instead of making it 1% faster.
 
 
 WTF is that function good for ....: