From 207919908d7aebeac2cdf63c6f18e01814045421 Mon Sep 17 00:00:00 2001
From: Karthikdasari0423 <92445174+Karthikdasari0423@users.noreply.github.com>
Date: Mon, 8 Aug 2022 22:17:44 +0530
Subject: [PATCH] Update README.md

---
 README.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/README.md b/README.md
index de47eec..b3ee410 100644
--- a/README.md
+++ b/README.md
@@ -3,11 +3,11 @@ goquic, QUIC support for Go
 
 [![Docker Repository on Quay](https://quay.io/repository/devsisters/quic-reverse-proxy/status "Docker Repository on Quay")](https://quay.io/repository/devsisters/quic-reverse-proxy)
 
-This is a work-in-progress QUIC implementation for Go. This is based on
+This is a standardised QUIC implementation for Go. This is based on
 [libquic](https://github.com/devsisters/libquic) library, which is in turn based
 on original QUIC implementation on [Chromium](http://www.chromium.org/quic).
 
-QUIC is an experimental protocol aimed at reducing web latency over that of TCP.
+QUIC is an standardised protocol conforming with [RFC 9000](https://datatracker.ietf.org/doc/html/rfc9000) aimed at reducing web latency over that of TCP.
 On the surface, QUIC is very similar to TCP+TLS+SPDY implemented on UDP. Because
 TCP is implement in operating system kernels, and middlebox firmware, making
 significant changes to TCP is next to impossible. However, since QUIC is built