X-Git-Url: https://git.cworth.org/git?p=cworth.org;a=blobdiff_plain;f=src%2Fintel%2Fperformance_measurement.mdwn;h=66454c09efeba23027cb916f0866b8acbb3e7103;hp=288e12de8a84b38a667a491d98359f02f7b446f6;hb=2316b07ba6f4f3ac1768aee62e214686ee74f3a8;hpb=9cff491575987c95cb246ba8dd53792129d400a3

diff --git a/src/intel/performance_measurement.mdwn b/src/intel/performance_measurement.mdwn
index 288e12d..66454c0 100644
--- a/src/intel/performance_measurement.mdwn
+++ b/src/intel/performance_measurement.mdwn
@@ -57,14 +57,14 @@ future. See below for what I suggest instead.
 
 For 3D performance, everybody knows this lesson already. Nobody
 measures the performance of "draw the same triangles over and
-over". And when a program that does that (like glxgears) everybody
-laughs if someone tries to take its frames-per-second report
-seriously. In fact, the phrase "glxgears is not a benchmark" is a
-catchphrase among 3D developers. Instead, 3D measurement is made with
-"benchmark modes" in the 3D applications that people actually care
-about, (which as far as I can tell is just games for some reason). In
-the benchmark mode, a sample session of recorded input is replayed as
-quickly as possible and a performance measurement is reported.
+over". And if someone does, (by seriously quoting glxgear fps numbers,
+for example), then everybody gets a good laugh. In fact, the phrase
+"glxgears is not a benchmark" is a catchphrase among 3D
+developers. Instead, 3D measurement is made with "benchmark modes" in
+the 3D applications that people actually care about, (which as far as
+I can tell is just games for some reason). In the benchmark mode, a
+sample session of recorded input is replayed as quickly as possible
+and a performance measurement is reported.
 
 As a rule, our 2D applications don't have similar benchmark
 modes. (There are some exceptions such as the trender utility for