Clarify toolkit issue reporting for RPM installs

Author: root

docs/personas/quick-deploy/install-perfsonar-toolkit.md

@@ -1839,17 +1839,18 @@ Perform these checks before handing the host over to operations:
 
 ??? note "What to include when reporting issues via email"
 
-    To help us diagnose install problems quickly, please include:
+    To help us diagnose toolkit (RPM) install problems quickly, please include:
 
-    - Host details: OS version (e.g., `cat /etc/os-release`), kernel (`uname -r`), and whether this is testpoint or toolkit.
-    - Script/log context: which script/step failed and the exact command you ran.
+    - Host details: OS version (`cat /etc/os-release`), kernel (`uname -r`), and that this is a **Toolkit/RPM** install.
+    - What failed: which step/command you ran and the exact error output (paste the terminal snippet).
     - Timestamps: approximate time of failure and timezone.
-    - Outputs/logs: relevant console output and excerpts from `journalctl -u podman -n 200`, `tail -200 /var/log/perfSONAR-install-nftables.log`, and any script-specific log mentioned in the error.
-    - Network state: `ip -br addr`, `ip rule show`, `nmcli connection show`, and whether port 80/443 should be open externally.
-    - Certificates (if LE): whether port 80 was reachable from the Internet and the contents of `/var/log/letsencrypt/letsencrypt.log` around the failure.
+    - Packages/services: `rpm -qa 'perfsonar*' | sort | head -n 30`, and `systemctl status pscheduler-scheduler pscheduler-runner pscheduler-ticker httpd`.
+    - Logs: `journalctl -u pscheduler-scheduler -u pscheduler-runner -u pscheduler-ticker -u httpd -n 200`, plus any relevant `/var/log/perfsonar/*.log` excerpts.
+    - Network state: `ip -br addr`, `ip rule show`, `nmcli connection show`, and `nft list ruleset` (or `firewall-cmd --list-all` if firewalld is used).
+    - Certificates (if Let’s Encrypt or custom HTTPS involved): whether port 80/443 are reachable externally and excerpts from `/var/log/httpd/error_log` and `/var/log/letsencrypt/letsencrypt.log`.
     - Contact info: your name, site, and a callback email.
 
-    Send reports to your usual perfSONAR support contact or project mailing list with the subject prefix `[perfSONAR install issue]`.
+    Send reports to your usual perfSONAR support contact or project mailing list with the subject prefix `[perfSONAR toolkit install issue]`.
 
     **Logs:**