Fixes a few nits in the deploy guide (quay#1455)

Co-authored-by: Steven Smith <[email protected]>

Author: stevsmit

modules/first-user-api.adoc

@@ -34,10 +34,10 @@ If successful, the command returns an object with the username, email, and encry
 +
 [source,yaml]
 ----
-{"access_token":"6B4QTRSTSD1HMIG915VPX7BMEZBVB9GPNY2FC2ED", "email":"[email protected]","encrypted_password":"<password>","username":"quayadmin"} # gitleaks:allow
+{"access_token":"123456789", "email":"[email protected]","encrypted_password":"<password>","username":"quayadmin"} # gitleaks:allow
 ----
 +
-If a user already exists in the database, an error is returned. For example::
+If a user already exists in the database, an error is returned. For example:
 +
 [source,terminal]
 ----

modules/operator-components-unmanaged.adoc

@@ -2,11 +2,12 @@
 [id="operator-components-unmanaged"]
 = Using unmanaged components for dependencies
 
-Although the {productname} Operator provides an opinionated deployment by automatically managing all required dependencies, this approach may not be suitable for every environment. If you need to integrate existing infrastructure or require specific configurations, you can leverage the Operator to use external, or _unmanaged_, resources instead. An unmanaged component is any core dependency—such as PostgreSQL, Redis, or object storage—that you deploy and maintain outside of the Operator's control.
+Although the {productname} Operator provides an opinionated deployment by automatically managing all required dependencies, this approach might not be suitable for every environment. If you need to integrate existing infrastructure or require specific configurations, you can leverage the Operator to use external, or _unmanaged_, resources instead. An unmanaged component is any core dependency—such as PostgreSQL, Redis, or object storage—that you deploy and maintain outside of the Operator's control.
 
 [NOTE]
 ====
 If you are using an unmanaged PostgreSQL database, and the version is PostgreSQL 10, it is highly recommended that you upgrade to PostgreSQL 13. PostgreSQL 10 had its final release on November 10, 2022 and is no longer supported. For more information, see the link:https://www.postgresql.org/support/versioning/[PostgreSQL Versioning Policy]. 
 ====
-
-For more information about unmanaged components, see. . . 
+////
+For more information about unmanaged components, see. . .
+////

modules/operator-config-bundle-secret.adoc

@@ -12,7 +12,7 @@ The `configBundleSecret` stores the `config.yaml` file. {productname} administra
 * Feature flags
 * Notification settings
 
-{productname} might update this secret for the following reasons:
+{productname} administrators might update this secret for the following reasons:
 
 * Enable a new authentication method
 * Add custom SSL/TLS certificates