add pveum_configure_u2f reference

[pve-docs.git] / pveum.adoc

diff --git a/pveum.adoc b/pveum.adoc
index 77f7aecbbc3e7e78dc4f34b5860417b62c6d9eef..3f21078dba66945c5491fa1cd4a19c46746a69cd 100644 (file)
--- a/pveum.adoc
+++ b/pveum.adoc
@@ -222,6 +222,7 @@ password (unless logged in as 'root'), as well as the ability to correctly use
 the 'TOTP' key by typing the current 'OTP' value into the 'Verification Code'
 field before pressing the 'Apply' button.
 
+[[pveum_configure_u2f]]
 Server side U2F configuration
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
@@ -442,7 +443,7 @@ Each(`and`) or any(`or`) further element in the current list has to be true.
 
 `["perm", <path>, [ <privileges>... ], <options>...]`::
 The `path` is a templated parameter (see
-<<pveum_templated_paths,Objects and Paths>>). All (or , if the `any`
+<<pveum_templated_paths,Objects and Paths>>). All (or, if the `any`
 option is used, any) of the listed
 privileges must be allowed on the specified path. If a `require-param`
 option is specified, then its specified parameter is required even if the
@@ -489,10 +490,10 @@ Command Line Tool
 -----------------
 
 Most users will simply use the GUI to manage users. But there is also
-a full featured command line tool called `pveum` (short for ``**P**roxmox
+a fully featured command line tool called `pveum` (short for ``**P**roxmox
 **VE** **U**ser **M**anager''). Please note that all Proxmox VE command
 line tools are wrappers around the API, so you can also access those
-function through the REST API.
+functions through the REST API.
 
 Here are some simple usage examples. To show help type: