public inbox for pve-devel@lists.proxmox.com
 help / color / mirror / Atom feed
From: Dylan Whyte <d.whyte@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [pve-devel] [PATCH pve-docs] system requirements: minor language fixup
Date: Wed,  7 Oct 2020 10:48:13 +0200	[thread overview]
Message-ID: <20201007084813.1267-1-d.whyte@proxmox.com> (raw)

Signed-off-by: Dylan Whyte <d.whyte@proxmox.com>
---
 pve-system-requirements.adoc | 28 ++++++++++++++--------------
 1 file changed, 14 insertions(+), 14 deletions(-)

diff --git a/pve-system-requirements.adoc b/pve-system-requirements.adoc
index dc4cc30..bb474ac 100644
--- a/pve-system-requirements.adoc
+++ b/pve-system-requirements.adoc
@@ -4,8 +4,8 @@ ifdef::wiki[]
 :pve-toplevel:
 endif::wiki[]
 
-We recommend to use high quality server hardware when running {pve} in
-production. To further decrease the impact of a failed host you can run {pve} in
+We recommend using high quality server hardware, when running {pve} in
+production. To further decrease the impact of a failed host, you can run {pve} in
 a cluster with highly available (HA) virtual machines and containers.
 
 {pve} can use local storage (DAS), SAN, NAS, and distributed storage like Ceph
@@ -22,11 +22,11 @@ used in production.
 
 * Intel VT/AMD-V capable CPU/Mainboard for KVM full virtualization support
 
-* RAM: 1 GB RAM, plus additional RAM used for guests
+* RAM: 1 GB RAM, plus additional RAM needed for guests
 
 * Hard drive
 
-* One NIC
+* One network card (NIC)
 
 
 [[install_recommended_requirements]]
@@ -35,8 +35,8 @@ Recommended System Requirements
 
 * Intel EMT64 or AMD64 with Intel VT/AMD-V CPU flag.
 
-* Memory, minimum 2 GB for the OS and {pve} services. Plus designated memory for
-  guests. For Ceph and ZFS additional memory is required; approximately 1GB of
+* Memory: Minimum 2 GB for the OS and {pve} services, plus designated memory for
+  guests. For Ceph and ZFS, additional memory is required; approximately 1GB of
   memory for every TB of used storage.
 
 * Fast and redundant storage, best results are achieved with SSDs.
@@ -45,12 +45,12 @@ Recommended System Requirements
   or non-RAID with ZFS (optional SSD for ZIL).
 
 * VM storage:
-** For local storage use either a hardware RAID with battery backed write cache
+** For local storage, use either a hardware RAID with battery backed write cache
   (BBU) or non-RAID for ZFS and Ceph. Neither ZFS nor Ceph are compatible with a
   hardware RAID controller.
 ** Shared and distributed storage is possible.
 
-* Redundant (Multi-)Gbit NICs with additional NICs depending on the preferred
+* Redundant (Multi-)Gbit NICs, with additional NICs depending on the preferred
   storage technology and cluster setup.
 
 * For PCI(e) passthrough the CPU needs to support the VT-d/AMD-d flag.
@@ -68,13 +68,13 @@ recommended, especially regarding the I/O performance of your system.
 Supported Web Browsers for Accessing the Web Interface
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
-To access the web-based user interface one of the following browsers is
-recommended:
+To access the web-based user interface, we recommend using one of the following
+browsers:
 
-* Firefox, a release of the current year, or the latest Extended Support Release
-* Chrome, a release of the current year
+* Firefox, a release from the current year, or the latest Extended Support Release
+* Chrome, a release from the current year
 * Microsoft's currently supported version of Edge
-* Safari, a release of the current year
+* Safari, a release from the current year
 
-When used on a mobile device, {pve} will show a lightweight touch-based
+When accessed from a mobile device, {pve} will show a lightweight, touch-based
 interface.
-- 
2.20.1





             reply	other threads:[~2020-10-07  8:48 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-07  8:48 Dylan Whyte [this message]
2020-10-07 14:05 ` [pve-devel] applied: " Thomas Lamprecht

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=20201007084813.1267-1-d.whyte@proxmox.com \
    --to=d.whyte@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
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal