diff --git a/README.md b/README.md
index 7ff7660..9ec5030 100644
--- a/README.md
+++ b/README.md
@@ -1,7 +1,7 @@
 
 # Operation Pandora Trigger Commandcenter
 
-A [MEAN Application](http://mean.io/) created for [operation-pandora.com](https://www.operation-pandora.com) Arma3 Community
+A [MEAN Application](http://mean.io/) created for <a href="https://www.operation-pandora.com" target="_blank">operation-pandora.com</a> Arma3 Community
 
 
 ## Installation
@@ -33,22 +33,22 @@ For production setup run the script, described in _Setup for development_, addin
 
         ./docs/opt-cc-environment/3rd-party-install prod
 
-This adds the [`pm2` process manager](http://pm2.keymetrics.io/) to be installed and start the _opt-cc_ server as `pm2` process.
+This adds the <a href="http://pm2.keymetrics.io/" target="_blank">`pm2` process manager</a> to be installed and start the _opt-cc_ server as `pm2` process.
 Run the `sudo` command printed as last output to configure the `pm2` process for automatic start on the system, as the current user.
 
 ## Development
 
+**NOTE:** Do not use the execution described here in any production environment! It will make the running application highly vulnerable.
+
 Before triggering the environment execution run
 
     npm install
 
 inside the main folder, to process all needed npm package installations for the program execution.
 
-Do not use the execution described here in any production environment!
-It will make the running application highly vulnerable. \
 To compile the Angular code and afterwards start the Express server with `nodemon` for development purpose run
 
-   npm run dev
+    npm run dev
 
 Any changes on `api` code will trigger an automatic restart of the Express server.
 
diff --git a/docs/infra/nginx-https-cc-site.txt b/docs/infra/nginx-https-cc-site.txt
index 9e0f743..286668b 100644
--- a/docs/infra/nginx-https-cc-site.txt
+++ b/docs/infra/nginx-https-cc-site.txt
@@ -1,4 +1,3 @@
-
 server {
     listen 80;
     server_name cc.noarch.de;
@@ -9,6 +8,8 @@ server {
     listen 443 ssl;
     server_name cc.noarch.de;
 
+    server_tokens off;
+
     ssl on;
     ssl_certificate /etc/letsencrypt/live/noarch.de/fullchain.pem;
     ssl_certificate_key /etc/letsencrypt/live/noarch.de/privkey.pem;