diff --git a/System-Requirements.md b/System-Requirements.md
index c8abd1a..5650ef1 100644
--- a/System-Requirements.md
+++ b/System-Requirements.md
@@ -6,16 +6,13 @@ The main requirement is Gravity Sync requires at least two separate Pi-hole 5.x
 - If you're not using the `root` account, make sure that the account is a member of either the `sudo` or `wheel` group on both the primary and secondary Pi-hole. Most of the pre-built images available for the Raspberry Pi already have this configured, as does Ubuntu. 
 - During installation, if a non-root user will be given [passwordless sudo](https://linuxize.com/post/how-to-run-sudo-command-without-password/) permissions to the system.
 
-### Docker Pi-hole
+### Containerized Pi-hole
 
-- As of Gravity Sync 3.1, your Pi-hole installs can be a Docker container deployment.
+- Your Pi-hole installs can be a Docker container deployment as of Gravity Sync 3.1.
+- Beta support for Podman as a container engine has been introduced starting in Gravity Sync 3.3.
 - Gravity Sync will run directly on the host OS, and not inside of the container image.
 - Only the [official Pi-hole Docker image](https://hub.docker.com/r/pihole/pihole) is supported.
-
-### Podman Containers
-
-- As of Gravity Sync 3.3, beta support for Podman as a container engine has been introduced.
-- The same restrictions as above for Docker, apply to Podman.
+- In addition to the officially supported Linux distributions as outlined above, when using a container engine, host OS deployments on more container oriented distributions such as [VMware Photon OS](https://vmware.github.io/photon/) may be used, so long as they’re able to run the Gravity Sync specific requirements below.
 
 ## Required Components