Use HTTPS links for Google domains in docs

docs/windows_build_instructions.md

 # Checking out and Building Chromium for Windows
 
 There are instructions for other platforms linked from the 
 [get the code](get_the_code.md) page.
 
 ## Instructions for Google Employees
 
 Are you a Google employee? See
 [go/building-chrome](https://goto.google.com/building-chrome) instead.
 
@@ skipping 129 matching lines @@
   configuration](https://www.chromium.org/developers/gn-build-configuration).
   The default will be a debug component build matching the current host
   operating system and CPU.
 * For more info on GN, run `gn help` on the command line or read the
   [quick start guide](../tools/gn/docs/quick_start.md).
 
 ### Using the Visual Studio IDE
 
 If you want to use the Visual Studio IDE, use the `--ide` command line
 argument to `gn gen` when you generate your output directory (as described on
-the [get the code](http://dev.chromium.org/developers/how-tos/get-the-code)
+the [get the code](https://dev.chromium.org/developers/how-tos/get-the-code)
 page):
 
 ```shell
 $ gn gen --ide=vs out\Default
 $ devenv out\Default\all.sln
 ```
 
 GN will produce a file `all.sln` in your build directory. It will internally
 use Ninja to compile while still allowing most IDE functions to work (there is
 no native Visual Studio compilation mode). If you manually run "gen" again you
@@ skipping 66 matching lines @@
 $ gclient sync
 ```
 
 The first command updates the primary Chromium source repository and rebases
 any of your local branches on top of tip-of-tree (aka the Git branch `origin/master`).
 If you don't want to use this script, you can also just use `git pull` or 
 other common Git commands to update the repo.
 
 The second command syncs the subrepositories to the appropriate versions and
 re-runs the hooks as needed.