dnsdist: Fix a typo reported by Matt Nordhoff in the TLS sessions guide

diff --git a/pdns/dnsdistdist/docs/guides/tls-sessions-management.rst b/pdns/dnsdistdist/docs/guides/tls-sessions-management.rst
index bc8894eb1ccd7ffc5eebc08123323c81529e5de9..b8d03542e1922d2db82ca04922de570f3f777b5e 100644 (file)
--- a/pdns/dnsdistdist/docs/guides/tls-sessions-management.rst
+++ b/pdns/dnsdistdist/docs/guides/tls-sessions-management.rst
@@ -4,7 +4,7 @@ TLS Sessions Management
 TLS sessions
 ------------
 
-One of the most costly TLS operation if the negotiation of a new session, since both the client and the server need to generate and agree on cryptographic materials. In order to reduce that cost, TLS implements what is called session resumption, where a client opening a new connection to a server can reuse the cryptographic materials negotiated for a previous TLS session.
+One of the most costly TLS operation is the negotiation of a new session, since both the client and the server need to generate and agree on cryptographic materials. In order to reduce that cost, TLS implements what is called session resumption, where a client opening a new connection to a server can reuse the cryptographic materials negotiated for a previous TLS session.
 
 The necessary information to resume a session can either be kept on the server's side (sessions) or on the client's one (tickets). Initially only the server-side approach existed, with two drawbacks:
 - the server needs to keep that information at hand, for a client that might never come back;