diff --git a/README.md b/README.md
index 5e8f84ed..e384b750 100644
--- a/README.md
+++ b/README.md
@@ -1,6 +1,6 @@
 # L4SBOA: TeleHealth Over L4S
 
-**L4SBOA** (pronounced [Lisboa](https://pt.wikipedia.org/wiki/Lisboa)) is an L4S-based experimental network framework. We use L4SBOA as a prototype for further network optimization developments in practice for various telehealth applications – sending DICOM images for diagnostics (high volume of data but tolerance for high latency), telemonitoring via wearable devices (low volume of data but demand for low latency), televisits (a video call through apps such as Zoom – high volume of data and demand for high latency). As a result of this project, we will understand whether we need any optimizations for L4S to use for telehealth applications and potential alternative approaches. 
+**L4SBOA** (pronounced [Lisboa](https://pt.wikipedia.org/wiki/Lisboa)) is an L4S-based experimental network framework. We use L4SBOA as a prototype for network optimization developments in practice for various telehealth applications – sending DICOM images for diagnostics (high volume of data but tolerance for high latency), telemonitoring via wearable devices (low volume of data but demand for low latency), televisits (a video call through apps such as Zoom – high volume of data and demand for high latency). As a result of this project, we will understand whether we need any optimizations for L4S to use for telehealth applications and potential alternative approaches. 
 
 Low Latency, Low Loss, and Scalable Throughput (L4S) Internet Service [1](https://datatracker.ietf.org/doc/rfc9330/), [2](http://www.watersprings.org/pub/id/draft-ietf-tsvwg-l4s-arch-06.html), [3](http://www.ring.gr.jp/archives/doc/RFC/rfc9330.pdf) has shown promising performance, by rethinking congestion control. Can we have a telehealth deployment with pairs of L4S nodes? Perhaps starting with something simple, such as two DICOM endpoints to send radiographic images in between? [Linux kernel with L4S patches](https://github.com/L4STeam/linux) can be a good point to start for the endpoints. How L4S, with telehealth and other applications, as well as classic non-L4S traffic, share the network will be an interesting test.