Update src/platforms/rust/index.mdx

Co-authored-by: Liza Mock <[email protected]>
getsentry · loewenheim · Aug 28, 2023 · Aug 14, 2023 · Aug 14, 2023 · Aug 16, 2023
commit 0c9995fe64b9da7c755c2dc604e36b7cb56c66b1
diff --git a/src/platforms/rust/index.mdx b/src/platforms/rust/index.mdx
@@ -45,7 +45,7 @@ let _guard = sentry::init(("___PUBLIC_DSN___", sentry::ClientOptions {
 
 **Important:** Note your DSN. The DSN (Data Source Name) tells the SDK where to send events. If you forget it, view Settings -> Projects -> Client Keys (DSN) in sentry.io.
 
-### Async main function
+### Async Main Function
 
 The Sentry client must be initialized before any async runtime is started or threads are spawned. Unfortunately, this makes it impossible to use macros such as `#[tokio::main]` or `#[actix_web::main]`, because they start the runtime first. Thus, instead of
-The Sentry client must be initialized before any async runtime is started or threads are spawned. Unfortunately, this makes it impossible to use macros such as `#[tokio::main]` or `#[actix_web::main]`, because they start the runtime first. Thus, instead of
+The Sentry client must be initialized before any async runtime is started, otherwise threads will be spawned. This means you'll have to avoid using macros such as `#[tokio::main]` or `#[actix_web::main]`, because they start the runtime first. So rather than doing this:
-The Sentry client must be initialized before any async runtime is started or threads are spawned. Unfortunately, this makes it impossible to use macros such as `#[tokio::main]` or `#[actix_web::main]`, because they start the runtime first. Thus, instead of
+The Sentry client must be initialized before any async runtime is started, otherwise threads will be spawned. This means you'll have to avoid using macros such as `#[tokio::main]` or `#[actix_web::main]`, because they start the runtime first. So rather than doing this: