Use HTTPS links for Google domains in docs

docs/ozone_overview.md

 # Ozone Overview
 
 Ozone is a platform abstraction layer beneath the Aura window system that is
 used for low level input and graphics. Once complete, the abstraction will
 support underlying systems ranging from embedded SoC targets to new
 X11-alternative window systems on Linux such as Wayland or Mir to bring up Aura
 Chromium by providing an implementation of the platform interface.
 
 ## Guiding Principles
 
@@ skipping 100 matching lines @@
 
 The recommended way to add your platform to the build is as follows. This walks
 through creating a new ozone platform called `foo`.
 
 1. Fork `chromium/src.git`.
 2. Add your implementation in `ui/ozone/platform/` alongside internal platforms.
 3. Patch `ui/ozone/ozone_extra.gni` to add your `foo` platform.
 
 ## Building with Ozone
 
-### ChromeOS - ([waterfall](http://build.chromium.org/p/chromium.chromiumos/waterfall?builder=Linux+ChromiumOS+Ozone+Builder&builder=Linux+ChromiumOS+Ozone+Tests+%281%29&builder=Linux+ChromiumOS+Ozone+Tests+%282%29&reload=none))
+### ChromeOS - ([waterfall](https://build.chromium.org/p/chromium.chromiumos/waterfall?builder=Linux+ChromiumOS+Ozone+Builder&builder=Linux+ChromiumOS+Ozone+Tests+%281%29&builder=Linux+ChromiumOS+Ozone+Tests+%282%29&reload=none))
 
 To build `chrome`, do this from the `src` directory:
 
 ``` shell
 gn args out/OzoneChromeOS --args="use_ozone=true target_os=\"chromeos\""
 ninja -C out/OzoneChromeOS chrome
 ```
 
 Then to run for example the X11 platform:
 
@@ skipping 21 matching lines @@
 ```
 
 Then to run for example the headless platform:
 
 ``` shell
 ./out/OzoneEmbedded/content_shell --ozone-platform=headless \
                                   --ozone-dump-file=/tmp/
 ```
 
 ### Linux Desktop - ([waterfall](https://build.chromium.org/p/chromium.fyi/builders/Ozone%20Linux/))
-Support for Linux Desktop is currently [in-progress](http://crbug.com/295089).
+Support for Linux Desktop is currently [in-progress](https://crbug.com/295089).
 
 The following targets are currently working:
 
 * various unit tests
 * `chrome`
 
 To build `chrome`, do this from the `src` directory:
 
 ``` shell
 gn args out/OzoneLinuxDesktop --args="use_ozone=true enable_package_mash_services=true"
@@ skipping 53 matching lines @@
 
 ``` shell
 content_shell --ozone-platform=headless \
               --ozone-dump-file=/tmp/
 ```
 
 ### DRM/GBM
 
 This is Linux direct rending with acceleration via mesa GBM & linux DRM/KMS
 (EGL/GLES2 accelerated rendering & modesetting in GPU process) and is in
-production use on [ChromeOS](http://www.chromium.org/chromium-os).
+production use on [ChromeOS](https://www.chromium.org/chromium-os).
 
 Note that all ChromeOS builds of Chrome will compile and attempt to use this.
 See [Building Chromium for Chromium OS](https://www.chromium.org/chromium-os/how-tos-and-troubleshooting/building-chromium-browser) for build instructions.
 
 ### Cast
 
 This platform is used for
 [Chromecast](https://www.google.com/intl/en_us/chromecast/).
 
 ### X11
@@ skipping 49 matching lines @@
 ./out/OzoneCaca/content_shell
 ```
 
   Note: traditional TTYs are not the ideal browsing experience.<br/>
   ![Picture of a workstation using Ozone/caca to display the Google home page in a text terminal](./images/ozone_caca.jpg)
 
 ## Communication
 
 There is a public mailing list:
 [ozone-dev@chromium.org](https://groups.google.com/a/chromium.org/forum/#!forum/ozone-dev)