sbolint: add note to try sbofixinfo in check_info()

1 files changed, 8 insertions, 10 deletions

diff --git a/sbofixinfo b/sbofixinfo
index 7c8028e..b467296 100755
--- a/sbofixinfo
+++ b/sbofixinfo
@@ -91,12 +91,13 @@ comprehensive checking.
 The file is modified 'in-place', in the same way as the B<-i> option
 to B<sed>(1).
 
-B<sbofixinfo> keeps a backup of the original file with the
-extension I<.bak> appended to the filename. If the backup file already
-exists, it will be silently overwritten. After the new file is generated,
-B<diff>(1) (with its B<-u> and B<--color> options) is run on the backup and modified
-files, and the backup is deleted if the new file is identical. The diff
-output also goes to stdout, so the user can see what changes were made.
+B<sbofixinfo> keeps a backup of the original file with the extension
+I<.bak> appended to the filename. If the backup file already exists,
+it will be silently overwritten. After the new file is generated,
+B<diff>(1) (with its B<-u> and B<--color> options) is run on the
+backup and modified files, and the backup is deleted if the new file
+is identical. The diff output also goes to stdout, so the user can see
+what changes were made.
 
 =head1 EXIT STATUS
 
@@ -105,10 +106,6 @@ files occur, the exit status will be the error count.
 
 =head1 BUGS
 
-Misspelled key names (e.g. MD5USM or DOWNLAOD) will be discarded. Not
-a true bug (it's by design), but it violates the principle of least
-surprise a bit.
-
 B<sbofixinfo> can't automatically fix every issue B<sbolint> reports.
 In particular, missing or extra values (for valid keys) can't
 automatically be fixed. This isn't really a bug, as B<sbofixinfo>
@@ -154,6 +151,7 @@ for($arg0) {
 		exec("pod2man --stderr -s1 -csbo-maintainer-tools -r$VERSION $0") ||
 			die "$SELF: can't exec pod2man\n";
 	};
+	# undocumented option:
 	/^--keytest/ && do {
 		while(<STDIN>) {
 			chomp;