docs(newline-after-description): option explanation inverted; fixes #…

…397
gajus · Oct 11, 2019 · eb8edca · eb8edca
1 parent 6985ce5
commit eb8edca
Show file tree

Hide file tree

Showing 2 changed files with 2 additions and 2 deletions.
diff --git a/.README/rules/newline-after-description.md b/.README/rules/newline-after-description.md
@@ -4,7 +4,7 @@ Enforces a consistent padding of the block description.
 
 #### Options
 
-This rule allows one optional string argument. If it is `"always"` then a problem is raised when there is a newline after the description. If it is `"never"` then a problem is raised when there is no newline after the description. The default value is `"always"`.
+This rule allows one optional string argument. If it is `"always"` then a problem is raised when there is no newline after the description. If it is `"never"` then a problem is raised when there is a newline after the description. The default value is `"always"`.
 
 |||
 |---|---|

diff --git a/README.md b/README.md
@@ -3396,7 +3396,7 @@ Enforces a consistent padding of the block description.
 <a name="eslint-plugin-jsdoc-rules-newline-after-description-options-5"></a>
 #### Options
 
-This rule allows one optional string argument. If it is `"always"` then a problem is raised when there is a newline after the description. If it is `"never"` then a problem is raised when there is no newline after the description. The default value is `"always"`.
+This rule allows one optional string argument. If it is `"always"` then a problem is raised when there is no newline after the description. If it is `"never"` then a problem is raised when there is a newline after the description. The default value is `"always"`.
 
 |||
 |---|---|