@@ -49,7 +49,7 @@ impl<T: ?Sized> *mut T {
49
49
/// memory.
50
50
///
51
51
/// When calling this method, you have to ensure that if the pointer is
52
- /// non-NULL, then it is properly aligned, dereferencable (for the whole
52
+ /// non-NULL, then it is properly aligned, dereferenceable (for the whole
53
53
/// size of `T`) and points to an initialized instance of `T`. This applies
54
54
/// even if the result of this method is unused!
55
55
/// (The part about being initialized is not yet fully decided, but until
@@ -176,7 +176,7 @@ impl<T: ?Sized> *mut T {
176
176
/// within the same allocated object: [`offset`] is immediate Undefined Behavior when
177
177
/// crossing object boundaries; `wrapping_offset` produces a pointer but still leads
178
178
/// to Undefined Behavior if that pointer is dereferenced. [`offset`] can be optimized
179
- /// better and is thus preferrable in performance-sensitive code.
179
+ /// better and is thus preferable in performance-sensitive code.
180
180
///
181
181
/// If you need to cross object boundaries, cast the pointer to an integer and
182
182
/// do the arithmetic there.
@@ -224,7 +224,7 @@ impl<T: ?Sized> *mut T {
224
224
/// all of the following is true:
225
225
/// - it is properly aligned
226
226
/// - it must point to an initialized instance of T; in particular, the pointer must be
227
- /// "dereferencable " in the sense defined [here].
227
+ /// "dereferenceable " in the sense defined [here].
228
228
///
229
229
/// This applies even if the result of this method is unused!
230
230
/// (The part about being initialized is not yet fully decided, but until
@@ -526,7 +526,7 @@ impl<T: ?Sized> *mut T {
526
526
/// within the same allocated object: [`add`] is immediate Undefined Behavior when
527
527
/// crossing object boundaries; `wrapping_add` produces a pointer but still leads
528
528
/// to Undefined Behavior if that pointer is dereferenced. [`add`] can be optimized
529
- /// better and is thus preferrable in performance-sensitive code.
529
+ /// better and is thus preferable in performance-sensitive code.
530
530
///
531
531
/// If you need to cross object boundaries, cast the pointer to an integer and
532
532
/// do the arithmetic there.
@@ -581,7 +581,7 @@ impl<T: ?Sized> *mut T {
581
581
/// within the same allocated object: [`sub`] is immediate Undefined Behavior when
582
582
/// crossing object boundaries; `wrapping_sub` produces a pointer but still leads
583
583
/// to Undefined Behavior if that pointer is dereferenced. [`sub`] can be optimized
584
- /// better and is thus preferrable in performance-sensitive code.
584
+ /// better and is thus preferable in performance-sensitive code.
585
585
///
586
586
/// If you need to cross object boundaries, cast the pointer to an integer and
587
587
/// do the arithmetic there.
0 commit comments