Markups.

Author: fasaxc

apis/v1alpha2/clusternetworkpolicy_types.go

@@ -378,7 +378,7 @@ type ClusterNetworkPolicyEgressPeer struct {
 	//
 	// Networks matches both regular IP traffic and ICMP traffic to/from
 	// the specified CIDRs. For example, a Networks entry of "0.0.0.0/0"
-	// will match both IPv4 and ICMP traffic, while "0::/0" will match
+	// will match both IPv4 and ICMP traffic, while "::/0" will match
 	// both IPv6 and ICMPv6 traffic.
 	//
 	// Each item in Networks should be provided in the CIDR format and should be

site-src/api-overview.md

@@ -119,14 +119,11 @@ before policies with higher priority values in the same tier.
 
 ### Rules 
 
-Each CNP should define at least one `Ingress` or `Egress` relevant in-cluster traffic flow
-along with the associated Action that should occur. In each rule the user
-should *at the minimum* define an `Action`, and at least one peer (`To` or `From` entry).
-Optionally the user may also select `Protocols` to filter traffic on and also
-a `Name` for each rule to make management and reporting easier for Admins.
-
-The `Protocols` field supports protocol-specific matching for TCP, UDP, and SCTP
-(including destination port numbers, port ranges, and named ports).
+Each CNP should define at least one `Ingress` or `Egress` relevant in-cluster traffic flow 
+along with the associated Action that should occur. In each rule the user 
+should *at a minimum* define an `Action`, and at least one peer (`To` or `From` entry).
+Optionally the user may also define select `Ports` to filter traffic on and also 
+a name for each rule to make management and reporting easier for Admins.
 
 ### Status