update installer screenshots with 6.0

[pve-docs.git] / pve-intro.adoc

diff --git a/pve-intro.adoc b/pve-intro.adoc
index 0431e09a0b86b3b2b93fcefc7746c210a900444f..b55889bfdc91a795abc250c369656e6798150f8e 100644 (file)
--- a/pve-intro.adoc
+++ b/pve-intro.adoc
@@ -39,7 +39,7 @@ enables you to store the configuration of thousands of virtual
 machines. By using corosync, these files are replicated in real time
 on all cluster nodes. The file system stores all data inside a
 persistent database on disk, nonetheless, a copy of the data resides
-in RAM which provides a maximum storage size is 30MB - more than
+in RAM which provides a maximum storage size of 30MB - more than
 enough for thousands of VMs.
 +
 Proxmox VE is the only virtualization platform using this unique
@@ -106,6 +106,7 @@ We currently support the following Network storage types:
 * LVM Group (network backing with iSCSI targets)
 * iSCSI target
 * NFS Share
+* CIFS Share
 * Ceph RBD
 * Directly use iSCSI LUNs
 * GlusterFS
@@ -125,9 +126,8 @@ running Containers and KVM guests. It basically creates an archive of
 the VM or CT data which includes the VM/CT configuration files.
 
 KVM live backup works for all storage types including VM images on
-NFS, iSCSI LUN, Ceph RBD or Sheepdog. The new backup format is
-optimized for storing VM backups fast and effective (sparse files, out
-of order data, minimized I/O).
+NFS, CIFS, iSCSI LUN, Ceph RBD. The new backup format is optimized for storing
+VM backups fast and effective (sparse files, out of order data, minimized I/O).
 
 
 High Availability Cluster
@@ -145,7 +145,7 @@ Flexible Networking
 Proxmox VE uses a bridged networking model. All VMs can share one
 bridge as if virtual network cables from each guest were all plugged
 into the same switch. For connecting VMs to the outside world, bridges
-are attached to physical network cards assigned a TCP/IP
+are attached to physical network cards and assigned a TCP/IP
 configuration.
 
 For further flexibility, VLANs (IEEE 802.1q) and network
@@ -183,8 +183,8 @@ Open source software also helps to keep your costs low and makes your
 core infrastructure independent from a single vendor.
 
 
-Your benefit with {pve}
------------------------
+Your benefits with {pve}
+------------------------
 
 * Open source software
 * No vendor lock-in
@@ -241,35 +241,6 @@ https://linuxcontainers.org/[LXC]. Containers are now deeply
 integrated, and they can use the same storage and network features
 as virtual machines.
 
-Improving the {pve} documentation
----------------------------------
+include::howto-improve-pve-docs.adoc[]
+include::translation.adoc[]
 
-Depending on which issue you want to improve, you can use a variety of
-communication mediums to reach the developers.
-
-If you notice an error in the current documentation, use the·
-http://bugzilla.proxmox.com[Proxmox bug tracker] and propose an·
-alternate text/wording.
-
-If you want to propose new content, it depends on what you want to
-document:
-
-* if the content is specific to your setup, a wiki article is the best
-option. For instance if you want to document specific options for guest
-systems, like which combination of Qemu drivers work best with a less popular
-OS, this is a perfect fit for a wiki article.
-
-* if you think the content is generic enough to be of interest for all users,
-then you should try to get it in the reference documentation. The reference
-documentation is written in the easy to use asciidoc document format. 
-Editing the official documentation requires to clone the git repository at
-`git://git.proxmox.com/git/pve-docs.git` and then follow the 
-https://git.proxmox.com/?p=pve-docs.git;a=blob_plain;f=README.adoc;hb=HEAD[REAME.adoc] document.
-
-Improving the documentation is just as easy as editing a Wikipedia
-article and is an interesting foray in the development of a large
-opensource project.
-
-NOTE: If you are interested in working on the {pve} codebase, the
-https://pve.proxmox.com/wiki/Developer_Documentation[Developer
-Documentation] wiki article will show you where to start.