remove second layer of 'for instance'

draft-ietf-quic-transport.md

@@ -681,13 +681,13 @@ exists to handle the case where state is lost, so this approach is suboptimal.
 A single static key can be used across all connections to the same endpoint by
 generating the proof using a second iteration of a preimage-resistant function
 that takes three inputs: the static key, a the connection ID for the connection
-(see {{connection-id}}), and an identifier for the server instance.  For
-instance, this could use HMAC {{?RFC2104}} (for example, HMAC(static_key,
-server_id || connection_id)), HKDF {{?RFC5869}} (for example, using the static
-key as input keying material, with server and connection identifiers as salt).
-The output of this function is truncated to 16 octets to produce a valid proof,
-then hashed again to produce the Public Reset Verifier, which is included in the
-transport parameters.
+(see {{connection-id}}), and an identifier for the server instance.  A server
+could use HMAC {{?RFC2104}} (for example, HMAC(static_key, server_id ||
+connection_id)) or HKDF {{?RFC5869}} (for example, using the static key as input
+keying material, with server and connection identifiers as salt).  The output of
+this function is truncated to 16 octets to produce a valid proof, then hashed
+again to produce the Public Reset Verifier, which is included in the transport
+parameters.
 
 A server that loses state and is forced to generate a Public Reset can use the
 same method to generate a valid Public Reset Proof.  The connection ID comes