From b2d41330e0f0636eb35ebfc6fc0eb747519514dc Mon Sep 17 00:00:00 2001 From: Dirk Wetter Date: Thu, 25 Jun 2020 13:05:47 +0200 Subject: [PATCH] port typo fixes to html and roff doc --- doc/testssl.1 | 4 ++-- doc/testssl.1.html | 4 ++-- 2 files changed, 4 insertions(+), 4 deletions(-) diff --git a/doc/testssl.1 b/doc/testssl.1 index 38bbfed..1b7a9f3 100644 --- a/doc/testssl.1 +++ b/doc/testssl.1 @@ -650,10 +650,10 @@ To implement a new grading cap, simply call the \fBset_grade_cap()\fR function, When implementing a new check (be it vulnerability or not) that sets grade caps, the \fBset_rating_state()\fR has to be updated (i\.e\. the \fB$do_mycheck\fR variable\-name has to be added to the loop, and \fB$nr_enabled\fR if\-statement has to be incremented) . .P -The \fBset_rating_state()\fR automatically disables ratinng, if all the required checks are \fInot\fR enabled\. This is to prevent giving out a misleading or wrong grade\. +The \fBset_rating_state()\fR automatically disables rating, if all the required checks are \fInot\fR enabled\. This is to prevent giving out a misleading or wrong grade\. . .P -When a new revision of the rating specification comes around, the following has to be done: * New grade caps has to be either: 1\. Added to the script wherever relevant, or 2\. Added to the above list of missing checks (if \fIi\.\fR is not possible) * New grade warnings has to be added wherever relevant * The revision output in \fBrun_rating()\fR function has to updated +When a new revision of the rating specification comes around, the following has to be done: * New grade caps has to be either: 1\. Added to the script wherever relevant, or 2\. Added to the above list of missing checks (if above is not possible) * New grade warnings has to be added wherever relevant * The revision output in \fBrun_rating()\fR function has to updated . .SH "EXAMPLES" . diff --git a/doc/testssl.1.html b/doc/testssl.1.html index 8290958..38067d1 100644 --- a/doc/testssl.1.html +++ b/doc/testssl.1.html @@ -515,7 +515,7 @@ set_grade_warning "Documentation is always right"

When implementing a new check (be it vulnerability or not) that sets grade caps, the set_rating_state() has to be updated (i.e. the $do_mycheck variable-name has to be added to the loop, and $nr_enabled if-statement has to be incremented)

-

The set_rating_state() automatically disables ratinng, if all the required checks are not enabled. +

The set_rating_state() automatically disables rating, if all the required checks are not enabled. This is to prevent giving out a misleading or wrong grade.

Implementing a new revision

@@ -523,7 +523,7 @@ This is to prevent giving out a misleading or wrong grade.

When a new revision of the rating specification comes around, the following has to be done: * New grade caps has to be either: 1. Added to the script wherever relevant, or - 2. Added to the above list of missing checks (if i. is not possible) + 2. Added to the above list of missing checks (if above is not possible) * New grade warnings has to be added wherever relevant * The revision output in run_rating() function has to updated