docs: update the links to the get-the-code page to use the https url

docs/profiling_content_shell_on_android.md

 # Profiling Content Shell on Android
 
 Below are the instructions for setting up profiling for Content Shell on
 Android. This will let you generate profiles for ContentShell. This will require
 linux, building an userdebug Android build, and wiping the device.
 
 [TOC]
 
 ## Prepare your device.
 
 You need an Android 4.2+ device (Galaxy Nexus, Nexus 4, 7, 10, etc.) which you
 don’t mind erasing all data, rooting, and installing a userdebug build on.
 
 ## Get and build `content_shell_apk` for Android
 
 (These instructions have been carefully distilled from the
 [Android Build Instructions](android_build_instructions.md).)
 
 1.  Get the code! You’ll want a second checkout as this will be
     android-specific. You know the drill:
-    http://dev.chromium.org/developers/how-tos/get-the-code
+    https://www.chromium.org/developers/how-tos/get-the-code
 1.  Append this to your `.gclient` file: `target_os = ['android']`
 1.  Create `chromium.gyp_env` next to your `.gclient` file:
     `echo "{ 'GYP_DEFINES': 'OS=android', }" > chromium.gyp_env`
 1.  (Note: All these scripts assume you’re using "bash" (default) as your
     shell.)
 1.  Sync and runhooks (be careful not to run hooks on the first sync):
 
     ```
     gclient sync --nohooks
     . build/android/envsetup.sh
@@ skipping 162 matching lines @@
 
     ```
     adb pull /proc/kallsyms symbols/kallsyms
     ```
 
 1.  Now add --kallsyms to your perfhost\_linux command:
     ```
     ./perfhost_linux report -g -i perf.data --symfs symbols/ \
         --kallsyms=symbols/kallsyms
     ```