pvecm: describe new coldstart behaviour

[pve-docs.git] / pveum.adoc

diff --git a/pveum.adoc b/pveum.adoc
index 3f7e789d51b3cb3283ea07920d39f5f72968b2e1..00f260ad6e6ad2e7057dca2f104720161951434e 100644 (file)
--- a/pveum.adoc
+++ b/pveum.adoc
@@ -103,8 +103,8 @@ Objects and Paths
 ~~~~~~~~~~~~~~~~~
 
 Access permissions are assigned to objects, such as a virtual machines
-('/vms/{vmid}') or a storage ('/storage/{storeid}') or a pool of
-resources ('/pool/{poolname}'). We use filesystem like paths to
+('/vms/\{vmid\}') or a storage ('/storage/\{storeid\}') or a pool of
+resources ('/pool/\{poolname\}'). We use filesystem like paths to
 address those objects. Those paths form a natural tree, and
 permissions can be inherited down that hierarchy.
 
@@ -219,7 +219,7 @@ Pools
 ~~~~~
 
 Pools can be used to group a set of virtual machines and data
-stores. You can then simply set permissions on pools ('/pool/{poolid}'),
+stores. You can then simply set permissions on pools ('/pool/\{poolid\}'),
 which are inherited to all pool members. This is a great way simplify
 access control.
 
@@ -329,7 +329,7 @@ are members of group 'customers':
  pveum aclmod /access/realm/pve -user joe@pve -role PVEUserAdmin
  pveum aclmod /access/groups/customers -user joe@pve -role PVEUserAdmin
 
-Note: The user is able to add other users, but only if they are
+NOTE: The user is able to add other users, but only if they are
 members of group 'customers' and within realm 'pve'.
 
 Pools
@@ -355,7 +355,7 @@ Now we create a new user which is a member of that group
 [source,bash]
  pveum useradd developer1@pve -group developers -password
 
-Note: The -password parameter will prompt you for a password
+NOTE: The -password parameter will prompt you for a password
 
 I assume we already created a pool called 'dev-pool' on the GUI. So we can now assign permission to that pool: