Apply suggestions from code review

Co-authored-by: John Krug <[email protected]> Signed-off-by: Víctor Cuadrado Juan <[email protected]>
kubewarden · Jul 26, 2024 · 32844af · 32844af
1 parent 25f2007
commit 32844af
Show file tree

Hide file tree

Showing 2 changed files with 3 additions and 4 deletions.
diff --git a/docs/howtos/telemetry/20-tracing-qs.md b/docs/howtos/telemetry/20-tracing-qs.md
@@ -329,6 +329,6 @@ as there is a new service `kubewarden-policy-server` listed in the UI:
 
 The Jaeger collector is properly receiving the traces generated by our PolicyServer.
 
-For accessing the Jaeger UI, you can use create an ingress or use
+To access the Jaeger UI, you can create an ingress or use
 `kubectl -n jaeger port-forward service/my-open-telemetry-query 16686`
-And go to [localhost:16686](localhost:16686).
+then go to [localhost:16686](localhost:16686).
diff --git a/docs/howtos/telemetry/30-metrics-qs.md b/docs/howtos/telemetry/30-metrics-qs.md
@@ -34,7 +34,7 @@ Prometheus community Helm chart.
 Let's create a `kube-prometheus-stack-values.yaml` file with the
 following contents:
 
-````yaml
+```yaml
 ---
 prometheus:
   additionalServiceMonitors:
@@ -252,5 +252,4 @@ variable to match the name of the desired policy.
 You should be able to see the dashboard similar to this:
 
 ![Dashboard](/img/grafana_dashboard.png)
-````