Merging upstream version 1.71.1+dfsg1.

Signed-off-by: Daniel Baumann <daniel.baumann@progress-linux.org>

1 files changed, 4 insertions, 4 deletions

diff --git a/vendor/icu_provider/src/key.rs b/vendor/icu_provider/src/key.rs
index d4d6905c9..8c76608fc 100644
--- a/vendor/icu_provider/src/key.rs
+++ b/vendor/icu_provider/src/key.rs
@@ -210,20 +210,20 @@ impl Default for DataKeyMetadata {
 /// Therefore, users should not generally create DataKey instances; they should instead use
 /// the ones exported by a component.
 ///
-/// `DataKey`s are created with the [`data_key!`] macro:
+/// `DataKey`s are created with the [`data_key!`](crate::data_key) macro:
 ///
 /// ```
-/// # use icu_provider::prelude::DataKey;
+/// # use icu_provider::DataKey;
 /// const K: DataKey = icu_provider::data_key!("foo/bar@1");
 /// ```
 ///
 /// The human-readable path string ends with `@` followed by one or more digits (the version
 /// number). Paths do not contain characters other than ASCII letters and digits, `_`, `/`.
 ///
-/// Invalid paths are compile-time errors (as [`data_key!`] uses `const`).
+/// Invalid paths are compile-time errors (as [`data_key!`](crate::data_key) uses `const`).
 ///
 /// ```compile_fail,E0080
-/// # use icu_provider::prelude::DataKey;
+/// # use icu_provider::DataKey;
 /// const K: DataKey = icu_provider::data_key!("foo/../bar@1");
 /// ```
 #[derive(Copy, Clone)]