misc: Fix spelling issues

Misspellings were identified by:
  https://github.com/marketplace/actions/check-spelling

* Initial corrections based on forbidden patterns from the action
* Additional corrections by Google Chrome auto-suggest
* Some manual corrections
* Adding markdown bullets to readme credits section

Signed-off-by: Josh Soref <2119212+jsoref@users.noreply.github.com>

virtio-devices/src/block.rs

@@ -247,7 +247,7 @@ impl BlockEpollHandler {
     #[inline]
     fn find_inflight_request(&mut self, completed_head: u16) -> Result<Request> {
         // This loop neatly handles the fast path where the completions are
-        // in order (it turng into just a pop_front()) and the 1% of the time
+        // in order (it turns into just a pop_front()) and the 1% of the time
         // (analysis during boot) where slight out of ordering has been
         // observed e.g.
         // Submissions: 1 2 3 4 5 6 7

virtio-devices/src/vsock/mod.rs

@@ -126,7 +126,7 @@ pub trait VsockEpollListener {
     /// Get the set of events for which the listener wants to be notified.
     fn get_polled_evset(&self) -> epoll::Events;
 
-    /// Notify the listener that one ore more events have occurred.
+    /// Notify the listener that one or more events have occurred.
     fn notify(&mut self, evset: epoll::Events);
 }
 

virtio-devices/src/vsock/packet.rs

@@ -141,7 +141,7 @@ impl VsockPacket {
             buf_size: 0,
         };
 
-        // No point looking for a data/buffer descriptor, if the packet is zero-lengthed.
+        // No point looking for a data/buffer descriptor, if the packet is zero-length.
         if pkt.is_empty() {
             return Ok(pkt);
         }

virtio-devices/src/vsock/unix/muxer.rs

@@ -32,7 +32,7 @@
 //!    `VsockConnection`.
 //!
 //! The muxer gets notified about all of these events, because, as a `VsockEpollListener`
-//! implementor, it gets to register a nested epoll FD into the main VMM epolling loop. All
+//! implementor, it gets to register a nested epoll FD into the main VMM epoll()ing loop. All
 //! other pollable FDs are then registered under this nested epoll FD.
 //!
 //! To route all these events to their handlers, the muxer uses another `HashMap` object,