Update docs to reflect removal of letsencrypt email flag

The letsencrypt email parameter is no longer required for inlets HTTP server configuration.

Signed-off-by: Han Verstraete (OpenFaaS Ltd) <han@openfaas.com>

Author: welteki

docs/reference/inletsctl.md

@@ -54,7 +54,6 @@ inletsctl create \
   --region="lon1" \
   --access-token-file $HOME/do-access-token \
   --letsencrypt-domain $DOMAIN \
-  --letsencrypt-email webmaster@$DOMAIN \
   --letsencrypt-issuer prod
 ```
 

docs/tutorial/automated-http-server.md

@@ -36,8 +36,7 @@ inletsctl create \
  --region lon1 \
  --provider digitalocean \
  --access-token-file ~/digital-ocean-api-key.txt \
- --letsencrypt-domain blog.example.com \
- --letsencrypt-email webmaster@example.com
+ --letsencrypt-domain blog.example.com
 ```
 
 A VM will be created in your account using the cheapest plan available, for DigitalOcean this costs 5 USD / mo at time of writing.
@@ -73,8 +72,7 @@ What if I have multiple sites?
 You can pass a number of sub-domains, for instance:
 
 ```bash
- --letsencrypt-domain blog.example.com,grafana.example.com \
- --letsencrypt-email webmaster@example.com
+ --letsencrypt-domain blog.example.com,grafana.example.com
 ```
 
 ## Connect your tunnel client

docs/tutorial/manual-http-server.md

@@ -33,8 +33,7 @@ export DOMAIN="example.com"
   --auto-tls-san 192.168.0.10 \
   --letsencrypt-domain subdomain1.$DOMAIN \
   --letsencrypt-domain subdomain2.$DOMAIN \
-  --letsencrypt-email contact@$DOMAIN \
-  --letsencrypt-issuer staging
+  --letsencrypt-issuer staging \
   --token $TOKEN
 ```