diff --git a/README.md b/README.md
index 23e4146b..c56a3b26 100644
--- a/README.md
+++ b/README.md
@@ -15,7 +15,7 @@ Before deploying Messaging Topology Operator, you need to have:
 If you have [cert-manager](https://cert-manager.io/docs/installation/kubernetes/) `1.2.0` or above installed in your k8s cluster, and `kubectl` configured to access your running k8s cluster, you can then run the following command to install the Messaging Topology Operator:
 
 ```bash
-kubectl apply -f https://github.com/rabbitmq/messaging-topology-operator/releases/latest/download/messaging-topology-operator-with-certmanager.yml
+kubectl apply -f https://github.com/rabbitmq/messaging-topology-operator/releases/latest/download/messaging-topology-operator-with-certmanager.yaml
 ```
 
 You can create RabbitMQ resources:
@@ -30,7 +30,7 @@ You can create RabbitMQ resources:
 ## Install without cert-manager
 
 If you do not have cert-manager installed in your k8s cluster, you will need to generate certificates used by admission webhooks yourself and include them in the operator and webhooks manifests.
-You can follow [this doc](./docs/installation/install-without-certmanager.md). 
+You can follow [this doc](./docs/installation/install-without-certmanager.md).
 
 ## Contributing
 
diff --git a/docs/installation/install-without-certmanager.md b/docs/installation/install-without-certmanager.md
index db22675f..2e38b6f6 100644
--- a/docs/installation/install-without-certmanager.md
+++ b/docs/installation/install-without-certmanager.md
@@ -8,7 +8,7 @@ Before deploying Messaging Topology Operator, you need to have:
 
 ## Installation
 
-Download the latest release manifests https://github.com/rabbitmq/messaging-topology-operator/releases/latest/download/messaging-topology-operator.yml.
+Download the latest release manifests https://github.com/rabbitmq/messaging-topology-operator/releases/latest/download/messaging-topology-operator.yaml.
 
 The Messaging Topology Operator has multiple [admission webhooks](https://kubernetes.io/docs/reference/access-authn-authz/extensible-admission-controllers/). You need to generate the webhook certificate and place it in multiple places in the manifest:
 
@@ -27,10 +27,10 @@ The Messaging Topology Operator has multiple [admission webhooks](https://kubern
       tls.key: # generated key
     ```
     This secret will be mounted to the operator container, where all webhooks will run from.
-1. Add webhook ca certificate in downloaded release manifest `messaging-topology-operator.yml`. There are 6 admission webhooks, one for each CRD type.
+1. Add webhook ca certificate in downloaded release manifest `messaging-topology-operator.yaml`. There are 6 admission webhooks, one for each CRD type.
 Look for keyword `caBundle` in the manifest, and paste the webhook ca cert in there (6 places because there are 6 webhooks).
 1. Now you are ready to deploy. If you have `kubectl` configured to access your running k8s cluster, you can then run:
 
 ```bash
-kubectl apply -f messaging-topology-operator.yml
-```
\ No newline at end of file
+kubectl apply -f messaging-topology-operator.yaml
+```