Modify rule S1607: Allow to add an explanation comment after the test…

… disabling (#4243)

Co-authored-by: Ilia Kebets <[email protected]>

rules/S1607/javascript/rule.adoc

@@ -6,7 +6,7 @@ This rule raises an issue when a test construct from Jasmine, Jest, Mocha, or No
 
 == How to fix it in Jasmine
 
-A comment should be added before the line of the unit test explaining why the test was disabled. Alternatively, if the test is no longer relevant, it should be removed entirely.
+A comment should be added before, on, or after the line of the unit test explaining why the test was disabled. Alternatively, if the test is no longer relevant, it should be removed entirely.
 
 === Code examples
 
@@ -35,7 +35,7 @@ describe('foo', function() {
 
 == How to fix it in Jest
 
-A comment should be added before the line of the unit test explaining why the test was disabled. Alternatively, if the test is no longer relevant, it should be removed entirely.
+A comment should be added before, on, or after the line of the unit test explaining why the test was disabled. Alternatively, if the test is no longer relevant, it should be removed entirely.
 
 === Code examples
 
@@ -64,7 +64,7 @@ describe('foo', function() {
 
 == How to fix it in Mocha
 
-A comment should be added before the line of the unit test explaining why the test was disabled. Alternatively, if the test is no longer relevant, it should be removed entirely.
+A comment should be added before, on, or after the line of the unit test explaining why the test was disabled. Alternatively, if the test is no longer relevant, it should be removed entirely.
 
 === Code examples