Update peering-via-cr.md

docs/advanced/peering/peering-via-cr.md

@@ -1,6 +1,6 @@
 # Declarative peering
 
-Declarative peering is supported starting from Liqo 1.0, which means that you can create a set of CRs describing the peering with a remote cluster, which is automatically set up once the CRs are applied on both sides.
+Declarative peerings are supported starting from Liqo 1.0, which means that you can create a set of CRs describing the peering with a remote cluster, which is automatically set up once the CRs are applied on both sides.
 This simplifies automation, GitOps and continuous delivery: for example, you might have your Git repository with the manifests describing the peerings, and an instance of [ArgoCD](https://argo-cd.readthedocs.io) which synchronizes the changes on the clusters, creating and destroying the peerings.
 
 The following lines analizes how to describe the configuration of each of the Liqo modules:
@@ -11,7 +11,8 @@ The following lines analizes how to describe the configuration of each of the Li
 
 ## Tenant namespace
 
-Before starting to configure the peerings, you will always need to create a tenant namespace in both clusters that you need to peer, **that refers to the peering with a specific cluster**, one for each peering.
+Before starting to configure the peerings, you need to create a tenant namespace in both clusters that you need to peer.
+This tenant namespace must **refer to the peering with a specific cluster**, hence a distinct tenant namespace must be created per each peering.
 **All the resources needed to configure the peering must be created in those namespaces**.
 A tenant namespace **can have an arbitrary name**, but **it must have the following labels**: