Index: chrome/app/google_chrome_strings.grd |
diff --git a/chrome/app/google_chrome_strings.grd b/chrome/app/google_chrome_strings.grd |
index 2de24322dbb48a3c9ba2004cd64591dd8bd8e59b..ecbf60a9286f5031538f6a09024bc6bfd2f0c0b6 100644 |
--- a/chrome/app/google_chrome_strings.grd |
+++ b/chrome/app/google_chrome_strings.grd |
@@ -197,9 +197,6 @@ Chrome supports. --> |
Your computer is missing some important Windows system files, so Chrome will be unable to function correctly. |
</message> |
</if> |
- <message name="IDS_INSTANT_OPT_IN_TITLE" desc="Title of the instant confirm dialog"> |
- Google Chrome Instant |
- </message> |
<message name="IDS_CERT_ERROR_COMMON_NAME_INVALID_EXTRA_INFO_2" desc="2nd paragraph of extra information for an unsafe common name in an X509 certificate"> |
In this case, the address listed in the certificate does not match the address of the website your browser tried to go to. One possible reason for this is that your communications are being intercepted by an attacker who is presenting a certificate for a different website, which would cause a mismatch. Another possible reason is that the server is set up to return the same certificate for multiple websites, including the one you are attempting to visit, even though that certificate is not valid for all of those websites. Google Chrome can say for sure that you reached <strong><ph name="DOMAIN2">$1<ex>paypal.com</ex></ph></strong>, but cannot verify that that is the same site as <strong><ph name="DOMAIN">$2<ex>www.paypal.com</ex></ph></strong> which you intended to reach. If you proceed, Chrome will not check for any further name mismatches. |
</message> |