Add links and fix style

Author: armano2

docs/rules/no-confusing-v-for-v-if.md

@@ -2,12 +2,6 @@
 
 - :warning: This rule was **deprecated** and replaced by [vue/no-use-v-if-with-v-for](no-use-v-if-with-v-for.md) rule.
 
-> When they exist on the same node, `v-for` has a higher priority than `v-if`. That means the `v-if` will be run on each iteration of the loop separately.
->
-> https://vuejs.org/v2/guide/list.html#v-for-with-v-if
-
-So when they exist on the same node, `v-if` directive should use the reference which is to the variables which are defined by the `v-for` directives.
-
 ## :book: Rule Details
 
 This rule reports the elements which have both `v-for` and `v-if` directives in the following cases:
@@ -42,6 +36,12 @@ In that case, the `v-if` should be written on the wrapper element.
 ```
 </eslint-code-block>
 
+::: warning Note
+When they exist on the same node, `v-for` has a higher priority than `v-if`. That means the `v-if` will be run on each iteration of the loop separately.
+
+[https://vuejs.org/v2/guide/list.html#v-for-with-v-if](https://vuejs.org/v2/guide/list.html#v-for-with-v-if)
+:::
+
 ## :wrench: Options
 
 Nothing.

docs/rules/no-v-html.md

@@ -2,11 +2,9 @@
 
 - :gear: This rule is included in `"plugin:vue/recommended"`.
 
-This rule reports use of `v-html` directive in order to reduce the risk of injecting potentially unsafe / unescaped html into the browser leading to Cross-Site Scripting (XSS) attacks.
-
 ## :book: Rule Details
 
-This rule reports all uses of `v-html` to help prevent XSS attacks.
+This rule reports all uses of `v-html` directive in order to reduce the risk of injecting potentially unsafe / unescaped html into the browser leading to Cross-Site Scripting (XSS) attacks.
 
 <eslint-code-block :rules="{'vue/no-v-html': ['error']}">
 ```
@@ -20,15 +18,15 @@ This rule reports all uses of `v-html` to help prevent XSS attacks.
 ```
 </eslint-code-block>
 
-This rule does not check syntax errors in directives because it's checked by no-parsing-error rule.
+This rule does not check syntax errors in directives because it's checked by [vue/no-parsing-error](./no-parsing-error.md) rule.
 
 ## :wrench: Options
 
 Nothing.
 
 ## :mute: When Not To Use It
 
-If you are certain the content passed `to v-html` is sanitized HTML you can disable this rule.
+If you are certain the content passed to `v-html` is sanitized HTML you can disable this rule.
 
 ## :books: Further reading
 

docs/rules/prop-name-casing.md

@@ -3,11 +3,9 @@
 - :gear: This rule is included in `"plugin:vue/strongly-recommended"` and `"plugin:vue/recommended"`.
 - :wrench: The `--fix` option on the [command line](https://eslint.org/docs/user-guide/command-line-interface#fixing-problems) can automatically fix some of the problems reported by this rule.
 
-This rule would enforce proper casing of props in vue components(camelCase).
-
 ## :book: Rule Details
 
-(https://vuejs.org/v2/style-guide/#Prop-name-casing-strongly-recommended).
+This rule enforce proper casing of props in vue components(camelCase).
 
 <eslint-code-block fix :rules="{'vue/prop-name-casing': ['error']}">
 ```