docs(check-alignment): grammar/clarify

Author: brettz9

.README/rules/check-indentation.md

@@ -1,9 +1,9 @@
 ### `check-indentation`
 
-Reports invalid padding inside JSDoc block.
+Reports invalid padding inside JSDoc blocks.
 
-Ignores parts enclosed in Markdown's "code block". For example,
-following description is valid:
+Ignores parts enclosed in Markdown "code block"'s. For example,
+the following description is not reported:
 
 ```js
 /**
@@ -25,13 +25,13 @@ This rule has an object option.
 Array of tags (e.g., `['example', 'description']`) whose content will be
 "hidden" from the `check-indentation` rule. Defaults to `['example']`.
 
-By default, whole JSDoc block is checked for invalid padding.
-That would include `@example` blocks too, which would get in the way
+By default, the whole JSDoc block will be checked for invalid padding.
+That would include `@example` blocks too, which can get in the way
 of adding full, readable examples of code without ending up with multiple
 linting issues.
 
-When disabled (by passing `excludeTags: []` option), following code will
-lint *with* padding issue:
+When disabled (by passing `excludeTags: []` option), the following code *will*
+report a padding issue:
 
 ```js
 /**

README.md

@@ -878,10 +878,10 @@ function quux () {
 <a name="eslint-plugin-jsdoc-rules-check-indentation"></a>
 ### <code>check-indentation</code>
 
-Reports invalid padding inside JSDoc block.
+Reports invalid padding inside JSDoc blocks.
 
-Ignores parts enclosed in Markdown's "code block". For example,
-following description is valid:
+Ignores parts enclosed in Markdown "code block"'s. For example,
+the following description is not reported:
 
 ```js
 /**
@@ -905,13 +905,13 @@ This rule has an object option.
 Array of tags (e.g., `['example', 'description']`) whose content will be
 "hidden" from the `check-indentation` rule. Defaults to `['example']`.
 
-By default, whole JSDoc block is checked for invalid padding.
-That would include `@example` blocks too, which would get in the way
+By default, the whole JSDoc block will be checked for invalid padding.
+That would include `@example` blocks too, which can get in the way
 of adding full, readable examples of code without ending up with multiple
 linting issues.
 
-When disabled (by passing `excludeTags: []` option), following code will
-lint *with* padding issue:
+When disabled (by passing `excludeTags: []` option), the following code *will*
+report a padding issue:
 
 ```js
 /**