Fix linter errors

Signed-off-by: Sridhar Gaddam <[email protected]>

Author: sridhargaddam

.spelling

@@ -662,12 +662,15 @@ IOPs
 ip
 ipallocate
 ipBlocks
+ipBlock
 IPs
 IPsec
 ipsets
 iptables
 IPv4
 IPv6
+fd16:9254:7127:1337:ffff:ffff:ffff:ffff
+fd16:9254:7127:1337:ffff:ffff:ffff:ffff/128
 ip_address
 Istio
 istio

content/en/docs/ambient/usage/networkpolicy/index.md

@@ -66,7 +66,7 @@ In Istio ambient, this problem is solved by using a combination of iptables rule
 
 This behavior is transparently enabled when you add pods to the ambient mesh, and by default ambient uses the link-local addresses 169.254.7.127 (IPv4) and fd16:9254:7127:1337:ffff:ffff:ffff:ffff (IPv6) to identify and correctly allow kubelet health probe packets.
 
-Note: If your workload, namespace, or cluster enforces Kubernetes `NetworkPolicy`, you must allow both the IPv4 and IPv6 addresses used by Ambient mode. Depending on your CNI, packets with these addresses may otherwise be blocked, which will cause application pod health probes to fail once they join the ambient mesh.
+Note: If your workload, namespace, or cluster enforces Kubernetes `NetworkPolicy`, you must allow both the IPv4 and IPv6 addresses used by ambient mode. Depending on your CNI, packets with these addresses may otherwise be blocked, which will cause application pod health probes to fail once they join the ambient mesh.
 
 For instance, applying the following `NetworkPolicy` in a namespace would block all traffic (Istio or otherwise) to the `my-app` pod, **including** kubelet health probes. Depending on your CNI, kubelet probes and link-local addresses may be ignored by this policy, or be blocked by it:
 
@@ -100,4 +100,4 @@ spec:
           cidr: 169.254.7.127/32
 {{< /text >}}
 
-Note: If you are using a dualStack cluster or an IPv6-only cluster, make sure to update your `NetworkPolicy` with the IPv6 ipBlock (fd16:9254:7127:1337:ffff:ffff:ffff:ffff/128) in addition to, or instead of, the IPv4 entry.
+Note: If you are using a dual-stack cluster or an IPv6-only cluster, make sure to update your `NetworkPolicy` with the IPv6 ipBlock (fd16:9254:7127:1337:ffff:ffff:ffff:ffff/128) in addition to, or instead of, the IPv4 entry.