Remove the "Crypto Handshake Data" section

It was not adding anything and was misleading

draft-ietf-quic-transport.md

@@ -2946,14 +2946,6 @@ needing acknowledgement are received.  The sender can use the receiver's
 Strategies and implications of the frequency of generating acknowledgments are
 discussed in more detail in {{QUIC-RECOVERY}}.
 
-### Crypto Handshake Data
-
-In order to quickly complete the handshake and avoid spurious retransmissions
-due to crypto retransmission timeouts, crypto packets SHOULD use a very short
-ack delay, such as the local timer granularity.  ACK frames SHOULD be sent
-immediately when the crypto stack indicates all data for that packet number
-space has been received.
-
 ### ACK Ranges
 
 When an ACK frame is sent, one or more ranges of acknowledged packets are