After Dylan

Author: RichardHoch

docs/topics/mta-7-installing-web-console-on-openshift.adoc

@@ -41,11 +41,6 @@ To successfully deploy, the {ProductShortName} Operator requires 3 RWO persisten
 |RWO
 |Keycloak back end database
 
-|`pathfinder postgresql`
-|1 GiB
-|RWO
-|Pathfinder back end database
-
 |`cache`
 |100 GiB
 |RWX
@@ -307,11 +302,11 @@ If you are an {ProductShortName} administrator, you can create users in your RHS
 
 Although a user can have more than one role, each role corresponds to a specific persona:
 
-* Administrator: An administrator has all the permissions that architects and migrators have, along with access to some application-wide configuration parameters that other users can consume but cannot change or view. Examples: Git credentials, Maven `settings.xml` files.
+* Administrator: An administrator has all the permissions that architects and migrators have, along with the ability to create some application-wide configuration parameters that other users can consume but cannot change or view. Examples: Git credentials, Maven `settings.xml` files.
 +
 Administrators have complete access to both the *Administration* and *Migration* views. Administrators can perform all actions supported by these views.
 
-* Architect: A technical lead for the migration project that can create and modify applications and information related to them. An architect cannot modify or delete sensitive information, but can consume it. Example: Associate an existing credential to the repository of a specific application.
+* Architect: A technical lead for the migration project who can run assessments and can create and modify applications and information related to them. An architect cannot modify or delete sensitive information, but can consume it. Example: Associate an existing credential to the repository of a specific application.
 
 * Migrator: A user who can analyze applications, but not create, modify, or delete them.
 +