Update docs/platforms/native/advanced-usage/backend-tradeoffs/index.mdx

Co-authored-by: Karl Heinz Struggl <[email protected]>

Author: supervacuus

docs/platforms/native/advanced-usage/backend-tradeoffs/index.mdx

@@ -51,7 +51,7 @@ Both backends are comparable in how they differ from `crashpad`. However, there
 
 `inproc` is currently the backend of choice for `Android` because it allows us to couple it with our own fork of a powerful platform unwinder `libunwindstack` (rather than relying on a user-space interface). This allows us to support very old Android versions.
 
-`inproc` is the right choice if you want
+`inproc` is the right choice if you
 
 * want minimal dependencies
 * want the smallest footprint for the resulting artifact