[M56 merge] Explicitly mention SHA-1 as a possible cause in the weak cert signature interstitial.

components/ssl_errors_strings.grdp

Index: components/ssl_errors_strings.grdp
diff --git a/components/ssl_errors_strings.grdp b/components/ssl_errors_strings.grdp
index b79b74353d7ae40403ae2baab8369e657eb130eb..dbad0b951dc808dc6cf72baf89964e20c911da1a 100644
--- a/components/ssl_errors_strings.grdp
+++ b/components/ssl_errors_strings.grdp
@@ -80,7 +80,7 @@
   </message>
 
   <message name="IDS_CERT_ERROR_WEAK_SIGNATURE_ALGORITHM_DETAILS" desc="Details of the error page for a certificate signed using a weak signature algorithm">
-    You attempted to reach <ph name="DOMAIN">&lt;strong&gt;$1<ex>paypal.com</ex>&lt;/strong&gt;</ph>, but the server presented a certificate signed using a weak signature algorithm. This means that the security credentials the server presented could have been forged, and the server may not be the server you expected (you may be communicating with an attacker). <ph name="BEGIN_LEARN_MORE_LINK">&lt;a href="#" id="learn-more-link"&gt;</ph>Learn more<ph name="END_LEARN_MORE_LINK">&lt;/a&gt;</ph>.
+    You attempted to reach <ph name="DOMAIN">&lt;strong&gt;$1<ex>paypal.com</ex>&lt;/strong&gt;</ph>, but the server presented a certificate signed using a weak signature algorithm (such as SHA-1). This means that the security credentials the server presented could have been forged, and the server may not be the server you expected (you may be communicating with an attacker). <ph name="BEGIN_LEARN_MORE_LINK">&lt;a href="#" id="learn-more-link"&gt;</ph>Learn more<ph name="END_LEARN_MORE_LINK">&lt;/a&gt;</ph>.
   </message>
   <message name="IDS_CERT_ERROR_WEAK_SIGNATURE_ALGORITHM_DESCRIPTION" desc="Description of the error page for a certificate signed using a weak signature algorithm">
     Server's certificate is signed using a weak signature algorithm.