chore: edit text

Katie Horne · Katie Horne · commit 7865f1283edb · 2022-03-18T09:47:01.000-05:00
diff --git a/admin/workspace-management/cvms/management.md b/admin/workspace-management/cvms/management.md
@@ -9,8 +9,8 @@ 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**.
 
-This section describes the customization features that Coder offers for CVMs as
-well:
+This section also describes the customization features that Coder offers for
+CVMs:
 
 ![CVM Settings](../../../assets/admin/cvm-settings.png)
 
@@ -25,7 +25,7 @@ To improve the startup time for CVM-based workspaces, you can enable caching.
 Cached CVMs require the `shiftfs` kernel to be present on the node. Some
 distributions (such as Ubuntu) include `shiftfs`. If you're unsure if `shiftfs`
 is present on your nodes, you can check by running `modinfo shiftfs`. If no
-output is returned, then you do not have `shiftfs` installed.
+output is returned, you do not have `shiftfs` installed.
 
 If you don't want to install `shiftfs` yourself, you can have Coder install the
 module automatically for you. **It is important that you do not have secure boot
@@ -39,10 +39,10 @@ install `shiftfs` on your behalf.**
 > Self-contained workspace builds are currently an **alpha** feature.
 
 By default, Coder initializes workspaces by running commands inside the
-container. When you enable [self-contained workspace builds], workspaces control
-the initialization sequence instead. This enables operation on clusters that
-restrict command execution inside containers using the Kubernetes API, such as
-with the `kubectl exec` command.
+container. Workspaces, however, control the initialization sequence instead when
+you enable [self-contained workspace builds]. This enables cluster operations
+that restrict command execution inside containers using the Kubernetes API, such
+as the `kubectl exec` command.
 
 [self-contained workspace builds]: ../self-contained-builds.md
 
@@ -61,39 +61,39 @@ workspace container.
 
 Coder allows the creation of custom network interfaces using the Linux TUN
 device. When using the **Enable TUN device** setting, Coder workspaces will have
-a `/dev/net/tun` device mounted into the workspace at build time. A TUN device
-is often required for VPN usage.
+a `/dev/net/tun` device mounted into the workspace at build time. VPN usage
+often requires a TUN device.
 
-Users may need root (or `sudo`) access within their workspace to be able to use
-the TUN device and start a VPN client.
+Users may need root (or `sudo`) access within their workspace to use the TUN
+device and start a VPN client.
 
-> At this time, Coder does not support TUN devices for other workspace types
-> (such as EC2 or Docker).
+> At this time, Coder does not support TUN devices for non-Kubernetes workspace
+> types, such as EC2 or Docker.
 >
 > If you're working with EC2 workspaces, we recommend enabling privileged mode
 > in the workspace provider settings, which will allow users to create their own
 > TUN device.
 
 We've tested this feature using the [Tailscale](https://tailscale.com/) VPN
-within Coder. Keep in mind that you may have to change your VPN settings to keep
-any persistent files (such as configuration/identity) files in your home volume,
-as any data outside the home volume is cleared when the workspace is rebuilt.
+within Coder. Remember that you may have to change your VPN settings to keep any
+persistent files (such as configuration/identity) files in your home volume, as
+any data outside the home volume is cleared when the workspace is rebuilt.
 
 ## FUSE device
 
-> FUSE devices currently an **alpha** feature.
+> FUSE devices are currently an **alpha** feature.
 
 Coder allows the creation of custom filesystems using the Linux FUSE userspace
-filesystem device. When using the **Enable FUSE device** setting, Coder
+filesystem device. By enabling the **Enable FUSE device** setting, Coder
 workspaces will have a `/dev/fuse` device mounted into the workspace at build
 time. These devices are often used to mount specialized filesystems, such as
 Google Cloud Storage buckets, to your workspace.
 
-Users may need root (or `sudo`) access within their workspace to be able to use
-the FUSE device and start a FUSE filesystem.
+Users may need root (or `sudo`) access within their workspace to use the FUSE
+device and start a FUSE filesystem.
 
-> At this time, Coder does not support FUSE devices for other workspace types
-> (such as EC2 or Docker).
+> At this time, Coder does not support FUSE devices for non-Kubernetes workspace
+> types, such as EC2 or Docker.
 >
 > If you're working with EC2 workspaces, we recommend enabling privileged mode
 > in the workspace provider settings, which will allow users to create their own
@@ -106,6 +106,6 @@ mkdir /tmp/mnt
 sshfs user@host:/ /tmp/mnt
 ```
 
-Then in a second terminal run `ls /tmp/mnt` to list the files from the remote
+Then, in a second terminal, run `ls /tmp/mnt` to list the files from the remote
 host. You should also be able to see a `fuse.sshfs` entry in the output from the
 `mount` command.
