diff --git a/certificate-management.adoc b/certificate-management.adoc index d159015..8d3b855 100644 --- a/certificate-management.adoc +++ b/certificate-management.adoc @@ -130,7 +130,7 @@ under `Node -> Certificates`, or using the `pvenode config` command. After configuring the desired domain(s) for a node and ensuring that the desired ACME account is selected, you can order your new certificate over the -web-interface. On success the interface will reload after 10 seconds. +web interface. On success the interface will reload after 10 seconds. Renewal will happen xref:sysadmin_certs_acme_automatic_renewal[automatically]. diff --git a/local-btrfs.adoc b/local-btrfs.adoc index f68e30d..b04d0a3 100644 --- a/local-btrfs.adoc +++ b/local-btrfs.adoc @@ -146,7 +146,7 @@ After the next reboot this will be automatically done by the system at boot. Adding a BTRFS file system to {pve} ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ -You can add an existing BTRFS file system to {pve} via the web-interface, or +You can add an existing BTRFS file system to {pve} via the web interface, or using the CLI, for example: ---- diff --git a/markdown-primer.adoc b/markdown-primer.adoc index dbeb270..d8165e3 100644 --- a/markdown-primer.adoc +++ b/markdown-primer.adoc @@ -8,7 +8,7 @@ to write using an easy-to-read, easy-to-write plain text format, then convert it to structurally valid XHTML (or HTML). ____ -The {pve} web-interface has support for using Markdown to rendering rich text +The {pve} web interface has support for using Markdown to rendering rich text formatting in node and virtual guest notes. {pve} supports CommonMark with most extensions of GFM (GitHub Flavoured Markdown), diff --git a/pve-firewall.adoc b/pve-firewall.adoc index 5c0d144..836a51c 100644 --- a/pve-firewall.adoc +++ b/pve-firewall.adoc @@ -521,7 +521,7 @@ This allows to log in a fine grained manner and independent of the log-level defined for the standard rules in *Firewall* -> *Options*. While the `loglevel` for each individual rule can be defined or changed easily -in the WebUI during creation or modification of the rule, it is possible to set +in the web UI during creation or modification of the rule, it is possible to set this also via the corresponding `pvesh` API calls. Further, the log-level can also be set via the firewall configuration file by diff --git a/pve-storage-cifs.adoc b/pve-storage-cifs.adoc index 535aaaf..d5d54e7 100644 --- a/pve-storage-cifs.adoc +++ b/pve-storage-cifs.adoc @@ -10,7 +10,7 @@ Storage pool type: `cifs` The CIFS backend extends the directory backend, so that no manual setup of a CIFS mount is needed. Such a storage can be added directly -through the {pve} API or the WebUI, with all our backend advantages, +through the {pve} API or the web UI, with all our backend advantages, like server heartbeat check or comfortable selection of exported shares. @@ -32,7 +32,7 @@ server, or list the server in the local `/etc/hosts` file. share:: CIFS share to use (get available ones with `pvesm scan cifs
` or the -WebUI). Required. +web UI). Required. username:: diff --git a/pveceph.adoc b/pveceph.adoc index 0720941..089ac80 100644 --- a/pveceph.adoc +++ b/pveceph.adoc @@ -286,7 +286,7 @@ CLI Installation of Ceph Packages ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Alternatively to the the recommended {pve} Ceph installation wizard available -in the web-interface, you can use the following CLI command on each node: +in the web interface, you can use the following CLI command on each node: [source,bash] ---- @@ -418,7 +418,7 @@ network. It is recommended to use one OSD per physical disk. Create OSDs ~~~~~~~~~~~ -You can create an OSD either via the {pve} web-interface or via the CLI using +You can create an OSD either via the {pve} web interface or via the CLI using `pveceph`. For example: [source,bash] @@ -536,7 +536,7 @@ known as **P**lacement **G**roups (`PG`, `pg_num`). Create and Edit Pools ~~~~~~~~~~~~~~~~~~~~~ -You can create and edit pools from the command line or the web-interface of any +You can create and edit pools from the command line or the web interface of any {pve} host under **Ceph -> Pools**. When no options are given, we set a default of **128 PGs**, a **size of 3 @@ -567,7 +567,7 @@ pveceph pool create --add_storages ---- TIP: If you would also like to automatically define a storage for your -pool, keep the `Add as Storage' checkbox checked in the web-interface, or use the +pool, keep the `Add as Storage' checkbox checked in the web interface, or use the command-line option '--add_storages' at pool creation. Pool Options diff --git a/pvesdn.adoc b/pvesdn.adoc index 95605d8..7500cac 100644 --- a/pvesdn.adoc +++ b/pvesdn.adoc @@ -860,7 +860,7 @@ Zone: qinqzone2 Tag: 100 ---- -Apply the configuration on the main SDN web-interface panel to create VNets +Apply the configuration on the main SDN web interface panel to create VNets locally on each node. Create four Debian-bases virtual machines (vm1, vm2, vm3, vm4) and add network @@ -908,7 +908,7 @@ Zone: myvxlanzone Tag: 100000 ---- -Apply the configuration on the main SDN web-interface panel to create VNets +Apply the configuration on the main SDN web interface panel to create VNets locally on each nodes. Create a Debian-based virtual machine ('vm1') on node1, with a vNIC on `vxvnet1`. @@ -995,7 +995,7 @@ Subnet: 10.0.2.0/24 Gateway: 10.0.2.1 ---- -Apply the configuration from the main SDN web-interface panel to create VNets +Apply the configuration from the main SDN web interface panel to create VNets locally on each node and generate the FRR configuration. Create a Debian-based virtual machine ('vm1') on node1, with a vNIC on `myvnet1`. diff --git a/pvesr.adoc b/pvesr.adoc index f99f5f2..9eda008 100644 --- a/pvesr.adoc +++ b/pvesr.adoc @@ -121,7 +121,7 @@ and replicate to node B. Node A failed and can not get back online. Now you have to migrate the guest to Node B manually. -- connect to node B over ssh or open its shell via the WebUI +- connect to node B over ssh or open its shell via the web UI - check if that the cluster is quorate + diff --git a/pveum.adoc b/pveum.adoc index d7f9be3..a549810 100644 --- a/pveum.adoc +++ b/pveum.adoc @@ -643,7 +643,7 @@ field and pressing the 'Apply' button. There is no server setup required. Simply install a TOTP app on your smartphone (for example, https://freeotp.github.io/[FreeOTP]) and use -the Proxmox Backup Server web-interface to add a TOTP factor. +the Proxmox Backup Server web interface to add a TOTP factor. [[user_tfa_setup_webauthn]] === WebAuthn @@ -715,7 +715,7 @@ This is done via `/etc/pve/datacenter.cfg`. For instance: u2f: appid=https://mypve.example.com:8006 ---- -For a single node, the 'AppId' can simply be the address of the web-interface, +For a single node, the 'AppId' can simply be the address of the web interface, exactly as it is used in the browser, including the 'https://' and the port, as shown above. Please note that some browsers may be more strict than others when matching 'AppIds'. diff --git a/qm-pci-passthrough.adoc b/qm-pci-passthrough.adoc index 72e7fe9..3abeb50 100644 --- a/qm-pci-passthrough.adoc +++ b/qm-pci-passthrough.adoc @@ -319,7 +319,7 @@ or by adding a line to the VM configuration file: If your device has multiple functions (e.g., ``00:02.0`' and ``00:02.1`' ), you can pass them through all together with the shortened syntax ``00:02`'. This is equivalent with checking the ``All Functions`' checkbox in the -web-interface. +web interface. There are some options to which may be necessary, depending on the device and guest OS: diff --git a/qm.adoc b/qm.adoc index fa70d55..e79aaf5 100644 --- a/qm.adoc +++ b/qm.adoc @@ -498,7 +498,7 @@ CPU flags: attacks and is able to utilize the CPU feature Otherwise you need to set the desired CPU flag of the virtual CPU, either by -editing the CPU options in the WebUI, or by setting the 'flags' property of the +editing the CPU options in the web UI, or by setting the 'flags' property of the 'cpu' option in the VM configuration file. For Spectre v1,v2,v4 fixes, your CPU or system vendor also needs to provide a @@ -734,7 +734,7 @@ the QEMU user networking stack, where a built-in router and DHCP server can provide network access. This built-in DHCP will serve addresses in the private 10.0.2.0/24 range. The NAT mode is much slower than the bridged mode, and should only be used for testing. This mode is only available via CLI or the API, -but not via the WebUI. +but not via the web UI. You can also skip adding a network device when creating a VM by selecting *No network device*. @@ -1317,7 +1317,7 @@ Online Migration If your VM is running and no locally bound resources are configured (such as devices that are passed through), you can initiate a live migration with the `--online` -flag in the `qm migration` command evocation. The web-interface defaults to +flag in the `qm migration` command evocation. The web interface defaults to live migration when the VM is running. How it works