Change UI strings per request of UX team.

chrome/app/google_chrome_strings.grd

Index: chrome/app/google_chrome_strings.grd
diff --git a/chrome/app/google_chrome_strings.grd b/chrome/app/google_chrome_strings.grd
index e6cf9084c236126383d25d196ddc2481fa4a88fb..9f8bfa0b76db2ddffde6f1242c398904fa0fba1c 100644
--- a/chrome/app/google_chrome_strings.grd
+++ b/chrome/app/google_chrome_strings.grd
@@ -920,7 +920,7 @@ Signing in anyway will merge Chrome information like bookmarks, history, and oth
           <ph name="SETTINGS_TITLE">&lt;span jscontent="settingsTitle"&gt;&lt;/span&gt;<ex>Settings</ex></ph>
           &gt;
           <ph name="ADVANCED_TITLE">&lt;span jscontent="advancedTitle"&gt;&lt;/span&gt;<ex>Under the Hood</ex></ph>
-          and deselect &quot;<ph name="NO_PREFETCH_DESCRIPTION">&lt;span jscontent="noNetworkPredictionTitle"&gt;&lt;/span&gt;<ex>Predict network actions to improve page load performance</ex></ph>.&quot;
+          and deselect &quot;<ph name="NO_PREFETCH_DESCRIPTION">&lt;span jscontent="noNetworkPredictionTitle"&gt;&lt;/span&gt;<ex>Prefetch resources to load pages more quickly</ex></ph>.&quot;
           If this does not resolve the issue, we recommend selecting this option
           again for improved performance.
         </message>
@@ -928,7 +928,7 @@ Signing in anyway will merge Chrome information like bookmarks, history, and oth
       <if expr="is_android">
         <message name="IDS_ERRORPAGES_SUGGESTION_NETWORK_PREDICTION_BODY" desc="When a page fails to load, sometimes we suggest disabling predicting network actions.  These are details below a header for Android devices.  Note that on devices without mobile network (3G) capability, the setting is a checkbox, while on other devices, it is a list of three items.  The words _disable_ and _re-enabling_ can be used for both cases.">
           Go to the Chrome menu &gt; Settings &gt; (Advanced) Privacy
-          and disable &quot;Network action predictions.&quot;
+          and disable &quot;Prefetch page resources.&quot;
           If this does not resolve the issue, we recommend re-enabling this option
           again for improved performance.
         </message>