chore: Review feedback: Drop empty string from doc comments

Signed-off-by: Flynn <[email protected]>

Author: kflynn

apis/v1/gateway_types.go

@@ -299,11 +299,10 @@ type GatewaySpec struct {
 	// meaning it will dynamically and implicitly have Routes (e.g. HTTPRoute)
 	// attached to it, according to the scope configured here.
 	//
-	// If unset (the default), set to an empty string (`""`), or set to None,
-	// the Gateway will not act as a default Gateway; if set, the Gateway will
-	// claim any Route with a matching scope set in its UseDefaultGateway
-	// field, subject to the usual rules about which routes the Gateway can
-	// attach to.
+	// If unset (the default) or set to None, the Gateway will not act as a
+	// default Gateway; if set, the Gateway will claim any Route with a
+	// matching scope set in its UseDefaultGateway field, subject to the usual
+	// rules about which routes the Gateway can attach to.
 	//
 	// Think carefully before using this functionality! While the normal rules
 	// about which Route can apply are still enforced, it is simply easier for

apis/v1/shared_types.go

@@ -248,11 +248,10 @@ type CommonRouteSpec struct {
 	ParentRefs []ParentReference `json:"parentRefs,omitempty"`
 
 	// UseDefaultGateways indicates the default Gateway scope to use for this
-	// Route. If unset (the default), set to an empty string (`""`), or set to
-	// None, the Route will not be attached to any default Gateway; if set, it
-	// will be attached to any default Gateway supporting the named scope,
-	// subject to the usual rules about which Routes a Gateway is allowed to
-	// claim.
+	// Route. If unset (the default) or set to None, the Route will not be
+	// attached to any default Gateway; if set, it will be attached to any
+	// default Gateway supporting the named scope, subject to the usual rules
+	// about which Routes a Gateway is allowed to claim.
 	//
 	// Think carefully before using this functionality! The set of default
 	// Gateways supporting the requested scope can change over time without