Apply suggestions from code review

Co-authored-by: Arpad Borsos <[email protected]>

Author: leops

sentry-tracing/src/layer.rs

@@ -219,9 +219,9 @@ impl<S> SentryLayer<S> {
         self
     }
 
-    /// Sets a custom span on_close hook.
+    /// Sets a custom span `on_close` hook.
     ///
-    /// The hook is called with [`Timings`] informations when a [`tracing::Span`]
+    /// The hook is called with [`Timings`] information when a [`tracing::Span`]
     /// is closed, and can mutate the associated [`protocol::Span`] accordingly.
     pub fn span_on_close<F>(mut self, on_close: F) -> Self
     where

sentry-tracing/src/lib.rs

@@ -5,7 +5,7 @@
 //! as breadcrumbs for later. Secondly, error events can be captured as events
 //! to Sentry. Finally, spans can be recorded as structured transaction events.
 //! By default, events above `Info` are recorded as breadcrumbs, events above
-//! `Error` are captured as error events, and spans above `Info` and recorded
+//! `Error` are captured as error events, and spans above `Info` are recorded
 //! as transactions.
 //!
 //! By using this crate in combination with `tracing-subscriber` and its `log`