Update ChromeShell -> ChromePublic in Android Test Instructions.

docs/android_test_instructions.md

 # Android Test Instructions
 
 Device Setup Tests are runnable on physical devices or emulators. See the
 instructions below for setting up either a physical device or an emulator.
 
 [TOC]
 
 ## Physical Device Setup **ADB Debugging**
 
 In order to allow the ADB to connect to the device, you must enable USB
@@ skipping 77 matching lines @@
 by the Android SDK. When doing so, be sure to enable GPU emulation in hardware
 settings, since Chromium requires it to render.
 
 ## Building Tests
 
 It may not be immediately obvious where your test code gets compiled to, so here
 are some general rules:
 
 *  If your test code lives under /content, it will probably be built as part of
    the content\_shell\_test\_apk * If your test code lives under /chrome (or
-   higher), it will probably be built as part of the chrome\_shell\_test\_apk *
+   higher), it will probably be built as part of the chrome\_public\_test\_apk *
    (Please fill in more details here if you know them).
 
-   NB: We used to call the chrome\_shell\_test\_apk the
+   NB: We used to call the chrome\_public\_test\_apk the
    chromium\_shell\_test\_apk. There may still be references to this kicking
    around, but wherever you see chromium\_shell\_test you should replace with
-   chrome\_shell\_test.
+   chrome\_public\_test.
 
 Once you know what to build, just do it like you normally would build anything
-else, e.g.: `ninja -C out/Release chrome_shell_test_apk`
+else, e.g.: `ninja -C out/Release chrome_public_test_apk`
 
 ## Running Tests
 
 All functional tests are run using `build/android/test_runner.py`.
 Tests are sharded across all attached devices. In order to run tests, call:
 `build/android/test_runner.py <test_type> [options]`
 For a list of valid test types, see `test_runner.py --help`. For
 help on a specific test type, run `test_runner.py <test_type> --help`.
 
 The commands used by the buildbots are printed in the logs. Look at
@@ skipping 65 matching lines @@
 ninja -C out/Release content_shell_test_apk
 
 # Install the code under test
 build/android/adb_install_apk.py out/Release/apks/ContentShell.apk
 
 # Run the test (will automagically install the test APK)
 build/android/test_runner.py instrumentation --test-apk=ContentShellTest \
 --isolate-file-path content/content_shell_test_apk.isolate --release -vv
 ```
 
-ChromeShell tests:
+ChromePublic tests:
 
 ```shell
 # Build the code under test
-ninja -C out/Release chrome_shell_apk
+ninja -C out/Release chrome_public_apk
 
 # Build the tests themselves
-ninja -C out/Release chrome_shell_test_apk
+ninja -C out/Release chrome_public_test_apk
 
 # Install the code under test
-build/android/adb_install_apk.py out/Release/apks/ChromeShell.apk
+build/android/adb_install_apk.py out/Release/apks/ChromePublic.apk
 
 # Run the test (will automagically install the test APK)
-build/android/test_runner.py instrumentation --test-apk=ChromeShellTest \
---isolate-file-path chrome/chrome_shell_test_apk.isolate --release -vv
+build/android/test_runner.py instrumentation --test-apk=ChromePublicTest \
+--isolate-file-path chrome/chrome_public_test_apk.isolate --release -vv
 ```
 
 AndroidWebView tests:
 
 ```shell
 ninja -C out/Release android_webview_apk
 ninja -C out/Release android_webview_test_apk
 build/android/adb_install_apk.py out/Release/apks/AndroidWebView.apk \
 build/android/test_runner.py instrumentation --test-apk=AndroidWebViewTest \
 --test_data webview:android_webview/test/data/device_files --release -vvv
@@ skipping 35 matching lines @@
 See
 https://sites.google.com/a/chromium.org/dev/developers/testing/webkit-layout-tests
 
 ## Running GPU tests
 
 (e.g. the "Android Debug (Nexus 7)" bot on the chromium.gpu waterfall)
 
 See http://www.chromium.org/developers/testing/gpu-testing for details. Use
 --browser=android-content-shell. Examine the stdio from the test invocation on
 the bots to see arguments to pass to src/content/test/gpu/run\_gpu\_test.py.