File tree Expand file tree Collapse file tree 2 files changed +2
-3
lines changed Expand file tree Collapse file tree 2 files changed +2
-3
lines changed Original file line number Diff line number Diff line change @@ -299,7 +299,7 @@ type GatewaySpec struct {
299
299
// meaning it will dynamically and implicitly have Routes (e.g. HTTPRoute)
300
300
// attached to it, according to the scope configured here.
301
301
//
302
- // If unset or set to the empty string `""` (the default), the Gateway
302
+ // If unset or set to an empty string `""` (the default), the Gateway
303
303
// will not act as a default Gateway; if set, the Gateway will claim any
304
304
// Route with a matching scope set in its UseDefaultGateway field, subject
305
305
// to the usual rules about which routes the Gateway can attach to.
@@ -311,7 +311,7 @@ type GatewaySpec struct {
311
311
// control of the scope (e.g. namespace) with tight controls and checks on
312
312
// what kind of workloads and Routes get added in that scope, we strongly
313
313
// recommend not using this just because it seems convenient, and instead
314
- // stick to explicit Route attachment.
314
+ // stick to direct Route attachment.
315
315
//
316
316
// +optional <gateway:experimental>
317
317
DefaultScope GatewayDefaultScope `json:"defaultScope,omitempty"`
Original file line number Diff line number Diff line change @@ -253,7 +253,6 @@ type CommonRouteSpec struct {
253
253
// appropriate to request a default Gateway for a given Route -- for
254
254
// example, a Route with specific security requirements should almost certainly
255
255
// not use a default Gateway.
256
- // not use a default Gateway.
257
256
//
258
257
// +optional <gateway:experimental>
259
258
UseDefaultGateway GatewayDefaultScope `json:"useDefaultGateway,omitempty"`
You can’t perform that action at this time.
0 commit comments