Fix some typos (#987)

Author: striezel

src/backend/libc/event/epoll.rs

@@ -187,7 +187,7 @@ pub fn add(
     // SAFETY: We're calling `epoll_ctl` via FFI and we know how it
     // behaves. We use our own `Event` struct instead of libc's because
     // ours preserves pointer provenance instead of just using a `u64`,
-    // and we have tests elsehwere for layout equivalence.
+    // and we have tests elsewhere for layout equivalence.
     unsafe {
         let raw_fd = source.as_fd().as_raw_fd();
         ret(c::epoll_ctl(
@@ -219,7 +219,7 @@ pub fn modify(
     // SAFETY: We're calling `epoll_ctl` via FFI and we know how it
     // behaves. We use our own `Event` struct instead of libc's because
     // ours preserves pointer provenance instead of just using a `u64`,
-    // and we have tests elsehwere for layout equivalence.
+    // and we have tests elsewhere for layout equivalence.
     unsafe {
         ret(c::epoll_ctl(
             epoll.as_fd().as_raw_fd(),

src/backend/libc/fs/dir.rs

@@ -131,7 +131,7 @@ impl Dir {
 
     /// `readdir(self)`, where `None` means the end of the directory.
     pub fn read(&mut self) -> Option<io::Result<DirEntry>> {
-        // If we've seen errors, don't continue to try to read anyting further.
+        // If we've seen errors, don't continue to try to read anything further.
         if self.any_errors {
             return None;
         }

src/backend/linux_raw/fs/dir.rs

@@ -81,7 +81,7 @@ impl Dir {
 
     /// `readdir(self)`, where `None` means the end of the directory.
     pub fn read(&mut self) -> Option<io::Result<DirEntry>> {
-        // If we've seen errors, don't continue to try to read anyting further.
+        // If we've seen errors, don't continue to try to read anything further.
         if self.any_errors {
             return None;
         }

src/fs/abs.rs

@@ -182,7 +182,7 @@ pub fn rmdir<P: path::Arg>(path: P) -> io::Result<()> {
 /// POSIX leaves it implementation-defined whether `link` follows a symlink in
 /// `old_path`, or creates a new link to the symbolic link itself. On platforms
 /// which have it, [`linkat`] avoids this problem since it has an [`AtFlags`]
-/// paramter and the [`AtFlags::SYMLINK_FOLLOW`] flag determines whether
+/// parameter and the [`AtFlags::SYMLINK_FOLLOW`] flag determines whether
 /// symlinks should be followed.
 ///
 /// # References

src/fs/at.rs

@@ -139,7 +139,7 @@ fn _readlinkat(dirfd: BorrowedFd<'_>, path: &CStr, mut buffer: Vec<u8>) -> io::R
 /// significantly trickier to use; most users should use plain [`readlinkat`].
 ///
 /// This version writes bytes into the buffer and returns two slices, one
-/// containing the written bytes, and one containint the remaining
+/// containing the written bytes, and one containing the remaining
 /// uninitialized space. If the number of written bytes is equal to the length
 /// of the buffer, it means the buffer wasn't big enough to hold the full
 /// string, and callers should try again with a bigger buffer.

src/process/pidfd_getfd.rs

@@ -40,7 +40,7 @@ bitflags::bitflags! {
 /// returned from `pidfd_getfd`.
 ///
 /// When `pidfd_getfd` is used to debug the target, or the target is not a Rust
-/// aplication, or `pidfd_getfd` is used in any other way, then extra care
+/// application, or `pidfd_getfd` is used in any other way, then extra care
 /// should be taken to avoid unexpected behaviour or crashes.
 ///
 /// For further details, see the references above.

tests/fs/file.rs

@@ -174,7 +174,7 @@ fn test_setfl_append() {
     .unwrap();
     assert_eq!(rustix::io::write(&file, b"abcdefghijklmnop"), Ok(16));
 
-    // Overwite the first few bytes.
+    // Overwrite the first few bytes.
     let file =
         rustix::fs::open(tmp.path().join("test.file"), OFlags::WRONLY, Mode::empty()).unwrap();
     assert_eq!(rustix::io::write(&file, b"uvw"), Ok(3));