final touches

1 files changed, 4 insertions, 3 deletions

diff --git a/template/news/2023-08-GSoC-QUIC.html.j2 b/template/news/2023-08-GSoC-QUIC.html.j2
index 91ca9f18..060d78f9 100644
--- a/template/news/2023-08-GSoC-QUIC.html.j2
+++ b/template/news/2023-08-GSoC-QUIC.html.j2
@@ -7,7 +7,8 @@
 </p>
 <h2>Goals of the Project.</h2>
 <p>
-  The goal of this project was to develop a new transport, QUIC, for the Transport Next Generation (TNG) service.  TNG is a successor to the previous transport plugins and will be running in the fall 2023 GNUnet release. At the time of writing, GNUnet currently supports transports over TCP, UDP, and UNIX sockets. I chose to implement a QUIC transport communicator due to the rising popularity and speed of this protocol. QUIC is intended to be a faster alternative to TCP and tries to address some issues that TLS has.
+  The goal of this project was to develop a new transport, QUIC, for the <a href="https://docs.gnunet.org/developers/transport-ng/transport-ng.html">Transport Next Generation (TNG) service</a>.  TNG is a successor to the previous transport plugins and will be running in the fall 2023 GNUnet release. At the time of writing, GNUnet currently supports transports over TCP, UDP, and UNIX sockets. 
+  I chose to implement a QUIC transport communicator due to the rising popularity and speed of this protocol. Due to the rising popularity, QUIC will be a great transport protocol for GNUnet traffic to sit on top of. QUIC is intended to be a faster alternative to TCP and tries to address some issues that TLS has.
 </p>
 <h2>What I completed.</h2>
 <p>
@@ -20,11 +21,11 @@ Link to source code: <a href="https://git.gnunet.org/gnunet.git/tree/src/transpo
 </p>
 <h2>The current state.</h2>
 <p>
-The QUIC communicator currently functions and passes basic communicator tests. That being said, there are some latency issues that need to be addressed. Mentioned below are some other things that have yet to be implemented, but will be fixed in the future.
+The QUIC communicator currently functions and passes basic communicator tests. That being said, there are some latency issues that need to be addressed. Since the communicator suite is designed to run alongside the new TNG service, it is currently not usable since TNG is still under development (as mentioned previously). Mentioned below are some other things that have yet to be implemented in the QUIC communicator, but will be fixed in the future.
 </p>
 <h2>Future Work.</h2>
 <p>
-We still need to develop a more permanent solution to the certificate generation so that the Quiche API functions properly. Currently, we are using static, example certificates. Adding timers to each connection so that a timeout will trigger a connection to close also needs to be done. Finally, we should look into lowering the latency by finding where the code is too slow and optimizing it.
+We still need to develop a more permanent solution to the certificate generation so that the Quiche API functions properly. This <a href="https://git.gnunet.org/gnunet.git/tree/src/transport/gnunet-transport-certificate-creation.in">certificate generation</a> has been done in previous implementations (for example the HTTPS plugin). Currently, we are using static, example certificates. Adding timers to each QUIC connection so that a timeout will trigger a connection to close also needs to be implemented. Finally, we should look into lowering the latency by finding points where the communicator is too slow and optimizing it.
 </p>
 <h2>Challenges I Encountered.</h2>
 <p>