[pmg-devel] [PATCH pmg-docs 3/3] fix #2098 and a typo

Stoiko Ivanov s.ivanov at proxmox.com
Wed Feb 27 17:30:01 CET 2019

The phrasing regarding copying the templates from '/var/lib/pmg/templates'
to '/etc/pmg/templates' caused some confusion [0] and some users thought they
need to copy all templates to '/etc/pmg/templates', even if they only modified
one template. Rephrasing the sentence to speak of a singular template, should
explain the workings better.

Additionally a singular/plural typo was fixed

[0] https://bugzilla.proxmox.com/show_bug.cgi?id=2098 and a few forum-threads

Signed-off-by: Stoiko Ivanov <s.ivanov at proxmox.com>
 pmgconfig.adoc | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/pmgconfig.adoc b/pmgconfig.adoc
index f12b258..3fb0e23 100644
--- a/pmgconfig.adoc
+++ b/pmgconfig.adoc
@@ -143,8 +143,8 @@ We use a template based approach to generate those files. The {tts} is
 a well known, fast and flexible template processing system. You can
 find the default templates in `/var/lib/pmg/templates/`. Please do not
 modify them directly, because your modification would get lost on the
-next update. Instead, copy them to `/etc/pmg/templates/`, then apply
-your changes there.
+next update. Instead, copy the template you wish to change to
+`/etc/pmg/templates/`, then apply your changes there.
 Templates can access any configuration setting, and you can use the
 `pmgconfig dump` command to get a list of all variable names:
@@ -167,7 +167,7 @@ or when you directly edit configuration files
 # pmgconfig sync --restart 1
-Above commands also restarts services if underlying configuration
+The above command also restarts services if the underlying configuration
 files are changed. Please note that this is automatically done when
 you change the configuration using the GUI or API.

More information about the pmg-devel mailing list