X-Git-Url: https://git.proxmox.com/?p=pve-docs.git;a=blobdiff_plain;f=pve-faq.adoc;h=9489295b8621388d70244b5a70b4880ceb87661d;hp=d3f2c84e144e6b63b22389460d1fd9a9a994a130;hb=67ea62c95a6b831084aa2850df803c5abc281cc7;hpb=16aecaa2dac0ce1aacc994201dd8702c04cee968

diff --git a/pve-faq.adoc b/pve-faq.adoc
index d3f2c84..9489295 100644
--- a/pve-faq.adoc
+++ b/pve-faq.adoc
@@ -21,15 +21,15 @@ version 3.
 
 Will {pve} run on a 32bit processor?::
 
-{pve} works only on 64-bit CPU´s (AMD or Intel). There is no plan
+{pve} works only on 64-bit CPUs (AMD or Intel). There is no plan
 for 32-bit for the platform.
 +
 NOTE: VMs and Containers can be both 32-bit and/or 64-bit.
 
 Does my CPU support virtualization?::
 
-To check if your CPU is virtualization compatible, check for the "vmx"
-or "svm" tag in this command output:
+To check if your CPU is virtualization compatible, check for the `vmx`
+or `svm` tag in this command output:
 +
 ----
 egrep '(vmx|svm)' /proc/cpuinfo
@@ -86,24 +86,35 @@ recommended.
 | {pve} 1.x     | Debian 5 (Lenny)  | 2008-10       | 2012-03    | 2013-01
 |===========================================================
 
-LXC vs LXD vs Docker::
+LXC vs LXD vs Proxmox Containers vs Docker::
 
 LXC is a userspace interface for the Linux kernel containment
-features. Through a powerful API and simple tools, it lets Linux users easily
-create and manage system containers. +
-LXD is building on top of LXC to provide a new, better user experience. Under
-the hood, LXD uses LXC through liblxc and its Go binding to create and manage
-the containers. It's basically an alternative to LXC's tools and distribution
-template system with the added features that come from being controllable over
-the network. +
-LXC, as well as the former OpenVZ, aims at *system virtualization*, ie
-allows you to run a complete OS inside a container, where you log in as ssh,
-add users, run apache, etc...
+features. Through a powerful API and simple tools, it lets Linux users
+easily create and manage system containers. LXC, as well as the former
+OpenVZ, aims at *system virtualization*, i.e. allows you to run a
+complete OS inside a container, where you log in as ssh, add users,
+run apache, etc...
++
+LXD is building on top of LXC to provide a new, better user
+experience. Under the hood, LXD uses LXC through `liblxc` and its Go
+binding to create and manage the containers. It's basically an
+alternative to LXC's tools and distribution template system with the
+added features that come from being controllable over the network.
++
+Proxmox Containers also aims at *system virtualization*, and thus uses
+LXC as the basis of its own container offer. The Proxmox Container
+Toolkit is called `pct`, and is tightly coupled with {pve}. That means
+that it is aware of the cluster setup, and it can use the same network
+and storage resources as fully virtualized VMs. You can even use the
+{pve} firewall, create and restore backups, or manage containers using
+the HA framework. Everything can be controlled over the network using
+the {pve} API.
++
 Docker aims at running a *single* application running in a contained
 environment. Hence you're managing a docker instance from the host with the
-docker toolkit.
-
-NOTE: Proxmox VE aims at system virtualization, and thus uses LXC as the basis
-of its own container offer. You can however perfectly install and use docker
-inside a VM, and thus getting the benefit of software containerization
-with the very strong isolation that VMs provide.
+docker toolkit. It is not recommended to run docker directly on your
+{pve} host.
++
+NOTE: You can however perfectly install and use docker inside a Proxmox Qemu
+VM, and thus getting the benefit of software containerization with the very
+strong isolation that VMs provide.