diff --git a/README.md b/README.md
index a64d536e..1ef04e54 100644
--- a/README.md
+++ b/README.md
@@ -59,15 +59,15 @@ http://files.froxlor.org/releases/froxlor-latest.tar.gz [MD5](http://files.froxl
 
 http://files.froxlor.org/gentoo/repositories.xml
 
-## Let's encrypt support
+## Let's Encrypt support
 
-This version of Froxlor contains a beta - version of support for [Let's Encrypt](https://letsencrypt.org). This is (as Let's Encrypt is in itself)
-still a test - version and may break your system. The way it currently works is by creating a (sub-)domain with the default system - certificate,
+This version of Froxlor contains a test - version of support for [Let's Encrypt](https://letsencrypt.org). This is (as Let's Encrypt is in itself)
+still a beta - version and may break your system. The way it currently works is by creating a (sub-)domain with the default system - certificate,
 after which the Let's Encrypt cronjob orders the certificate for this (sub-)domain and inserts the certificates in the database. With the next run
 of the default cronjob, the certificates will be updated on the disk and the webserver reloaded.
 
 This has 2 known side-effects at the moment:
-* The ip/port combinations don't work with the Froxlor - integration of Let's Encrypt, since it needs a certificate for the very first creation
+* The basic ip/port combinations don't work with the Froxlor - integration of Let's Encrypt, since it needs a certificate for the very first creation
 * After creating a domain, it will have the default certificate for a short time (by default 5 minutes until the cronjob runs the next time)
 
 It may be possible to fix these issues, but they are not a priority at the moment