@@ -229,7 +229,7 @@ unsafe impl Send for GuestSharedMemory {}
229
229
/// sadly, mostly un-adopted for C++23, although that does not concern
230
230
/// us), the paper did not actually redefine volatile accesses or data
231
231
/// races to prevent volatile accesses from racing with other accesses
232
- /// and causing undefined behaviour. P1382R1 [5] would have amendend
232
+ /// and causing undefined behaviour. P1382R1 [5] would have amended
233
233
/// the wording of the data race definition to specifically exclude
234
234
/// volatile, but, unfortunately, despite receiving a
235
235
/// generally-positive reception at its first WG21 meeting more than
@@ -257,7 +257,7 @@ unsafe impl Send for GuestSharedMemory {}
257
257
/// In short, none of the Rust-level operations available to us do the
258
258
/// right thing, at the Rust spec level or the LLVM spec level. Our
259
259
/// major remaining options are therefore:
260
- /// - Choose one of the options that is avaiblale to us, and accept
260
+ /// - Choose one of the options that is available to us, and accept
261
261
/// that we are doing something unsound according to the spec, but
262
262
/// hope that no reasonable compiler could possibly notice.
263
263
/// - Use inline assembly per architecture, for which we would only
0 commit comments