Clarify historical GitHub wget reliability

Author: jessuppi

docs/malware-rumors.md

@@ -122,9 +122,9 @@ That history is public in the Git repository.
 
 The option existed for compatibility rather than to conceal the destination of downloads.
 
-SlickStack historically supported older Ubuntu LTS releases where `wget` depended on older system certificate stores and TLS libraries. During that period, HTTPS compatibility changes and certificate-chain issues could cause otherwise valid unattended downloads to fail certificate verification. Earlier SlickStack infrastructure also relied more heavily on GitHub Pages and various public mirrors, during a period when plain HTTP retrieval was more commonly supported.
+SlickStack historically supported older Ubuntu LTS releases where `wget` depended on older system certificate stores and TLS libraries. During that period, HTTPS compatibility changes and certificate-chain issues could cause otherwise valid unattended downloads to fail certificate verification. Earlier SlickStack infrastructure relied primarily on GitHub Pages, with some project endpoints still accessible over plain HTTP at the time. As SlickStack also retrieved raw files from GitHub using unauthenticated `wget`, intermittent failures became an operational concern; the project documented blank or NULL responses in 2021 and later investigated GitHub's undocumented raw-file rate limits and authentication options, including in a [public Stack Overflow discussion](https://stackoverflow.com/questions/66522261/does-github-rate-limit-access-to-public-raw-files).
 
-That presented a practical problem for an automated server stack: a failed certificate check could interrupt an unattended download and prevent the expected maintenance or recovery action from completing.
+That presented a practical problem for an automated server stack: a failed certificate check or upstream download could interrupt an unattended request and prevent the expected maintenance or recovery action from completing.
 
 Using `--no-check-certificate` was therefore a compatibility tradeoff.