From 2ff7c7f3e8ae3c548f09e12659c569f82930a263 Mon Sep 17 00:00:00 2001
From: jabu <jabu@gx.ag>
Date: Sat, 18 May 2024 04:07:55 -0500
Subject: [PATCH] fmt

---
 src/read_write.rs | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/src/read_write.rs b/src/read_write.rs
index 4ce3a2e..d0bef84 100644
--- a/src/read_write.rs
+++ b/src/read_write.rs
@@ -6,7 +6,7 @@ use crate::{Address, PacketReceived, Socket, SocketOptions};
 ///
 /// This provides a useful alternative to implementing the [`Socket`] trait, especially when
 /// interfacing with multiple kinds of sockets at once.
-/// 
+///
 /// The call to [`Socket::init`] never fails for this type, so it is safe to assume
 /// [`Host::new`](`crate::Host::new`) will not fail with
 /// [`HostNewError::FailedToInitializeSocket`](`crate::error::HostNewError::FailedToInitializeSocket`).