edits

versioned_docs/version-1.3.0/overview/architecture.mdx

@@ -8,20 +8,20 @@ extensible framework to build flat overlay networks across heterogeneous Kuberne
 KubeSlice enables and simplifies pod-to-pod communications for L3-L7 protocols across a fleet 
 of clusters by using a construct called **Slice**. Each slice can be associated with a set of 
 clusters with varying topologies and can be associated with one or more namespaces in each 
-cluster. The pods in the Slice namespaces can reach each other over the Slice specific flat 
+cluster. The pods in the slice namespaces can reach each other over the slice-specific flat 
 overlay network. It can also be described as an application-specific VPC that spans across 
-clusters. KubeSlice allows creating multiple Slices across clusters with each slice having a 
+clusters. KubeSlice allows creating multiple slices across clusters with each slice having a 
 dedicated set of namespaces in each associated cluster. It enables easy segmentation and 
 isolation of applications using slices. It allows namespace-sameness across the associated 
 clusters in a slice. KubeSlice brings with it software-defined, highly-available and secure 
 connections across clusters using VPN gateways.
 
 KubeSlice can also be used to enable service discovery and reachability across clusters. 
-KubeSlice enables service discovery across the Slice using Service Exports and Imports in 
-each cluster. A Slice associated namespace service running in a cluster can be exported over 
+KubeSlice enables service discovery across the slice using Service Exports and Imports in 
+each cluster. A slice-associated namespace service running in a cluster can be exported over 
 the slice overlay network so that it is discovered and reached by pods running in other 
-clusters associated with the Slice. SliceDNS in each cluster can be used for FQDN based 
-inter-cluster service-service communications across the Slice. Slice DNS has service entries 
+clusters associated with the slice. SliceDNS in each cluster can be used for FQDN based 
+inter-cluster service-service communications across the slice. Slice DNS has service entries 
 with overlay network IP addresses for service endpoints.
 
 The KubeSlice architecture consists of several components that interact with each other to