Apply suggestions from code review

(Will flatten)

Co-authored-by: classabbyamp <[email protected]>
Co-authored-by: 0x5c <[email protected]>

Author: 3 people

src/config/containers-and-vms/lxc.md

@@ -124,32 +124,32 @@ wrong map is possible, but inconvenient.
 Incus provides an alternative interface to LXC's `lxc-*` utilities. However, it
 does not require the configuration described in [the previous section](#lxc).
 
-Edit `/etc/rc.conf` and set the `CGROUP_MODE` variable to `unified`. Install the
+In `/etc/rc.conf`, set the `CGROUP_MODE` variable to `unified`. Install the
 `incus` package, and [enable](../services/index.md#enabling-services) the
 `incus` service.
 
 Incus users must be belong to the `_incus-admin` group.
 
-Optionally enable some users to have limited acces to incus as described
+Optionally, some users can be given limited access to Incus as described
 [here](https://linuxcontainers.org/incus/docs/main/howto/projects_confine/#confine-projects-to-specific-incus-users).
-Add users to the `_incus` group, and enable the `incus-user` service
+Add users to the `_incus` group, and enable the `incus-user` service.
 
 Note that `incus-user` will initialize the default incus profile when it is
-started. To avoid default configuration initialize incus for youself with `incus
+started. To avoid default configuration initialize incus for yourself with `incus
 admin init` before enabling `incus-user`.
 
-**WARNING:** `incus-user` will also replace the networking config of the default
-profile if it appears invalid. runit does not have socket activation so this
-happens when when the machine boots instead of when a user attempts to access
-it. If the default profile uses a [bridge
-interface](../network/index.md#bridge-interfaces) `incus-user` may replace it on
-boot.
+> Warning: `incus-user` will also replace the networking config of the default
+> profile if it appears invalid. runit does not have socket activation so this
+> happens when when the machine boots instead of when a user attempts to access
+> it. If the default profile uses a [bridge
+> interface](../network/index.md#bridge-interfaces) `incus-user` may replace it on
+> boot.
 
-To migrate existing LXD setups to incus use the 'lxd-to-incus' binary from the
+To migrate existing LXD setups to Incus, use the `lxd-to-incus` tool from the
 `incus-tools` package as described
 [here](https://linuxcontainers.org/incus/docs/main/howto/server_migrate_lxd/).
 
-To migrate existing LXC containers to incus use the 'lxc-to-incus' binary from
+To migrate existing LXC containers to Incus use the `lxc-to-incus` script from
 the `incus-tools` package as described
 [here](https://linuxcontainers.org/incus/docs/main/howto/migrate_from_lxc/).