@@ -157,7 +157,7 @@ impl OsString {
157
157
/// # Safety
158
158
///
159
159
/// As the encoding is unspecified, callers must pass in bytes that originated as a mixture of
160
- /// validated UTF-8 and bytes from [`OsStr::as_encoded_bytes`] from within the same rust version
160
+ /// validated UTF-8 and bytes from [`OsStr::as_encoded_bytes`] from within the same Rust version
161
161
/// built for the same target platform. For example, reconstructing an `OsString` from bytes sent
162
162
/// over the network or stored in a file will likely violate these safety rules.
163
163
///
@@ -213,7 +213,7 @@ impl OsString {
213
213
/// ASCII.
214
214
///
215
215
/// Note: As the encoding is unspecified, any sub-slice of bytes that is not valid UTF-8 should
216
- /// be treated as opaque and only comparable within the same rust version built for the same
216
+ /// be treated as opaque and only comparable within the same Rust version built for the same
217
217
/// target platform. For example, sending the bytes over the network or storing it in a file
218
218
/// will likely result in incompatible data. See [`OsString`] for more encoding details
219
219
/// and [`std::ffi`] for platform-specific, specified conversions.
@@ -747,7 +747,7 @@ impl OsStr {
747
747
/// # Safety
748
748
///
749
749
/// As the encoding is unspecified, callers must pass in bytes that originated as a mixture of
750
- /// validated UTF-8 and bytes from [`OsStr::as_encoded_bytes`] from within the same rust version
750
+ /// validated UTF-8 and bytes from [`OsStr::as_encoded_bytes`] from within the same Rust version
751
751
/// built for the same target platform. For example, reconstructing an `OsStr` from bytes sent
752
752
/// over the network or stored in a file will likely violate these safety rules.
753
753
///
@@ -955,7 +955,7 @@ impl OsStr {
955
955
/// ASCII.
956
956
///
957
957
/// Note: As the encoding is unspecified, any sub-slice of bytes that is not valid UTF-8 should
958
- /// be treated as opaque and only comparable within the same rust version built for the same
958
+ /// be treated as opaque and only comparable within the same Rust version built for the same
959
959
/// target platform. For example, sending the slice over the network or storing it in a file
960
960
/// will likely result in incompatible byte slices. See [`OsString`] for more encoding details
961
961
/// and [`std::ffi`] for platform-specific, specified conversions.
0 commit comments