cleanup

Author: JoshuaMoelans

docs/platforms/native/advanced-usage/signal-handling/index.mdx

@@ -12,7 +12,7 @@ This document provides guidance on signal handling in the Native SDK. If you'd l
 * The [Signal (IPC) Wikipedia article](https://en.wikipedia.org/wiki/Signal_(IPC)) provides an overview of signals and describes many POSIX signals.
 * The [glibc-docs](https://www.gnu.org/software/libc/manual/html_node/Signal-Handling.html) and [the man pages](https://man7.org/linux/man-pages/man7/signal.7.html) offer reference details for the signal vocabulary.
 * If you want a book-length treatment, we recommend chapters 20-22 of Michael Kerrisk's [The Linux Programming Interface](https://man7.org/tlpi/).
- 
+
 ## Signal Handling Conflicts
 
 Sentry's Native SDK comes with its own set of signal handlers. There may be conflicts if your application currently installs handlers for any [signals of interest](#signals-of-interest) (listed below) that can result in a crash. To avoid this, do the following:
@@ -38,15 +38,15 @@ If you use the `crashpad` backend, in addition to the above, on Linux, you will
 * `SIGSYS`: The kernel received a system call with an invalid argument.
 * `SIGEMT`: An emulator trap occurred.
 * `SIGXCPU`: The process exceeded a previously specified CPU [rlimit](https://pubs.opengroup.org/onlinepubs/9699919799/functions/getrlimit.html).
-* `SIGXFSZ`: Raised when a process grows a file beyond a maximum allowed size ([`RLIMIT_FSIZE`](https://man7.org/linux/man-pages/man2/getrlimit.2.html)). 
+* `SIGXFSZ`: Raised when a process grows a file beyond a maximum allowed size ([`RLIMIT_FSIZE`](https://man7.org/linux/man-pages/man2/getrlimit.2.html)).
 
 ## What to Consider When Writing `on_crash` Hooks
 
 The callback that you register as an `on_crash` hook runs in the context of a signal handler. (`before_send` also runs in the context of a signal handler, unless you turned it off for crashes.)
 
-Since signal handlers can interrupt the running process (and even each other) at any time, take special care when writing them. 
+Since signal handlers can interrupt the running process (and even each other) at any time, take special care when writing them.
 
-Our developer documentation provides [guidelines for writing signal handlers](https://develop.sentry.dev/sdk/signal-handlers/). If you run on Linux or Android, these guidelines also apply to hooks. Signal handlers are notoriously difficult to work with, so it is crucial to follow these guidelines in order to avoid causing severe faults (like crashes and deadlocks), which can prevent terminating programs and sending reports.```
+Our developer documentation provides [guidelines for writing signal handlers](https://develop.sentry.dev/sdk/signal-handlers/). If you run on Linux or Android, these guidelines also apply to hooks. Signal handlers are notoriously difficult to work with, so it is crucial to follow these guidelines in order to avoid causing severe faults (like crashes and deadlocks), which can prevent terminating programs and sending reports.
 
 ## Stack Size in the Signal Handler