about summary refs log tree commit diff
diff options
context:
space:
mode:
authorBenjamin Herr <git@1d6.org>2022-06-10 20:53:49 -0700
committerBenjamin Herr <git@1d6.org>2022-06-10 20:58:27 -0700
commit74ef14830f659c4865448a1a5b5aa75cd78b61fe (patch)
treee5ff494543bf8e669836bc54dfbada840f7bb1e4
parentb9f3bdf5ce37c50c71dd7cee969a14e15f14130a (diff)
downloadrust-74ef14830f659c4865448a1a5b5aa75cd78b61fe.tar.gz
rust-74ef14830f659c4865448a1a5b5aa75cd78b61fe.zip
Fix typos in Provider API docs
-rw-r--r--library/core/src/any.rs4
1 files changed, 2 insertions, 2 deletions
diff --git a/library/core/src/any.rs b/library/core/src/any.rs
index 5eda860264c..866419ac34b 100644
--- a/library/core/src/any.rs
+++ b/library/core/src/any.rs
@@ -94,7 +94,7 @@
 //! functions for requesting data from an object which implements `Provider`. Generally, end users
 //! should not call `request_*` directly, they are helper functions for intermediate implementers
 //! to use to implement a user-facing interface. This is purely for the sake of ergonomics, there is
-//! safety concern here; intermediate implementers can typically support methods rather than
+//! no safety concern here; intermediate implementers can typically support methods rather than
 //! free functions and use more specific names.
 //!
 //! Typically, a data provider is a trait object of a trait which extends `Provider`. A user will
@@ -1007,7 +1007,7 @@ mod tags {
         type Reified = T;
     }
 
-    /// Type-based tag similar to [`Value`] but which may be unsized (i.e., has a `'Sized` bound).
+    /// Type-based tag similar to [`Value`] but which may be unsized (i.e., has a `?Sized` bound).
     #[derive(Debug)]
     pub struct MaybeSizedValue<T: ?Sized + 'static>(PhantomData<T>);