X-Git-Url: https://gerrit.o-ran-sc.org/r/gitweb?a=blobdiff_plain;f=docs%2Finstallation-guides.rst;fp=docs%2Finstallation-guides.rst;h=6f734a0fa68856df64970fd036aac10a2cde1e8b;hb=cb200338a3fb842c9500a9e8b3f36a2e72db0bb2;hp=f451c81bab8061a1d7687d5efc74396034c0cebe;hpb=c22d1ce8663b9e6c04e9683ab223a38a7a06c913;p=it%2Fdep.git

diff --git a/docs/installation-guides.rst b/docs/installation-guides.rst
index f451c81b..6f734a0f 100644
--- a/docs/installation-guides.rst
+++ b/docs/installation-guides.rst
@@ -51,7 +51,9 @@ The following diagram depicts the installation architecture.
 .. image:: images/nrtric-amber.png
    :width: 600
 
-Within the RIC cluster, Kubernetes resources are deployed using three name spaces: ricinfra, ricplt, and ricxapp.  Similarly, within the AUX cluster, Kubernetes resources are deployed using two name spaces: ricinfra, and ricaux.
+Within the RIC cluster, Kubernetes resources are deployed using three name spaces: ricinfra, ricplt,
+and ricxapp.  Similarly, within the AUX cluster, Kubernetes resources are deployed using two name spaces:
+ricinfra, and ricaux.
 
 For each cluster, there is a Kong ingress controller that proxies incoming API calls into the cluster.
 With Kong, service APIs provided by Kubernetes resources can be accessed at the cluster node IP and