From 0d8ebda347b751a9cd7a6555408520d9245fd7ad Mon Sep 17 00:00:00 2001 From: Keyasha Brothern Date: Tue, 4 Oct 2016 10:15:11 -0500 Subject: [PATCH] Change sentence structure slightly on line 63 (#1102) Changed sentence structure slightly on line 63 from "consider to encrypt your traffic" to "consider encrypting your traffic", flows better by eliminating the word "to" from the sentence. --- source/getting-started/basic.markdown | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/getting-started/basic.markdown b/source/getting-started/basic.markdown index dea9db75ef9..ee9e19dd73a 100644 --- a/source/getting-started/basic.markdown +++ b/source/getting-started/basic.markdown @@ -60,7 +60,7 @@ The common approach is to setup port forwarding from your router to port 8123 on The problem with making a port accessible is that some Internet service providers will only offer dynamic IPs. This can cause you to be unable to access Home Assistant while away. You can solve this by using a free Dynamic DNS service like [DuckDNS](https://www.duckdns.org/). -Just putting a port up is not secure. You should definitely consider to encrypt your traffic if you are accessing your Home Assistant installation from abroad. For details please check the [Set up encryption using Let's Encrypt](/blog/2015/12/13/setup-encryption-using-lets-encrypt/) blog post. +Just putting a port up is not secure. You should definitely consider encrypting your traffic if you are accessing your Home Assistant installation from abroad. For details please check the [Set up encryption using Let's Encrypt](/blog/2015/12/13/setup-encryption-using-lets-encrypt/) blog post. If you want the very best security, check out [the instructions how to use Tor to access your home](/cookbook/tor_configuration/).