Could swear I fixed this, which probably means a conflict later

draft-ietf-quic-transport.md

@@ -6375,7 +6375,7 @@ In the case of a cluster that uses dynamic load balancing, it is possible that a
 change in load balancer configuration could occur while an active instance
 retains connection state.  Even if an instance retains connection state, the
 change in routing and resulting stateless reset will result in the connection
-being terminated.  If there is no chance in the packet being routed to the
+being terminated.  If there is no chance of the packet being routed to the
 correct instance, it is better to send a stateless reset than wait for the
 connection to time out.  However, this is acceptable only if the routing cannot
 be influenced by an attacker.