From: Filip Schauer <f.schauer@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [pve-devel] [PATCH docs] faq: fix typos and grammar
Date: Mon, 24 Nov 2025 12:32:44 +0100 [thread overview]
Message-ID: <20251124113303.43480-1-f.schauer@proxmox.com> (raw)
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
reply other threads:[~2025-11-24 11:33 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20251124113303.43480-1-f.schauer@proxmox.com \
--to=f.schauer@proxmox.com \
--cc=pve-devel@lists.proxmox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox