followup: storage config description

From
https://pve.proxmox.com/pipermail/pve-devel/2019-September/038727.html

Suggested-by: Stefan Reiter <s.reiter@proxmox.com>
Signed-off-by: Thomas Lamprecht <t.lamprecht@proxmox.com>

diff --git a/pvesm.adoc b/pvesm.adoc
index c2be9fedb58de28e66455bf40cc7e1cc079181ed..5340c3dc5395120012fa0e3d5113d5063303615f 100644 (file)
--- a/pvesm.adoc
+++ b/pvesm.adoc
@@ -139,12 +139,13 @@ Each storage pool has a `<type>`, and is uniquely identified by its
 <type>: <STORAGE_ID>
        <property> <value>
        <property> <value>
 <type>: <STORAGE_ID>
        <property> <value>
        <property> <value>

+       <property>

        ...
 ----
 
 The `<type>: <STORAGE_ID>` line starts the pool definition, which is then
        ...
 ----
 
 The `<type>: <STORAGE_ID>` line starts the pool definition, which is then

-followed by a list of properties. Most properties have values and some of
-them come with a reasonable default. In that case you can omit the value.
+followed by a list of properties. Most properties require a value. Some have
+reasonable defaults, in which case you can omit the value.

 
 To be more specific, take a look at the default storage configuration
 after installation. It contains one special local storage pool named
 
 To be more specific, take a look at the default storage configuration
 after installation. It contains one special local storage pool named