fix typos in tracing-subscriber

tracing-subscriber/src/fmt/format/mod.rs

@@ -110,7 +110,7 @@ use fmt::{Debug, Display};
 ///
 /// # Examples
 ///
-/// This example re-implements a simiplified version of this crate's [default
+/// This example re-implements a simplified version of this crate's [default
 /// formatter]:
 ///
 /// ```rust

tracing-subscriber/src/lib.rs

@@ -4,7 +4,7 @@
 //! scoped, structured, and async-aware diagnostics. The [`Collect`] trait
 //! represents the functionality necessary to collect this trace data. This
 //! crate contains tools for composing subscribers out of smaller units of
-//! behaviour, and batteries-included implementations of common subscriber
+//! behavior, and batteries-included implementations of common subscriber
 //! functionality.
 //!
 //! `tracing-subscriber` is intended for use by both `Collector` authors and
@@ -28,7 +28,7 @@
 //!
 //! In addition, the [`Filter`] trait defines an interface for filtering what
 //! spans and events are recorded by a particular subscriber. This allows different
-//! [`Subscribe`] implementationss to handle separate subsets of the trace data
+//! [`Subscribe`] implementations to handle separate subsets of the trace data
 //! emitted by a program. See the [documentation on per-subscriber
 //! filtering][psf] for more information on using [`Filter`]s.
 //!

tracing-subscriber/src/prelude.rs

@@ -3,7 +3,7 @@
 //! This brings into scope a number of extension traits that define methods on
 //! types defined here and in other crates.
 
-// apparently `as _` reexpoorts now generate `unreachable_pub` linting? which
+// apparently `as _` reexports now generate `unreachable_pub` linting? which
 // seems wrong to me...
 #![allow(unreachable_pub)]
 pub use crate::field::{MakeExt as _, RecordFields as _};