diff --git a/docs/troubleshooting.md b/docs/troubleshooting.md
index 45bad692c4474b6fa6eac48e6020cf3c3c783b2f..ef60cfda1e39884eab07f4f0a11086520dc1444b 100644
--- a/docs/troubleshooting.md
+++ b/docs/troubleshooting.md
@@ -16,13 +16,19 @@ Please check the resulting value of the `acme_staging` key in
 are fetched from the [Let's Encrypt staging API](https://letsencrypt.org/docs/staging-environment/),
 which can't be validated by default in your browser.
 
-Are all pods in the `cert-manager` namespace in the `READY` state ?
+Are all cert-manager pods in the `oas` namespace in the `READY` state ?
 
-    cluster$ kubectl -n cert-manager get pods
+    cluster$ kubectl -n oas get pods | grep cert-manager
+
+Are there any `cm-acme-http-solver-*` pods still running, indicating that there
+are unfinished certificate requests ?
+
+    cluster$ kubectl -n oas-apps get pods | grep cm-acme-http-solver
+    cluster$ kubectl -n oas get pods | grep cm-acme-http-solver
 
 Show the logs of the main `cert-manager` pod:
 
-    cluster$ kubectl -n cert-manager logs -l "app.kubernetes.io/name=cert-manager"
+    cluster$ kubectl -n oas logs -l "app.kubernetes.io/name=cert-manager"
 
 You can `grep` for your cluster domain or for any specific subdomain to narrow
 down results.