Use HTTPS links for Google domains in docs

docs/piranha_plant.md

 # Piranha Plant
 
 Piranha Plant is the name of a project, started in November 2013, that aims to
 deliver the future architecture of MediaStreams in Chromium.
 
 Project members are listed in the
 [group for the project](https://groups.google.com/a/chromium.org/forum/#!members/piranha-plant).
 
 The Piranha Plant is a monster plant that has appeared in many of the Super
 Mario games. In the original Super Mario Bros, it hid in the green pipes and is
@@ skipping 28 matching lines @@
 1.  Make life easier for Chromium developers using MS.
 1.  Balance concerns and priorities of the different teams that are or will be
     using MS in Chromium.
 1.  Do the above without hurting our ability to produce the WebRTC.org
     deliverables, and without hurting interoperability between Chromium and
     other software built on the WebRTC.org deliverables.
 
 ## Deliverables
 
 1.  Project code name: Piranha Plant.
-1.  A [design document](http://www.chromium.org/developers/design-documents/idealized-mediastream-design)
+1.  A [design document](https://www.chromium.org/developers/design-documents/idealized-mediastream-design)
     for the idealized future design (work in progress).
 1.  A document laying out a plan for incremental steps to achieve as much of the
     idealized design as is pragmatic. See below for current draft.
 1.  A [master bug](https://crbug.com/323223) to collect all existing and
     currently planned work items:
 1.  Sub-bugs of the master bug, for all currently known and planned work.
 1.  A document describing changed and improved team policies to help us keep
     improving code quality (e.g. naming, improved directory structure, OWNERS
     files). Not started.
 
@@ skipping 24 matching lines @@
     *   Switch to a push model for received PeerConnection audio.
 *   Video
     *   [perkj] Add a Chrome-side interface representing a sink for a video
         track.
     *   [perkj] Add a Content API where given a video WebMediaStreamTrack, you
         can register as a sink for that track.
     *   Add a Chrome-side adapter for libjingle’s video track interface, which
         may also need to change.
     *   Implement a Chrome-side VideoSource and constraints handling (currently
         in libjingle).