From 75a8838dd81cfa660015ece9372f8c4692f93d42 Mon Sep 17 00:00:00 2001 From: Gregory Colpart Date: Thu, 9 Aug 2018 08:30:29 +0200 Subject: [PATCH] typo --- INSTALL.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/INSTALL.md b/INSTALL.md index 81ad753..b550b54 100644 --- a/INSTALL.md +++ b/INSTALL.md @@ -110,4 +110,4 @@ You can use the `script/to_staging` and/or `script/to_production` scripts. * with `to_staging` you deploy the current commit to the staging server ; * with `to_production` you deploy the `master` branch to production. -On the remote servers – where the application will be deployed – you have to copy the configuration files just as yoiu've just did for your development setup. The files has to go in the `shared/config/` directory, relative to your `deploy_to` path. They will be symlinked to the proper destination by Capistrano. +On the remote servers – where the application will be deployed – you have to copy the configuration files just as you've just did for your development setup. The files has to go in the `shared/config/` directory, relative to your `deploy_to` path. They will be symlinked to the proper destination by Capistrano.