- You can do coverage testing for a file of Lisp code by first using
-the command @kbd{M-x testcover-start @key{RET} @var{file} @key{RET}}
-to instrument it. Then test your code by calling it one or more
-times. Then use the command @kbd{M-x testcover-mark-all} to display
-``splotches'' on the code to show where coverage is insufficient. The
-command @kbd{M-x testcover-next-mark} will move point forward to the
-next spot that has a splotch.
-
- Normally, a red splotch indicates the form was never completely
-evaluated; a brown splotch means it always evaluated to the same value
-(meaning there has been little testing of what is done with the
-result). However, the red splotch is skipped for forms that can't
+ You can do coverage testing for a file of Lisp code by loading the
+@code{testcover} library and using the command @kbd{M-x
+testcover-start @key{RET} @var{file} @key{RET}} to instrument the
+code. Then test your code by calling it one or more times. Then use
+the command @kbd{M-x testcover-mark-all} to display colored highlights
+on the code to show where coverage is insufficient. The command
+@kbd{M-x testcover-next-mark} will move point forward to the next
+highlighted spot.
+
+ Normally, a red highlight indicates the form was never completely
+evaluated; a brown highlight means it always evaluated to the same
+value (meaning there has been little testing of what is done with the
+result). However, the red highlight is skipped for forms that can't