@@ -531,9 +531,9 @@ impl SCB {
531
531
///
532
532
/// After invalidating, the next read of invalidated data will be from main memory. This may
533
533
/// cause recent writes to be lost, potentially including writes that initialized objects.
534
- /// Therefore, this method may cause uninitialised memory or invalid values to be read,
534
+ /// Therefore, this method may cause uninitialized memory or invalid values to be read,
535
535
/// resulting in undefined behaviour. You must ensure that main memory contains valid and
536
- /// initialised values before invalidating.
536
+ /// initialized values before invalidating.
537
537
///
538
538
/// `addr` **must** be aligned to the size of the cache lines, and `size` **must** be a
539
539
/// multiple of the cache line size, otherwise this function will invalidate other memory,
@@ -598,10 +598,10 @@ impl SCB {
598
598
/// # Safety
599
599
///
600
600
/// After invalidating, `obj` will be read from main memory on next access. This may cause
601
- /// recent writes to `obj` to be lost, potentially including the write that initialised it.
602
- /// Therefore, this method may cause uninitialised memory or invalid values to be read,
601
+ /// recent writes to `obj` to be lost, potentially including the write that initialized it.
602
+ /// Therefore, this method may cause uninitialized memory or invalid values to be read,
603
603
/// resulting in undefined behaviour. You must ensure that main memory contains a valid and
604
- /// initialised value for T before invalidating `obj`.
604
+ /// initialized value for T before invalidating `obj`.
605
605
///
606
606
/// `obj` **must** be aligned to the size of the cache lines, and its size **must** be a
607
607
/// multiple of the cache line size, otherwise this function will invalidate other memory,
@@ -636,10 +636,10 @@ impl SCB {
636
636
/// # Safety
637
637
///
638
638
/// After invalidating, `slice` will be read from main memory on next access. This may cause
639
- /// recent writes to `slice` to be lost, potentially including the write that initialised it.
640
- /// Therefore, this method may cause uninitialised memory or invalid values to be read,
639
+ /// recent writes to `slice` to be lost, potentially including the write that initialized it.
640
+ /// Therefore, this method may cause uninitialized memory or invalid values to be read,
641
641
/// resulting in undefined behaviour. You must ensure that main memory contains valid and
642
- /// initialised values for T before invalidating `slice`.
642
+ /// initialized values for T before invalidating `slice`.
643
643
///
644
644
/// `slice` **must** be aligned to the size of the cache lines, and its size **must** be a
645
645
/// multiple of the cache line size, otherwise this function will invalidate other memory,
0 commit comments