[pve-devel] [PATCH docs] faq: fix typos and grammar

[pve-devel] [PATCH docs] faq: fix typos and grammar

[Filip Schauer]

Signed-off-by: Filip Schauer <f.schauer@proxmox.com>
---
 pve-faq.adoc | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/pve-faq.adoc b/pve-faq.adoc
index 2e7054f..606a1c1 100644
--- a/pve-faq.adoc
+++ b/pve-faq.adoc
@@ -130,7 +130,7 @@ They must be carefully planned and tested and should *never* be started without
 having a current backup ready.
 +
 Although the specific upgrade steps depend on your respective setup, we provide
-general instructions and advice of how a upgrade should be performed:
+general instructions and advice on how an upgrade should be performed:
 +
 * https://pve.proxmox.com/wiki/Upgrade_from_8_to_9[Upgrade from {pve} 8 to 9]
 
@@ -165,7 +165,7 @@ virtualization* and use LXC as the basis of the container offering. With the
 addition of OCI image support (technology preview), Proxmox VE can also create
 containers from OCI images, including full system containers but also
 application containers (tech preview).
-The Poxmox Container Toolkit (`pct`) is tightly coupled with {pve}. This means
+The Proxmox Container Toolkit (`pct`) is tightly coupled with {pve}. This means
 that it is aware of cluster setups, and it can use the same network and storage
 resources as QEMU virtual machines (VMs). You can even use the {pve} firewall,
 create and restore backups, or manage containers using the HA framework.
-- 
2.47.3



_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel

[pve-devel] applied: [PATCH docs] faq: fix typos and grammar

[Fiona Ebner]

Applied, thanks!

[1/1] faq: fix typos and grammar
      commit: 744f756bb6c4c00ab3ae2e1eb2d1d5444c8617d8


_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel