Fix a few typos (#169)

README.md

@@ -46,7 +46,7 @@ operations that are 100% safe will be added.
 * The crate is 1.0 and I consider this it to be "basically done". New features
   are usually being accepted when other people want to put in the work, but
   myself I wanna move on to using `bytemuck` in bigger projects.
-* The defatult build of the `bytemuck` crate will continue to work with `rustc-1.34`
+* The default build of the `bytemuck` crate will continue to work with `rustc-1.34`
   for at least the rest of the `1.y.z` versions.
 * Any other cargo features of the crate **are not** held to the same standard, and
   may work only on the latest Stable or even only on latest Nightly.

derive/Cargo.toml

@@ -15,7 +15,7 @@ name = "bytemuck_derive"
 proc-macro = true
 
 [dependencies]
-# syn seems to have broken backwards compability in this version https://github.com/dtolnay/syn/issues/1194
+# syn seems to have broken backwards compatibility in this version https://github.com/dtolnay/syn/issues/1194
 syn = "1.0.99"
 quote = "1"
 proc-macro2 = "1"

derive/changelog.md

@@ -12,7 +12,7 @@
 
 ## 1.2.1
 
-* Fixed a regression of the `align(N)` attribute that occured during otherwise
+* Fixed a regression of the `align(N)` attribute that occurred during otherwise
   routine cleanup.
 
 ## 1.2.0

src/checked.rs

@@ -15,7 +15,7 @@ use crate::{
 /// To do this, we define a `Bits` type which is a type with equivalent layout
 /// to `Self` other than the invalid bit patterns which disallow `Self` from
 /// being [`AnyBitPattern`]. This `Bits` type must itself implement
-/// [`AnyBitPattern`]. Then, we implement a function that checks wheter a
+/// [`AnyBitPattern`]. Then, we implement a function that checks whether a
 /// certain instance of the `Bits` is also a valid bit pattern of `Self`. If
 /// this check passes, then we can allow casting from the `Bits` to `Self` (and
 /// therefore, any type which is able to be cast to `Bits` is also able to be

tests/doc_tests.rs

@@ -103,7 +103,7 @@ fn test_offsetof_nonpod() {
   // Note: offsets are in bytes.
   let as_bytes = &foo as *const _ as *const u8;
 
-  // we're using wrapping_offset here becasue it's not worth
+  // We're using wrapping_offset here because it's not worth
   // the unsafe block, but it would be valid to use `add` instead,
   // as it cannot overflow.
   assert_eq!(