Use HTTPS links for Google domains in docs

docs/chromoting_android_hacking.md

 # Chromoting Android Hacking
 
 This guide, which is meant to accompany the
 [compilation guide](chromoting_build_instructions.md), explains the process of
 viewing the logs and debugging the CRD Android client. I'll assume you've
 already built the APK as described in the aforementioned guide, that you're in
 the `src/` directory, and that your binary is at
 `out/Release/apks/Chromoting.apk`. Additionally, you should have installed the
 app on at least one (still) connected device.
 
 [TOC]
 
 ## Viewing logging output
 
 In order to access LogCat and view the app's logging output, we need to launch
 the Android Device Monitor. Run `third_party/android_tools/sdk/tools/monitor`
 and select the desired device under `Devices`. Using the app as normal will
 display log messages to the `LogCat` pane.
 
 ## Attaching debuggers for Java code
 
 ### Eclipse
 
-1.  Go to http://developer.android.com/sdk/index.html and click "Download the
+1.  Go to https://developer.android.com/sdk/index.html and click "Download the
     SDK ADT Bundle for Linux"
 1.  Configure eclipse
     1.  Select General > Workspace from the tree on the left.
         1.  Uncheck Refresh workspace on startup (if present)
         1.  Uncheck Refresh using native hooks or polling (if present)
         1.  Disable build before launching
     1.  Select Run/Debug > Launching
         1.  Uncheck Build (if required) before launching
 1. Create a project
     1.  Select File > New > Project... from the main menu.
@@ skipping 113 matching lines @@
 to easily launch GDB. Run
 
 ```shell
 $ build/android/adb_gdb --package-name=org.chromium.chromoting \
 --activity=.Chromoting --start
 ```
 
 Note that if you have multiple devices connected, you must export
 `ANDROID_SERIAL` to select one; set it to the serial number of the desired
 device as output by `$ adb devices`.