edits & todos

docs/quickstart/visualization/postgresql.mdx

@@ -149,12 +149,14 @@ create an Otterize database integration and configure it with your GCP project a
 - Click <b>Add</b> to finish setting up your database integration
 
 At this point, Otterize's database integration will start collecting visibility logs from your Pub/Sub topic,
-and view them in your [Access Graph](https://app.staging.otterize.com/access-graph).
+and view them in the [Access graph](https://app.otterize.com/access-graph).
 
 If you deployed the dummy postgres application used earlier in this tutorial,
 you should start seeing connections from the psql-client app to your Cloud SQL server after about one minute.
 
-[//]: # (TODO: Better screenshots + update with latest unknown node design)
+:::danger
+(TODO: Better screenshots + update with latest unknown node design)
+:::
 
 ![Access Graph with Unknown Node](/img/visualization/postgresql-visibility/access-graph-unknown-node.png)
 ![Client Node for Unknown Service](/img/visualization/postgresql-visibility/access-graph-unknown-client-node.png)
@@ -179,24 +181,26 @@ kubectl patch cronjob psql-client -n otterize-tutorial-postgresql-visibility -p
   '{"spec": {"jobTemplate": {"spec": {"template": {"metadata": {"annotations": {"credentials-operator.otterize.com/user-password-secret-name": "psql-credentials"}}}}}}}'
 ```
 
-- Apply a ClientIntents custom resource definition for the psql client application, allowing all access to the Cloud SQL DB
+- Apply a ClientIntents resource for the psql client application, allowing all access to the Cloud SQL DB:
 ```shell
 kubectl apply -f ${ABSOLUTE_URL}/code-examples/postgresql-visibility/psql-client-clientintents.yaml -n otterize-tutorial-postgresql-visibility
 ```
 
 You should now see the access graph updated with an edge connecting the psql-client app to your Cloud SQL server:
+:::danger
+Please update with new screenshots (that don't include your name, but look like official Otterize)
+:::
 
 ![Access Graph with Known Node](/img/visualization/postgresql-visibility/access-graph-known-node.png)
 
 Click on the psql-client node to see Otterize's suggestion about applying least privilege ClientIntents for it, based on
 the discovered traffic seen from your audit logs:
+:::danger
+Please update with new screenshots (that don't include your name, but look like official Otterize)
+:::
 ![Client Node for Known Service](/img/visualization/postgresql-visibility/access-graph-known-client-node.png)
 
 
-## What's next
-
-[//]: # (TODO: link to a blogpost? )
-
 ## Teardown
 
 To remove the deployed examples: