Edit text

Author: Katie Horne

admin/workspace-management/cvms/cluster-setup.md

@@ -8,14 +8,14 @@ by Google, Azure, and Amazon to support CVMs.
 
 ## Google Cloud Platform w/ GKE
 
-To use CVMs with GKE, [create a cluster](../../../setup/kubernetes/google.md) using
-the following parameters:
+To use CVMs with GKE, [create a cluster](../../../setup/kubernetes/google.md)
+with the following parameters set:
 
 - GKE Master version `latest`
 - `node-version = "latest"`
 - `image-type = "UBUNTU"`
 
-For example:
+Example:
 
 ```console
 gcloud beta container clusters create "YOUR_NEW_CLUSTER" \
@@ -27,15 +27,15 @@ gcloud beta container clusters create "YOUR_NEW_CLUSTER" \
 
 ## Azure Kubernetes Service
 
-If you're using Kubernetes version 1.18, Azure defaults to the correct Ubuntu
+If you're using Kubernetes version `1.18`, Azure defaults to the correct Ubuntu
 node base image. When
 [creating your cluster](../../../setup/kubernetes/azure.md), set
 `--kubernetes-version` to `1.18.x` or newer for CVMs.
 
 ## Amazon Web Services w/ EKS
 
-You can modify an existing [AWS-hosted container](../../../setup/kubernetes/aws.md)
-to support CVMs by
+You can modify an existing
+[AWS-hosted container](../../../setup/kubernetes/aws.md) to support CVMs by
 [creating a nodegroup](https://eksctl.io/usage/managing-nodegroups/#creating-a-nodegroup-from-a-config-file)
 and updating your `eksctl` config spec.
 
@@ -57,10 +57,10 @@ and updating your `eksctl` config spec.
        ami: <your Ubuntu 20.04 AMI ID>
    ```
 
-   > [See here for a list of EKS-compatible Ubuntu
-   > AMIs](https://cloud-images.ubuntu.com/docs/aws/eks/)
+   > [See here for a list of EKS-compatible Ubuntu AMI IDs](https://cloud-images.ubuntu.com/docs/aws/eks/)
 
-1. Create your nodegroup (be sure to provide the correct file name):
+1. Create your nodegroup using the config file you just created (be sure to
+   provide the correct file name):
 
    ```console
    eksctl create nodegroup --config-file=coder-node.yaml

admin/workspace-management/cvms/images.md

@@ -67,5 +67,5 @@ To use CVM workspaces with private images, you **must** create a
 credentials. Private images that can be pulled directly by the node will not
 work with CVMs.
 
-This restriction is removed if you enable [cached
-CVMs](../cvms/management.md#enabling-cached-cvms).
+This restriction does not apply if you enable
+[cached CVMs](../cvms/management.md#enabling-cached-cvms).

admin/workspace-management/cvms/index.md

@@ -3,34 +3,34 @@ title: Docker in workspaces
 description: Learn about supproting Docker inside workspaces.
 ---
 
-If you're a site admin or a site manager, you can enable
-[container-based virtual machines (CVMs)](../../../workspaces/cvms.md) as a
-workspace deployment option. CVMs allow users to run system-level programs, such
-as Docker and systemd, in their workspaces.
+[Container-based virtual machines (CVMs)](../../../workspaces/cvms.md) allow
+users to run system-level programs, such as Docker and systemd, in their
+workspaces.
+
+If you're a site admin or a site manager, you can enable CVMs as a workspace
+deployment option.
 
 ## Infrastructure requirements
 
 - CVMs leverage the
   [Sysbox container runtime](https://github.com/nestybox/sysbox), so the
   Kubernetes Node must run a supported Linux distro with the minimum kernel
-  version (see
+  version. See
   [Sysbox distro compatibility](https://github.com/nestybox/sysbox/blob/master/docs/distro-compat.md)
-  for more information)
-- The cluster must allow privileged containers and `hostPath` mounts. Read more
-  about why this is still secure [here](#security).
+  for more information.
+
+- The cluster must allow privileged containers and `hostPath` mounts. See
+  [Security](#security) for more information on why this is still secure.
 
 > You can use any cloud provider that supports the above requirements, but we
 > have instructions on how to set up supported clusters on
 > [AWS](../../../setup/kubernetes/aws.md) and
 > [Google](../../../setup/kubernetes/google.md). Azure-hosted clusters will meet
 > these requirements as long as you use Kubernetes version 1.18+.
->
-> Coder doesn't support legacy versions of cluster-wide proxy services such as
-> Istio, and CVMs do not currently support NFS as a file system.
 
 ## Security
 
-The [Container-based virtual machine](../../../workspaces/cvms.md) deployment
+The [container-based virtual machine](../../../workspaces/cvms.md) deployment
 option leverages the
 [Sysbox container runtime](https://github.com/nestybox/sysbox) to offer a
 VM-like user experience while retaining the footprint of a typical container.
@@ -48,11 +48,15 @@ container is what provides
 
 ## Known issues
 
-NVIDIA GPUs can be added to CVMs on bare metal clusters only. This feature is
-not supported on Google Kubernetes Engine or other cloud providers at this time.
+- NVIDIA GPUs can be added to CVMs on bare metal clusters only. This feature is
+  not supported on Google Kubernetes Engine or other cloud providers at this
+  time.
+
+  Support for NVIDIA [GPUs](../gpu-acceleration.md) is in **beta**. We do not
+  support AMD GPUs at this time.
 
-Support for NVIDIA [GPUs](../gpu-acceleration.md) is in **beta**. We do not support
-AMD GPUs at this time.
+- Coder doesn't support legacy versions of cluster-wide proxy services such as
+  Istio, and CVMs do not currently support NFS as a file system.
 
 ## Next Steps
 

admin/workspace-management/cvms/management.md

@@ -9,7 +9,7 @@ a site manager must enable CVMs. To do so:
 1. Go to **Manage > Admin > Infrastructure**.
 1. Toggle the **Enable Container-Based Virtual Machines** option to **Enable**.
 
-### Enabling cached CVMs
+## Cached CVMs
 
 > Cached CVMs are currently an **alpha** feature.