From e47e17cf66540ef3c1374a59b516b68d92c29807 Mon Sep 17 00:00:00 2001 From: raquel-campuzano Date: Fri, 18 Nov 2016 12:19:01 +0100 Subject: [PATCH] Fix minor typos --- bitnami/suitecrm/README.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/bitnami/suitecrm/README.md b/bitnami/suitecrm/README.md index 041d6f25cc83..e2c9ba725d7d 100644 --- a/bitnami/suitecrm/README.md +++ b/bitnami/suitecrm/README.md @@ -84,13 +84,13 @@ If you remove every container and volume all your data will be lost, and the nex For persistence of the SuiteCRM deployment, the above examples define docker volumes namely `mariadb_data`, `suitecrm_data`, `apache_data` and `php_data`. The SuiteCRM application state will persist as long as these volumes are not removed. -If avoid inadvertent removal of these volumes you can [mount host directories as data volumes](https://docs.docker.com/engine/tutorials/dockervolumes/). Alternatively you can make use of volume plugins to host the volume data. +To avoid inadvertent removal of these volumes you can [mount host directories as data volumes](https://docs.docker.com/engine/tutorials/dockervolumes/). Alternatively you can make use of volume plugins to host the volume data. > **Note!** If you have already started using your application, follow the steps on [backing](#backing-up-your-application) up to pull the data from your running container down to your host. ### Mount host directories as data volumes with Docker Compose -This requires a sightly modification from the `docker-compose.yml` template previously shown: +This requires a minor change to the `docker-compose.yml` template previously shown: ``` version: '2'