* Use https links

Use https links for caniuse.com

* Use https link

Use https link for nvlpubs.nist.gov

* Fix dead link

* Use https links

Use https links for nvlpubs.nist.gov and social.technet.microsoft.com. Remove redirect for social.technet.microsoft.com

* Replace dead link

* fix fpki faq on certificates page 

changed the links to point to fpki.idmanagement.gov pages
updated to show that the mozilla application has been closed
minor nit:  there are non-USG operated publicly trusted root CAs that still create valid paths in some trust stores to federal pki issued certs.  whether this is desirable or intentional is not addressed.

* remove mozilla paragraph altogether

The origin-when-cross-origin Referrer-policy HTTP header (and meta tag) limits referrer information whether or not the request downgrades the URL scheme (https-to-http vs https-to-https; see examples at https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Referrer-Policy#Directives). The existing language seems to imply that a third-party website that upgrades to HTTPS can expect to receive resource URLs in their referrers after they update to HTTPS, which is not the case.

Here I propose new language to clarify what third parties should expect from the recommended referrer policy.

- For the question of limiting which CAs can issue, there is now a much
  more responsive answer made possible by CAA.
- Split out CT into a separate question on how to monitor / detect
  issuance.
- Update CT language to reflect that CT is now mandatory in Chrome for
  new certificates.

EV certificates no longer have the organization name generally appear in the browser bar.

* update gulp to v4 and node to v12

* update bundler to 2.2

* emptying file

* 2nd try

* 3rd try - 12

* trying again

* Create .bundler-version