From 0b1b6700fc05f02b9310d4f7cf48d91c88fde5f7 Mon Sep 17 00:00:00 2001 From: Pedro Navarro Date: Sun, 20 Nov 2016 09:07:03 -0800 Subject: [PATCH] Fixed typo (#1465) --- source/getting-started/installation-virtualenv.markdown | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/getting-started/installation-virtualenv.markdown b/source/getting-started/installation-virtualenv.markdown index b956ef18ee7..4971b6f7197 100644 --- a/source/getting-started/installation-virtualenv.markdown +++ b/source/getting-started/installation-virtualenv.markdown @@ -87,7 +87,7 @@ And that's it... you now have Home Assistant installed, and you can be sure that ### {% linkable_title Finally... Run Home Assistant %} -There are two ways to launch Home Assistant. If you are **in** the virtualenv, you can just run `hass` and it will work as normal. If the virtualenv is not activated, you just use the `hass` executable in the `bin` directory mentioned earlier. There is one caveat... Because Home Assistant stores it's configuration in the user's home directory, we need to be the user `hass` user or specify the configuration with `-c`. +There are two ways to launch Home Assistant. If you are **in** the virtualenv, you can just run `hass` and it will work as normal. If the virtualenv is not activated, you just use the `hass` executable in the `bin` directory mentioned earlier. There is one caveat... Because Home Assistant stores its configuration in the user's home directory, we need to be the user `hass` user or specify the configuration with `-c`. ```bash $ sudo -u hass -H /srv/hass/bin/hass