X-Git-Url: https://git.proxmox.com/?a=blobdiff_plain;f=pveum.adoc;h=00f260ad6e6ad2e7057dca2f104720161951434e;hb=612417fdcf58572fd4e15ba7f8555446970565df;hp=2f3584a21017005f6d4b07657e8ed076911c9499;hpb=0abc65b04f6a78333e60c0d84f1b153ba98f7ed6;p=pve-docs.git

diff --git a/pveum.adoc b/pveum.adoc
index 2f3584a..00f260a 100644
--- 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.