diff --git a/src/content/getting-started/architecture/route-agent/_index.en.md b/src/content/getting-started/architecture/route-agent/_index.en.md
index d6ecee456..8171ed8e6 100644
--- a/src/content/getting-started/architecture/route-agent/_index.en.md
+++ b/src/content/getting-started/architecture/route-agent/_index.en.md
@@ -43,8 +43,8 @@ For Submariner 0.15 and below refer [network plugin syncer](../networkplugin-sy
With OVN we can have two deployment models,
{{% notice info %}}
-The Submariner automatically chooses the mode based on the deployment and this is not a
-configuration option in Submariner
+Submariner automatically discovers the OVN mode and uses the appropriate implementation and this is
+not a configuration option in Submariner
{{% /notice %}}
### Single Zone
@@ -52,13 +52,13 @@ configuration option in Submariner
A single-zone deployment involves a single OVN database and a set of master nodes that
program it.
-Here, Submariner configures the ovn_cluster_router to route traffic to other clusters through the
-ovn-k8s-mp0 interface of the gateway node, effectively bridging it to the host networking
-stack of the gateway node. Since ovn_cluster_router is distributed, this route also ensures
-that traffic from non-gateway node is directed to gateway node.
+Here, Submariner configures the `ovn_cluster_router` to route traffic to other clusters through the
+`ovn-k8s-mp0` interface of the gateway node, effectively bridging it to the host networking
+stack of the gateway node. Since `ovn_cluster_router` is distributed, this route also ensures
+that traffic from non-gateway node is directed to local gateway node.
The traffic that comes through Submariner tunnel from remote cluster to gateway node will be
-directed to ovn-k8s-mp0 interface through host routes and will be handled by ovn_cluster_router.
+directed to `ovn-k8s-mp0` interface through host routes and will be handled by `ovn_cluster_router`.
@@ -75,7 +75,7 @@ Submariner takes action by adding a route that directs traffic to remote cluster
it through the transit switch IP of the gateway node.
The host networking rules remain consistent across all nodes. They guide traffic towards the
-ovn_cluster_router specific to that zone, leveraging ovn-k8s-mp0. The ovn_cluster_router, in
+`ovn_cluster_router` specific to that zone, leveraging `ovn-k8s-mp0`. The `ovn_cluster_router`, in
turn, guarantees that the traffic is directed through the Submariner tunnel via the gateway
node.
diff --git a/src/static/images/ovn-kubernetes/ovn-with-ic.svg b/src/static/images/ovn-kubernetes/ovn-with-ic.svg
index 4deccce5d..5eb1aa83a 100644
--- a/src/static/images/ovn-kubernetes/ovn-with-ic.svg
+++ b/src/static/images/ovn-kubernetes/ovn-with-ic.svg
@@ -1 +1 @@
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/src/static/images/ovn-kubernetes/ovn-without-ic.svg b/src/static/images/ovn-kubernetes/ovn-without-ic.svg
index 5988cd3ac..45d06917c 100644
--- a/src/static/images/ovn-kubernetes/ovn-without-ic.svg
+++ b/src/static/images/ovn-kubernetes/ovn-without-ic.svg
@@ -1 +1 @@
-
\ No newline at end of file
+
\ No newline at end of file