Added information about permissions on data/db

[github/wallabag/wallabag.git] / docs / en / developer / docker.rst

diff --git a/docs/en/developer/docker.rst b/docs/en/developer/docker.rst
index aece29841a94dbd389f49a3bffba525bf295a37b..8816cbcfbdc2cdf395b29e2383bbeadb756f0a93 100644 (file)
--- a/docs/en/developer/docker.rst
+++ b/docs/en/developer/docker.rst
@@ -15,11 +15,11 @@ your system and up to date.
 Switch DBMS
 -----------
 
 Switch DBMS
 -----------
 

-By default, wallabag will start with a sqlite database.
+By default, wallabag will start with a SQLite database.

 Since wallabag provides support for Postgresql and MySQL, docker
 containers are also available for these ones.
 
 Since wallabag provides support for Postgresql and MySQL, docker
 containers are also available for these ones.
 

-In ``docker-compose.yml``, for the chosen DBMS uncomment :
+In ``docker-compose.yml``, for the chosen DBMS uncomment:

 
 - the container definition (``postgres`` or ``mariadb`` root level
   block)
 
 - the container definition (``postgres`` or ``mariadb`` root level
   block)


@@ -27,7 +27,7 @@ In ``docker-compose.yml``, for the chosen DBMS uncomment :
 - the container env file in the ``php`` container
 
 In order to keep running Symfony commands on your host (such as
 - the container env file in the ``php`` container
 
 In order to keep running Symfony commands on your host (such as

-``wallabag:install``), you also should :
+``wallabag:install``), you also should:

 
 - source the proper env files on your command line, so variables
   like ``SYMFONY__ENV__DATABASE_HOST`` will exist.
 
 - source the proper env files on your command line, so variables
   like ``SYMFONY__ENV__DATABASE_HOST`` will exist.