Fix further PR comments

Signed-off-by: Nick Young <nick@isovalent.com>

apis/v1beta1/gateway_types.go

@@ -79,13 +79,18 @@ type GatewaySpec struct {
 	// Practically, this means that each listener in a set MUST have a unique
 	// combination of Port, Protocol, and, if supported by the protocol, Hostname.
 	//
-	// Some combinations of port, protocol, and TLS settings are are considered
-	// Core support and MUST be supported by implementations if they support the
-	// associated Route type:
+	// Some combinations of port, protocol, and TLS settings are considered
+	// Core support and MUST be supported by implementations based on their
+	// targeted conformance profile:
+	//
+	// HTTP Profile
 	//
 	// 1. HTTPRoute, Port: 80, Protocol: HTTP
 	// 2. HTTPRoute, Port: 443, Protocol: HTTPS, TLS Mode: Terminate, TLS keypair provided
-	// 3. TLSRoute, Port: 443, Protocol: TLS, TLS Mode: Passthrough
+	//
+	// TLS Profile
+	//
+	// 1. TLSRoute, Port: 443, Protocol: TLS, TLS Mode: Passthrough
 	//
 	// "Distinct" Listeners have the following property:
 	//
@@ -138,7 +143,7 @@ type GatewaySpec struct {
 	// Implementations MAY choose to accept a Gateway with Conflicted
 	// Listeners if they accept a partial Listener set that contains no
 	// Conflicted Listeners. They MUST set a "ListenersNotValid" condition
-	// the Gateway Status when the Gateway contains Conflicted Listeners
+	// on the Gateway Status when the Gateway contains Conflicted Listeners
 	// whether or not they accept the Gateway. That Condition SHOULD clearly
 	// indicate in the Message which Listeners are conflicted.
 	//