diff --git a/doc/roles/index.md b/doc/roles/index.md
index ef9f3bf61dcdc376bc3a5175784becf776e57a2b_ZG9jL3JvbGVzL2luZGV4Lm1k..4facc0da6e1640ba601f10a009de26f5cbe1e9e8_ZG9jL3JvbGVzL2luZGV4Lm1k 100644
--- a/doc/roles/index.md
+++ b/doc/roles/index.md
@@ -80,6 +80,5 @@
 
 - **geo_primary_role** (`gitlab-ee`)
 
-  Prepares the database for streaming replication to the secondary site.
-  Prevents automatic upgrade of PostgreSQL to avoid unintended downtime.
+  This role:
 
@@ -85,4 +84,6 @@
 
-  This role is only needed on the Geo primary site's nodes running PostgreSQL.
-  Undesired services will need to be explicitly disabled in `/etc/gitlab/gitlab.rb`.
+  - Configures a single-node PostgreSQL database as a leader for streaming replication.
+  - Prevents automatic upgrade of PostgreSQL since it requires downtime of streaming replication to Geo secondary sites.
+  - Enables all single-node GitLab services including NGINX, Puma, Redis, and Sidekiq. If you are segregating services, then you must explicitly disable unwanted services in `/etc/gitlab/gitlab.rb`. Therefore, this role is only useful on a single-node PostgreSQL in a Geo primary site.
+  - Cannot be used to set up a PostgreSQL cluster in a Geo primary site. Instead, see [Geo multi-node database replication](https://docs.gitlab.com/ee/administration/geo/setup/database.html#multi-node-database-replication).
 
@@ -88,8 +89,5 @@
 
-  This role should not be used to set up a PostgreSQL cluster in a Geo primary
-  site. Instead, see [Geo multi-node database replication](https://docs.gitlab.com/ee/administration/geo/setup/database.html#multi-node-database-replication).
-
-  *By default, enables all of the GitLab standard single node services. (NGINX, Puma, Redis, Sidekiq, etc)*
+  *By default, enables standard single-node GitLab services including NGINX, Puma, Redis, and Sidekiq.*
 
 - **geo_secondary_role** (`gitlab-ee`)