[Search] Tweak the styling for the first-run experience

chrome/app/chromium_strings.grd

 <?xml version="1.0" encoding="UTF-8"?>
 <!-- This file contains definitions of strings that are distribution specific.
 These strings will not be translated and only english versions will
 be available for now. -->
 
 <grit base_dir="." latest_public_release="0" current_release="1"
       source_lang_id="en" enc_check="möl">
   <outputs>
     <output filename="grit/chromium_strings.h" type="rc_header">
       <emit emit_type='prepend'></emit>
@@ skipping 1184 matching lines @@
         </message>
         <message name="IDS_INBOUND_MDNS_RULE_DESCRIPTION" desc="The description of the firewall rule allowing inbound mDNS traffic.">
           Inbound rule for Chromium to allow mDNS traffic.
         </message>
         <message name="IDS_INBOUND_MDNS_RULE_DESCRIPTION_CANARY" desc="The description of the firewall rule allowing inbound mDNS traffic canary.">
           Inbound rule for Chromium to allow mDNS traffic.
         </message>
       </if>
 
       <!-- Contextual Search -->
+      <message name="IDS_CONTEXTUAL_SEARCH_HEADER" desc="Header shown at the top of the first run experience, to describe the Contextual Search feature.">
+        Search with one touch
+      </message>
       <message name="IDS_CONTEXTUAL_SEARCH_PROMO_DESCRIPTION" desc="Description of the Contextual Search feature.">
-        “Touch to Search” provides an easy way to search for terms on a web page by simply touching on them.  The touched word and surrounding page will be sent to Google.
+        Using “Touch to Search” you can touch any word on a website to learn more about a topic. Chromium will send that word and the surrounding contents to Google and bring back relevant information about it.

[huangs, 2014/09/11 20:52:29]

Grammar: does the information refer to "that word" or "that word and the
surrounding contents"?  If latter, then should be "information about them.".

[huangs, 2014/09/11 20:52:29]

Note the usage of fancy quotation mark (left and right).  Maybe these should be
escaped?

[Mathieu, 2014/09/11 20:59:55]

It works well in the UI!

[Mathieu, 2014/09/11 20:59:55]

information about the topic? UI people have vetted the string. Will ask them and
possibly change in a follow-up.

[donnd, 2014/09/11 21:24:09]

I agree -- it's information about the topic -- I single search term that gets
identified by this process.  The surrounding contents help identify the topic
but are essentially ignored afterwards.

       </message>
       <message name="IDS_CONTEXTUAL_SEARCH_PROMO_OPTIN" desc="Text for the button the user clicks to opt in.">
-        Yes, please
+        Accept &amp; Search
       </message>
       <message name="IDS_CONTEXTUAL_SEARCH_PROMO_OPTOUT" desc="Text for the button the user clicks to opt out.">
-        No, thanks
+        No thanks

[huangs, 2014/09/11 20:52:29]

NIT: Capitalization of "Search" and "thanks" inconsistent.

[Mathieu, 2014/09/11 20:59:55]

they are shown in CAPS in the UI, so not an issue. Still changed it.

       </message>
 
       <!-- Update bubble -->
       <message name="IDS_REINSTALL_APP" desc="Text for the button the user clicks to reinstall the app.">
         Reinstall Chromium
       </message>
       <if expr="use_titlecase">
         <message name="IDS_UPGRADE_BUBBLE_MENU_ITEM" desc="In Title Case: Text for the Chrome menu option replacing Update required.">
           Chromium is Out of Date
         </message>
@@ skipping 55 matching lines @@
           Chromium updates automatically so you always have the freshest version. When this download completes, Chromium will restart and you'll be on your way.
         </message>
         <message name="IDS_EULA_SCREEN_ACCESSIBLE_TITLE" desc="Title to be spoken on opening the OOBE EULA screen">
           Chromium OS terms
         </message>
       </if>
 
     </messages>
   </release>
 </grit>