Update index.mdx

lcian · web-flow · commit c1347dfeb992 · 2025-10-07T12:07:35.000+02:00
diff --git a/docs/platforms/rust/guides/tracing/index.mdx b/docs/platforms/rust/guides/tracing/index.mdx
@@ -88,9 +88,9 @@ async fn fail() {
 }
 ```
 
-By default, error level events from `tokio-rs/tracing` are captured as Sentry events, while anything at or above info level is added as a breadcrumb.
+By default, error level events from `tracing` are captured as Sentry events, while anything at or above info level is added as a breadcrumb.
 
-Additionally, if the `logs` feature flag of the `sentry` crate is enabled and the SDK is initialized with `enable_logs: true`, then events from `tokio-rs/tracing` at info level or above are also captured as [structured logs](https://docs.sentry.io/product/explore/logs/).
+Additionally, if the `logs` feature flag of the `sentry` crate is enabled and the SDK is initialized with `enable_logs: true`, then events from `tracing` at info level or above are also captured as [structured logs](https://docs.sentry.io/product/explore/logs/).
 
 This behavior can be customized by applying a custom `event_filter` when creating the layer.
 The following snippet shows the default `event_filter` that's applied when using the `sentry` crate with the `logs` feature flag.

Original file line number	Diff line number	Diff line change
`@@ -88,9 +88,9 @@ async fn fail() {`
`88`	`88`	`}`
`89`	`89`	```
`90`	`90`
`91`		-By default, error level events from `tokio-rs/tracing` are captured as Sentry events, while anything at or above info level is added as a breadcrumb.
	`91`	+By default, error level events from `tracing` are captured as Sentry events, while anything at or above info level is added as a breadcrumb.
`92`	`92`
`93`		-Additionally, if the `logs` feature flag of the `sentry` crate is enabled and the SDK is initialized with `enable_logs: true`, then events from `tokio-rs/tracing` at info level or above are also captured as [structured logs](https://docs.sentry.io/product/explore/logs/).
	`93`	+Additionally, if the `logs` feature flag of the `sentry` crate is enabled and the SDK is initialized with `enable_logs: true`, then events from `tracing` at info level or above are also captured as [structured logs](https://docs.sentry.io/product/explore/logs/).
`94`	`94`
`95`	`95`	This behavior can be customized by applying a custom `event_filter` when creating the layer.
`96`	`96`	The following snippet shows the default `event_filter` that's applied when using the `sentry` crate with the `logs` feature flag.