diff --git a/doc/architecture/blueprints/cells/application-deployment.md b/doc/architecture/blueprints/cells/application-deployment.md
index e941940a7af0a964ee937dad8e0bde071fc206b6..8af7051f06d8132f9760fe2c517ed100f50bad45 100644
--- a/doc/architecture/blueprints/cells/application-deployment.md
+++ b/doc/architecture/blueprints/cells/application-deployment.md
@@ -42,13 +42,12 @@ User ==> R
 R ==> Primary
 R ==> Secondary
 
-Primary --> Secondary : "DB selective replica"
-Secondary --> Primary : "internal API"
+Secondary --> Primary : "Internal API"
 
 @enduml
 ```
 
-As we can see from the diagram, users interact with the system through the router only. Cells communicate with the Primary Cell using internal API calls and have a local copy of all the database rows necessary to operate.
+As we can see from the diagram, users interact with the system through the router only. Secondary Cells communicate with the Primary Cell using internal API and have a local copy of all the database rows necessary to operate.
 
 It is important to note that even if a Secondary Cell supports GitLab Geo out of the box, we will not be able to provide this feature to our users until the Router supports it.