Mention technology preview also in the introductory paragraph, and fix an incomplete sentence in the "Open Container Initiative (OCI) Images" section.
Signed-off-by: Friedrich Weber <[email protected]> --- Notes: best viewed with --word-diff pct.adoc | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/pct.adoc b/pct.adoc index fe656d8..d68a4ed 100644 --- a/pct.adoc +++ b/pct.adoc @@ -58,10 +58,10 @@ Our primary goal has traditionally been to offer an environment that provides the benefits of using a VM, but without the additional overhead. This means that Proxmox Containers have been primarily categorized as ``System Containers''. -With the introduction of OCI (**O**pen **C**ontainer **I**nitiative) image support, -Proxmox VE now also integrates ``Application Containers''. When creating a -container from an OCI image, the image is automatically converted to the -LXC stack that Proxmox VE uses. +With the introduction of OCI (**O**pen **C**ontainer **I**nitiative) image +support, Proxmox VE now also integrates ``Application Containers'' as a +technology preview. When creating a container from an OCI image, the image is +automatically converted to the LXC stack that Proxmox VE uses. This approach allows users to benefit from a wide ecosystem of pre-packaged applications while retaining the robust management features of Proxmox VE. @@ -353,8 +353,8 @@ Open Container Initiative (OCI) Images ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ {pve} can also use OCI images to create containers, both system containers but -also application containers. Note that running application in {pve} is currently -considered a (technology preview. +also application containers. Note that running application containers in {pve} +is currently considered a technology preview. A container created from an OCI image still uses the existing LXC framework. -- 2.47.3 _______________________________________________ pve-devel mailing list [email protected] https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
