diff --git a/content/docs/distros/Asahi_Linux.md b/content/docs/distros/Asahi_Linux.md
index 180a69a..b9e91e9 100644
--- a/content/docs/distros/Asahi_Linux.md
+++ b/content/docs/distros/Asahi_Linux.md
@@ -9,14 +9,16 @@ title: Asahi Linux
 ## Envision
 
 Fedora has the `envision` package, as well as the `envision-monado` and `envision-wivrn` metapackages which grab the necessary dependencies for building monado and wivrn, respectively.
-This *will not* be the most up-to-date with upstream envision, but seeing as Envision doesn't currently build aarch64 AppImages, this is the easiest way to build custom commits of monado/wivrn/opencomposite/xrizer.
+This *will not* be the most up-to-date with upstream envision, but seeing as Envision doesn't currently build aarch64 AppImages, this is the easiest way to build custom commits of monado/wivrn/opencomposite/xrizer for arm64, specifically.
+If you are looking to use non-native VR applications, or [Steam Games](#steam-games-under-muvm), you should continue on into the [Multiarch](#multiarch) section.
 
 ## Multiarch
 
 Depending on what openxr applications you are planning on running, you may need multiple builds of the same component, but for different architectures.
 You can acquire these builds in multiple ways, such as cross-compiling, or gathering builds from multiple machines.
 
-A repo ([vr-multiarch-build]) for cross-compiling these components has been thrown together to make things easy.
+A repo ([vr-multiarch-build]) for cross-compiling these components has been thrown together to make things easier.
+You will need podman, as well as the typical runtime dependencies.
 Some sample usage:
 
 ```sh
@@ -43,7 +45,7 @@ sudo ./setcap.sh
 ## Steam Games under muvm
 
 What worked for me was running `monado-service` manually, with all the environment variables that envision uses, and manually setting up environment variables for steam launch arguments.
-On my machine, the launch arguments look like: `XR_RUNTIME_JSON=~/.config/openxr/1/active_runtime.x86_64.json PRESSURE_VESSEL_FILESYSTEMS_RW=/run/user/1000/wivrn/comp_ipc:/run/user/1000/monado_comp_ipc %command%`
+On my machine, the steam launch arguments look like: `XR_RUNTIME_JSON=~/.config/openxr/1/active_runtime.x86_64.json PRESSURE_VESSEL_FILESYSTEMS_RW=/run/user/1000/wivrn/comp_ipc:/run/user/1000/monado_comp_ipc %command%`
 There are some extra complications caused by muvm putting its `XDG_RUNTIME_DIR` in a weird spot interfering with monado's ability to connect to itself.
 Therefore, my reccomended launch order is as follows: