From f4e1901b156b210d0bee89ba4412117005e427cd Mon Sep 17 00:00:00 2001 From: Simon Hellmayr Date: Wed, 31 Jul 2024 11:39:15 +0200 Subject: [PATCH] fix(docs): grammar in Hub docs --- sentry-core/src/hub.rs | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/sentry-core/src/hub.rs b/sentry-core/src/hub.rs index cc0a9c3d..f5ebf155 100644 --- a/sentry-core/src/hub.rs +++ b/sentry-core/src/hub.rs @@ -8,7 +8,7 @@ use crate::protocol::{Event, Level, SessionStatus}; use crate::types::Uuid; use crate::{Integration, IntoBreadcrumbs, Scope, ScopeGuard}; -/// The central object that can manages scopes and clients. +/// The central object that can manage scopes and clients. /// /// This can be used to capture events and manage the scope. This object is [`Send`] and /// [`Sync`] so it can be used from multiple threads if needed. @@ -16,10 +16,10 @@ use crate::{Integration, IntoBreadcrumbs, Scope, ScopeGuard}; /// Each thread has its own thread-local ( see [`Hub::current`]) hub, which is /// automatically derived from the main hub ([`Hub::main`]). /// -/// In most situations developers do not need to interface with the hub directly. Instead -/// toplevel convenience functions are expose that will automatically dispatch -/// to the thread-local ([`Hub::current`]) hub. In some situations this might not be -/// possible in which case it might become necessary to manually work with the +/// In most situations, developers do not need to interface with the hub directly. Instead +/// toplevel convenience functions are exposed that will automatically dispatch +/// to the thread-local ([`Hub::current`]) hub. In some situations, this might not be +/// possible, in which case it might become necessary to manually work with the /// hub. See the main [`crate`] docs for some common use-cases and pitfalls /// related to parallel, concurrent or async code. ///