Apply suggestions from code review

JLLeitschuh · felicitymay · web-flow · commit 73fba3a3c0af · 2021-02-15T10:01:03.000-05:00
Co-authored-by: Felicity Chapman &lt;felicitymay@github.com&gt;
diff --git a/java/ql/src/Security/CWE/CWE-1104/MavenPomDependsOnBintray.qhelp b/java/ql/src/Security/CWE/CWE-1104/MavenPomDependsOnBintray.qhelp
@@ -4,8 +4,8 @@
 <qhelp>
 <overview>
 <p><a href="https://jfrog.com/blog/into-the-sunset-bintray-jcenter-gocenter-and-chartcenter/">Bintray and JCenter are shutting down on February 1st, 2022</a>.
-Relying upon repositories that are deprecated or slated to be shutdown can have unintended consequences;
-for example, artifacts being resolved from different artifact server or total breakage of the CI build.</p>
+Relying upon repositories that are deprecated or scheduled to be shutdown can have unintended consequences;
+for example, artifacts being resolved from a different artifact server or a total failure of the CI build.</p>
 
 <p>When artifact repositories are left unmaintained for a long period of time, vulnerabilities may emerge.
 Theoretically, this could allow attackers to inject malicious code into the artifacts that you are resolving and infect build artifacts
diff --git a/java/ql/src/Security/CWE/CWE-1104/MavenPomDependsOnBintray.ql b/java/ql/src/Security/CWE/CWE-1104/MavenPomDependsOnBintray.ql
@@ -1,6 +1,6 @@
 /**
  * @name Depending upon JCenter/Bintray as an artifact repository
- * @description JCenter & Bintray are deprecated
+ * @description Using a deprecated artifact repository may eventually give attackers access for a supply chain attack.
  * @kind problem
  * @problem.severity error
  * @precision very-high
