Fix rule help format issue

Author: Nikita Kraiouchkine

c/cert/src/rules/INT30-C/UnsignedIntegerOperationsWrapAround.md

@@ -5,7 +5,6 @@ This query implements the CERT-C rule INT30-C:
 > Ensure that unsigned integer operations do not wrap
 
 
-
 ## Description
 
 The C Standard, 6.2.5, paragraph 9 \[[ISO/IEC 9899:2011](https://wiki.sei.cmu.edu/confluence/display/c/AA.+Bibliography#AA.Bibliography-ISO-IEC9899-2011)\], states

c/cert/src/rules/INT31-C/IntegerConversionCausesDataLoss.md

@@ -5,7 +5,6 @@ This query implements the CERT-C rule INT31-C:
 > Ensure that integer conversions do not result in lost or misinterpreted data
 
 
-
 ## Description
 
 Integer conversions, both implicit and explicit (using a cast), must be guaranteed not to result in lost or misinterpreted data. This rule is particularly true for integer values that originate from untrusted sources and are used in any of the following ways:

c/cert/src/rules/INT32-C/SignedIntegerOverflow.md

@@ -5,7 +5,6 @@ This query implements the CERT-C rule INT32-C:
 > Ensure that operations on signed integers do not result in overflow
 
 
-
 ## Description
 
 Signed integer overflow is [undefined behavior 36](https://wiki.sei.cmu.edu/confluence/display/c/BB.+Definitions#BB.Definitions-undefinedbehavior). Consequently, [implementations](https://wiki.sei.cmu.edu/confluence/display/c/BB.+Definitions#BB.Definitions-implementation) have considerable latitude in how they deal with signed integer overflow. (See [MSC15-C. Do not depend on undefined behavior](https://wiki.sei.cmu.edu/confluence/display/c/MSC15-C.+Do+not+depend+on+undefined+behavior).) An implementation that defines signed integer types as being modulo, for example, need not detect integer overflow. Implementations may also trap on signed arithmetic overflows, or simply assume that overflows will never happen and generate object code accordingly. It is also possible for the same conforming implementation to emit code that exhibits different behavior in different contexts. For example, an implementation may determine that a signed integer loop control variable declared in a local scope cannot overflow and may emit efficient code on the basis of that determination, while the same implementation may determine that a global variable used in a similar context will wrap.

c/cert/src/rules/INT33-C/DivOrRemByZero.md

@@ -5,7 +5,6 @@ This query implements the CERT-C rule INT33-C:
 > Ensure that division and remainder operations do not result in divide-by-zero errors
 
 
-
 ## Description
 
 The C Standard identifies the following condition under which division and remainder operations result in [undefined behavior (UB)](https://wiki.sei.cmu.edu/confluence/display/c/BB.+Definitions#BB.Definitions-undefinedbehavior):

c/cert/src/rules/INT35-C/UseCorrectIntegerPrecisions.md

@@ -5,7 +5,6 @@ This query implements the CERT-C rule INT35-C:
 > Use correct integer precisions
 
 
-
 ## Description
 
 Integer types in C have both a *size* and a *precision*. The size indicates the number of bytes used by an object and can be retrieved for any object or type using the `sizeof` operator. The precision of an integer type is the number of bits it uses to represent values, excluding any sign and padding bits.