Remove overuse of “simply”.

[nageru-docs] / analyzer.rst

diff --git a/analyzer.rst b/analyzer.rst
index 5496eff859b16bbaf87a7454c5660cfc581c8b82..72305df877d53340ff13f52ff2615140efdbce72 100644 (file)
--- a/analyzer.rst
+++ b/analyzer.rst
@@ -12,7 +12,7 @@ and that the entire 0–255 brightness range is both being input and output.
 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.