Apply suggestions from code review

Co-authored-by: Cody Maffucci <46459665+Maffooch@users.noreply.github.com>

Author: Maffooch

docs/content/releases/pro/ddorch-database.md

@@ -18,7 +18,7 @@ This guide walks through adding `dojodb-ddorch` to an existing self-hosted Postg
 - `listen_addresses` in `postgresql.conf` is already configured for remote access.
 - You have upgraded to the release that ships the `ddorch` and `ddorch-workers` services.
 
-> **A note on the database name:** `dojodb-ddorch` contains a hyphen, so it must be double-quoted in every SQL statement (`"dojodb-ddorch"`). If you prefer to avoid the quoting, use `dojodb_ddorch` (underscore) and drop the quotes throughout the rest of this guide.
+> **A note on the database name:** `dojodb-ddorch` contains a hyphen, so it must be double-quoted in every SQL statement (`"dojodb-ddorch"`).
 
 ## Part 1: Provision the Database
 
@@ -179,8 +179,7 @@ docker compose logs ddorch-workers --tail=50
 Finally, confirm the main Django container can reach the orchestrator. From the `dojo` container:
 
 ```bash
-docker compose exec dojo curl -kf https://ddorch:9871/health
-                                                    ^^^ PAUL CONFIRM THIS IS REAL
+docker compose exec -u root dojo bash -c "apt update && apt install curl -y && echo -e '\n\nReady if 200 is returned\n' && curl -kf -w "%{http_code}" https://ddorch:9871/readyz"
 ```
 
 A `200 OK` response confirms the orchestrator is healthy and the main app can talk to it. Your installation is now using the new `dojodb-ddorch` database.