Apply suggestions from code review

Signed-off-by: Tom Kerkhove <kerkhove.tom@gmail.com>

content/blog/2022-12-12-keda-2.9.0-release.md

@@ -57,19 +57,19 @@ Details on the underlying fixes can be found in the [changelog](https://github.c
 
 There are a number of improvements into the ways KEDA provides operational information in Prometheus and how you can consume it.
 
-For starters, our operator now exposes Prometheus metrics which can be scraped on port `8080` at `/metrics`. It provides the same set of metrics as the metric server (although renamed) offers today, in addition to a few new metrics and the introduction of a `ScalerName` label.
+For starters, **our operator now exposes Prometheus metrics** which can be scraped on port `8080` at `/metrics`. It provides the same set of metrics as the metric server (although renamed) offers today, in addition to a few new metrics and the introduction of a `ScalerName` label.
 
 The metrics are moving given we are changing how KEDA is integrating with external systems so that we can improve the performance and reduce the load on those external systems.
 
-As part of this, we are deprecating the KEDA-specific metrics in our metric server and recommend end-users to use the metrics in the operator. Join our [conversation there](https://github.com/kedacore/keda/discussions/3973).
+As part of this, **we are deprecating the KEDA-specific metrics in our metric server** and recommend end-users to use the metrics in the operator. Join our [conversation there](https://github.com/kedacore/keda/discussions/3973).
 
-Next, we have introduced `keda_resource_totals`and `keda_trigger_totals` that provide insights on your autoscaling landscape and the various autoscaling triggers that are being used.
+Next, we have **introduced `keda_resource_totals` and `keda_trigger_totals` as metrics** that provide insights into your autoscaling landscape and the various autoscaling triggers that are being used.
 
-Metrics are great - But they have to be consumed. That's why we introduced a new Grafana dashboard allows you to easily visualize the KEDA metrics in Grafana to see how your applications are scaling:
+Metrics are great - But they have to be consumed. That's why we **introduced a new Grafana dashboard allows end-users to easily visualize the KEDA metrics in Grafana** to see how your applications are scaling:
 
 ![Grafana Dashboard](/img/blog/v2.9-release/grafana-dashboard.png)
 
-Lastly, end-users using `ScaledJobs` can now see what the minimum replica count is when inspecting resources through the Kubernetes API.
+Lastly, **end-users using `ScaledJobs` can now see what the minimum replica count is when inspecting resources** through the Kubernetes API.
 
 Learn more about our available Prometheus metrics and our Grafana dashboard in our [docs](https://keda.sh/docs/operate/prometheus/).
 
@@ -83,7 +83,7 @@ In this release we have added some additional configuration options for triggers
 
 Azure Key Vault authentication provider now allows end-users to use pod identities for authentication for improved simplicity & security:
 
-```
+```diff
 azureKeyVault:                                          # Optional.
   vaultUri: https://keda.vault.azure.net
 + podIdentity:                                          # Optional.