X-Git-Url: https://git.sesse.net/?a=blobdiff_plain;f=analyzer.rst;h=72305df877d53340ff13f52ff2615140efdbce72;hb=HEAD;hp=f1adf5f3c82f5d0cacb69a12060bcd3510fcc778;hpb=9a3f9170dcdd59b37480d0dd81f864ea96109839;p=nageru-docs

diff --git a/analyzer.rst b/analyzer.rst
index f1adf5f..72305df 100644
--- a/analyzer.rst
+++ b/analyzer.rst
@@ -9,10 +9,10 @@ or that one end or the other is doing something wrong in the HDMI handshake.)
 This means that it can be useful to verify that there are no subtle color shifts,
 and that the entire 0–255 brightness range is both being input and output.
 
-The **frame analyzer**, new in Nageru 1.6.0 and available from the video menu,
+The **frame analyzer**, available from the video menu,
 can help with this.  It allows you to look at any input, grab a frame (manually
 or periodically), and then hover over specific pixels to look at their RGB
-values. When you're done, simply close it, and it will stop grabbing frames.
+values. When you're done, close it, and it will stop grabbing frames.
 
 .. _synthetictests:
 
@@ -20,7 +20,7 @@ Synthetic tests and common problems
 -----------------------------------
 
 If your input is synthetic, such as from a computer, you may want to use an
-image such as this one as your test source (simply right-click and save):
+image such as this one as your test source (right-click and save):
 
 .. image:: images/wedges.png
 
@@ -31,7 +31,7 @@ with slightly fewer steps: 255, 238, 221, 204, 187, 170, 153, 136,
 119, 102, 85, 68, 51, 34, 17, 0). (You can also use any other picture
 where you know the right pixel values, of course.)
 
-Using the frame analyzer, you can simply look at each value to see if the input
+Using the frame analyzer, you can look at each value to see if the input
 matches the expected values. Being off-by-one (or even occasionally two)
 is normal due to Y'CbCr rounding errors, but more than this indicates that
 something in your chain is doing something wrong with the pixel values.
@@ -53,7 +53,7 @@ Common errors include:
 
 Nageru cannot correct arbitrary input problems, but the most common ones
 can be fixed by selecting a different *input interpretation* for the card in question.
-Simply right-click the input, and you can choose from a variety of
+Right-click the input, and you can choose from a variety of
 different ones. Optionally, check the settings on your sending device
 to see if they can be corrected, as this is usually a better choice
 than forcing Nageru to interpret the output in a nonstandard way.