From: Dylan Whyte <d.whyte@proxmox.com>
To: pmg-devel@lists.proxmox.com
Subject: [pmg-devel] [PATCH pmg-docs 3/4] faq: language fixup
Date: Tue, 13 Jul 2021 17:54:05 +0200 [thread overview]
Message-ID: <20210713155406.185306-3-d.whyte@proxmox.com> (raw)
In-Reply-To: <20210713155406.185306-1-d.whyte@proxmox.com>
minor fixup for the FAQ section
Signed-off-by: Dylan Whyte <d.whyte@proxmox.com>
---
pmg-faq.adoc | 24 ++++++++++++------------
1 file changed, 12 insertions(+), 12 deletions(-)
diff --git a/pmg-faq.adoc b/pmg-faq.adoc
index c3dbd0e..162a221 100644
--- a/pmg-faq.adoc
+++ b/pmg-faq.adoc
@@ -22,12 +22,12 @@ What distribution is {pmg} based on?::
What license does the {pmg} project use?::
{pmg} code is licensed under the GNU Affero General Public License,
-version 3 (since the 5.0 release).
+version 3 (as of the 5.0 release).
Will {pmg} run on a 32bit processor?::
{pmg} works only on 64-bit CPUs (AMD or Intel). There is no plan
-for 32-bit for the platform.
+for 32-bit platform support.
[[faq-support-table]]
How long will my {pmg} version be supported?::
@@ -35,7 +35,7 @@ How long will my {pmg} version be supported?::
{pmg} versions are supported at least as long as the corresponding
Debian Version is
https://wiki.debian.org/DebianOldStable[oldstable]. {pmg} uses a
-rolling release model and using the latest stable version is always
+rolling release model, and using the latest stable version is always
recommended.
+
[width="100%",cols="5*d",options="header"]
@@ -47,12 +47,12 @@ recommended.
|===============================================================================
NOTE: {pmg} releases before 5.0 are not listed here. As they are all EOL (End
-Of Life), it's highly recommended to upgrade to a newer version if still in use.
+Of Life), it's highly recommended to upgrade to a newer version, if still in use.
[[faq-upgrade]]
How can I upgrade {pmg} to the next release?::
-Minor version upgrades, for example upgrading from {pmg} in version 5.1
+Minor version upgrades, for example, upgrading from {pmg} version 5.1
to 5.2, can be done just like any normal update, either through the
__Node -> Updates__ panel or through the command line with:
+
@@ -61,15 +61,15 @@ apt update
apt full-upgrade
----
+
-NOTE: Always ensure you correctly set up the
-xref:pmg_package_repositories[package repositories] and only continue with the
-actual upgrade if `apt update` did not hit any error.
+NOTE: Always ensure that you correctly set up the
+xref:pmg_package_repositories[package repositories], and only continue with the
+actual upgrade if `apt update` did not hit any errors.
+
-Major version upgrades, for example going from {pmg} 5.4 to 6.0, are
-also supported. They must be carefully planned and tested and should
-*never* be started without having a current backup ready.
+Major version upgrades, for example, going from {pmg} 5.4 to 6.0, are
+also supported. They must be carefully planned and tested, and should
+*never* be started without having an up-to-date backup ready.
Although the specific upgrade steps depend on your respective setup, we
-provide general instructions and advice of how a upgrade should be
+provide general instructions and advice on how an upgrade should be
performed:
+
* https://pmg.proxmox.com/wiki/index.php/Upgrade_from_6.x_to_7.0[Upgrade from {pmg} 6.x to 7.0]
--
2.30.2
next prev parent reply other threads:[~2021-07-13 15:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-13 15:54 [pmg-devel] [PATCH pmg-docs 1/4] service daemons: " Dylan Whyte
2021-07-13 15:54 ` [pmg-devel] [PATCH pmg-docs 2/4] cli tools: " Dylan Whyte
2021-07-13 15:54 ` Dylan Whyte [this message]
2021-07-13 15:54 ` [pmg-devel] [PATCH pmg-docs 4/4] certificate management: langauge fixup Dylan Whyte
2021-07-13 16:41 ` [pmg-devel] applied-series: [PATCH pmg-docs 1/4] service daemons: language fixup Stoiko Ivanov
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=20210713155406.185306-3-d.whyte@proxmox.com \
--to=d.whyte@proxmox.com \
--cc=pmg-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