Cherrypick release-0.6 --> master (#1523)

* Update order of files in example (#1501)

Updating kubernetes secret creation instruction to correctly show which file should hold which data, ie. certificate on `cert.pem` and private key on `cert.pk`.

* Update link for Knative Install on OpenShift via Operator (#1511)

Author: samodell

docs/install/README.md

@@ -84,7 +84,7 @@ available observability plugins, to minimize the disk space used for install.
 
 - [Knative Install on Docker for Mac](./Knative-with-Docker-for-Mac.md)
 - [Knative Install on OpenShift](./Knative-with-OpenShift.md)
-- [Knative Install on OpenShift via Operator](https://github.com/openshift-cloud-functions/Documentation/blob/master/knative-OCP-4x.md)
+- [Knative Install on OpenShift via Operator](https://github.com/openshift-knative/docs/blob/master/README.md)
 
 **Custom install guide**
 

docs/serving/using-a-tls-cert.md

@@ -154,7 +154,7 @@ To manually add a TLS certificate to your Knative cluster, you create a
 Kubernetes secret and then configure the `knative-ingress-gateway`:
 
 1. Run the following command to create a Kubernetes secret to hold your TLS
-   certificate, `cert.pk`, and the private key, `cert.pem`:
+   certificate, `cert.pem`, and the private key, `cert.pk`:
 
    ```shell
    kubectl create --namespace istio-system secret tls istio-ingressgateway-certs \