Fix CI issues

Author: mbaluda

c/cert/src/rules/SIG30-C/CallOnlyAsyncSafeFunctionsWithinSignalHandlers.md

@@ -5,7 +5,6 @@ This query implements the CERT-C rule SIG30-C:
 > Call only asynchronous-safe functions within signal handlers
 
 
-
 ## Description
 
 Call only [asynchronous-safe functions](https://wiki.sei.cmu.edu/confluence/display/c/BB.+Definitions#BB.Definitions-asynchronous-safefunction) within signal handlers. For [strictly conforming](https://wiki.sei.cmu.edu/confluence/display/c/BB.+Definitions#BB.Definitions-strictlyconforming) programs, only the C standard library functions `abort()`, `_Exit()`, `quick_exit()`, and `signal()` can be safely called from within a signal handler.

c/cert/src/rules/SIG31-C/DoNotAccessSharedObjectsInSignalHandlers.md

@@ -5,7 +5,6 @@ This query implements the CERT-C rule SIG31-C:
 > Do not access shared objects in signal handlers
 
 
-
 ## Description
 
 Accessing or modifying shared objects in signal handlers can result in race conditions that can leave data in an inconsistent state. The two exceptions (C Standard, 5.1.2.3, paragraph 5) to this rule are the ability to read from and write to lock-free atomic objects and variables of type `volatile sig_atomic_t`. Accessing any other type of object from a signal handler is [undefined behavior](https://wiki.sei.cmu.edu/confluence/display/c/BB.+Definitions#BB.Definitions-undefinedbehavior). (See [undefined behavior 131](https://wiki.sei.cmu.edu/confluence/display/c/CC.+Undefined+Behavior#CC.UndefinedBehavior-ub_131).)

c/cert/src/rules/SIG34-C/DoNotCallSignalFromInterruptibleSignalHandlers.md

@@ -5,7 +5,6 @@ This query implements the CERT-C rule SIG34-C:
 > Do not call signal() from within interruptible signal handlers
 
 
-
 ## Description
 
 A signal handler should not reassert its desire to handle its own signal. This is often done on *nonpersistent* platforms—that is, platforms that, upon receiving a signal, reset the handler for the signal to SIG_DFL before calling the bound signal handler. Calling` signal()` under these conditions presents a race condition. (See [SIG01-C. Understand implementation-specific details regarding signal handler persistence](https://wiki.sei.cmu.edu/confluence/display/c/SIG01-C.+Understand+implementation-specific+details+regarding+signal+handler+persistence).)