diff --git a/README.md b/README.md
index 7f533e9..3af44b6 100644
--- a/README.md
+++ b/README.md
@@ -127,10 +127,10 @@ If you have seen something very suspicious and/or needs to be investigated/integ
 
 ### Q&As
 
-**Your project seem very cool, does it send data to Kaspersky or any telemetry server?**<br />
-No, at all. You can look to the sources, the only data sent by TinyCheck is an HTTP GET request to a website that you can specify in the config, as well as the watchers URLs. Kaspersky don't - and will not - receive any telemetry from your TinyCheck device.<br /><br />
-**I'm not very confortable with the concept of "watchers" as the IOCs downloaded are public. Do you plan to develop a server to centralize AMBER/RED IOCs?**<br />
-Yes, if the demand is felt by NGOs (contact us!). Is it possible to develop this kind of thing, allowing you to centralize your IOCs and managing your fleet of TinyCheck instances. The server can also embed better detection rules thanks to the telemetry that it will receive.<br />
+**Your project seem very cool, does it send data to Kaspersky or any telemetry server?**<br /><br />
+No, at all. You can look to the sources, the only data sent by TinyCheck is an HTTP GET request to a website that you can specify in the config, as well as the watchers URLs. Kaspersky don't - and will not - receive any telemetry from your TinyCheck device.<br /><br /><br />
+**I'm not very confortable with the concept of "watchers" as the IOCs downloaded are public. Do you plan to develop a server to centralize AMBER/RED IOCs?**<br /><br />
+Yes, if the demand is felt by NGOs (contact us!). Is it possible to develop this kind of thing, allowing you to centralize your IOCs and managing your fleet of TinyCheck instances on a server that you host. The server can also embed better detection rules thanks to the telemetry that it will receive from devices.<br />
 
 ### Possible updates for next releases