From b48666dc43d6450c76f06c72f7181b207d5c9eae Mon Sep 17 00:00:00 2001
From: Miguel Jacq <mig@mig5.net>
Date: Sun, 21 Jun 2026 12:45:20 +1000
Subject: [PATCH] more docs

---
 src/content/docs.html | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/src/content/docs.html b/src/content/docs.html
index 0c64ab0..58af7fc 100644
--- a/src/content/docs.html
+++ b/src/content/docs.html
@@ -158,7 +158,7 @@ description: "How Enroll works: harvest, manifest, modes, and configuration."
 
 	  <div class="alert alert-secondary mt-3 mb-0">
             <div class="fw-semibold">Does Enroll use community roles/modules?</div>
-	    <div class="small mb-0">No, Enroll does not pull in Ansible Galaxy roles, Puppet Forge modules, or Salt formulas. It generates its own output from the harvest state. If you want to adopt community content later, Enroll can still help you discover and bootstrap the host-specific state you need to port.</div>
+	    <div class="small mb-0">When using Ansible and any Docker/Podman images, Flatpak or Snaps are 'harvested' by the system, the manifested ansible playbooks will expect to use some of those community collections, but otherwise, everything is 'core' Ansible. Enroll generates a <code>requirements.yml</code> you can use with <code>ansible-galaxy</code> to install it, if needed, but many community collections may already be on your system, depending on your installation. For Puppet and Salt, no third-party extensions or modules are used.</div>
           </div>
         </section>