fixups

docs/features/network-mapping-network-policies/reference/README.mdx

@@ -32,10 +32,10 @@ spec:
 
 When a ClientIntent is specified utilizing DNS identifiers, such as domain names, it initiates a sequence of operations to integrate the relevant IP addresses into the respective NetworkPolicies.
 
-1. The NetworkMapper incorporates a DNS cache layer, which identifies and archives all resolved DNS records alongside their corresponding IPv4 and IPv6 IP addresses.
+1. The Network Mapper incorporates a DNS cache layer, which identifies and archives all resolved DNS records alongside their corresponding IPv4 and IPv6 IP addresses.
 2. Without a ClientIntent associated with the given domain or its related IP addresses, Otterize will propose a policy tailored to the observed traffic.
 3. Upon the application of a ClientIntent with a domain name present in the cache, the NetworkMapper dynamically updates the intent’s `status` section at one-second intervals with any newly identified IP addresses. It is important to note that Otterize retains all previously identified IP addresses to ensure backward compatibility.
-4. The IntentOperator reviews changes within the `status` section and amends the associated NetworkPolicy to include these newly discovered IP addresses.
+4. The Intents Operator reviews changes within the `status` section and amends the associated NetworkPolicy to include these newly discovered IP addresses.
 
 
 

docs/features/network-mapping-network-policies/tutorials/k8s-egress-access-control-tutorial.mdx

@@ -1,6 +1,6 @@
 ---
 sidebar_position: 5
-title: Egress Network Policy Automation
+title: Egress NetworkPolicy Automation
 image: /img/quick-tutorials/egress-access-control/social.png
 ---