diff --git a/index.html b/index.html
index eb72fec..d92a304 100644
--- a/index.html
+++ b/index.html
@@ -173,10 +173,10 @@ layout: false
 | Protocol | Published | Status |
 | ----------- | ----------- | -------- |
 | SSL 1.0 | Unpublished | Unpublished |
-| SSL 2.0 | 1995 |  Deprecated in 2011 (RFC 6176)  |
+| SSL 2.0 | 1995 |  Deprecated in 2011 (RFC 6176) |
 | SSL 3.0 | 1996 |  Deprecated in 2015 (RFC 7568) |
-| TLS 1.0 | 1999 |  Deprecation planned in 2020 |
-| TLS 1.1 | 2006 |  Deprecation planned in 2020 |
+| TLS 1.0 | 1999 |  Deprecated in 2021 (RFC 8996) |
+| TLS 1.1 | 2006 |  Deprecated in 2021 (RFC 8996) |
 | TLS 1.2 | 2008 | |
 | TLS 1.3 | 2018 | |
 
@@ -263,7 +263,7 @@ show certificate
 So, how does a certificate get signed?
 ]
 
-<img src="document-signing-process.png" width="100%" />
+<img src="document-signing-process.png" width="80%" />
 
 ???
 Or how does this signing work:
@@ -279,7 +279,7 @@ Or how does this signing work:
 Now anyone can verify the signature:
 ]
 
-<img src="document-verify-signature.png" width="100%" />
+<img src="document-verify-signature.png" width="80%" />
 ???
 Now anyone can verify the signature by:
 - decrypting the signature with the CAs public key
@@ -340,6 +340,17 @@ This is where the client and server decide on:
 9.    Secure symmetric encryption achieved: The handshake is completed, and communication continues using the session keys.
 ---
 .left-column[
+## Key exchange, no certificate?
+]
+.right-column[
+This is where the Diffie Hellman key exchange helps
+
+<img src="250px-Diffie-Hellman_Key_Exchange.svg.png" width="50%" />
+
+.footnote[Borrowed from: (https://en.wikipedia.org/wiki/Diffie%E2%80%93Hellman_key_exchange)]
+]
+---
+.left-column[
 ## TLS1.3
 ]
 .right-column[