[taler-deployment] branch master updated: readme

[gnunet]

This is an automated email from the git hooks/post-receive script.

ms pushed a commit to branch master
in repository deployment.

The following commit(s) were added to refs/heads/master by this push:
     new 2fa0f0f  readme
2fa0f0f is described below

commit 2fa0f0f27910066d824aaa97502760a8ca3203cc
Author: MS <ms@taler.net>
AuthorDate: Wed Oct 19 22:57:11 2022 +0200

    readme
---
 docker/hybrid/README | 12 ++++++------
 1 file changed, 6 insertions(+), 6 deletions(-)

diff --git a/docker/hybrid/README b/docker/hybrid/README
index ba79e9a..52adb18 100644
--- a/docker/hybrid/README
+++ b/docker/hybrid/README
@@ -51,16 +51,16 @@ Volumes
 -------
 
 The environment variable TALER_DEPLOYMENT_DATA controls
-where on the host's filesystem the services' data gets stored.
+where on the host's filesystem the services store data.
 It defaults to ~/taler-data, and contains exchange, libeufin,
 and postgresql data.
 
 The environment variable TALER_DEPLOYMENT_LOGS controls
-where on the host's filesystem the logs get stored.  It defaults
-to ~/taler-logs and will be created by Docker - owned by "root:root" -
-if it's not found.  NOTE: the 'postgres' user (uid=999) needs
-write access to TALER_DEPLOYMENT_LOGS, in order to log from
-the database container.
+where on the host's filesystem the services store log files.
+It defaults to ~/taler-logs and will be created by Docker -
+owned by "root:root" - if it's not found.  NOTE: the 'postgres'
+user (uid=999) needs write access to TALER_DEPLOYMENT_LOGS,
+in order to log from the database container.
 
 Run
 ---

-- 
To stop receiving notification emails like this one, please contact
gnunet@gnunet.org.