ref(specs): matches -> routes in HTTPRouteGroup

apis/traffic-specs/v1alpha4/traffic-specs.md → apis/traffic-specs/traffic-specs.md

@@ -2,7 +2,7 @@
 
 **API Group:** specs.smi-spec.io
 
-**API Version:** v1alpha4
+**API Version:** v1alpha5-draft
 
 ## Specification
 
@@ -28,7 +28,7 @@ kind: HTTPRouteGroup
 metadata:
   name: the-routes
 spec:
-  matches:
+  routes:
   - name: metrics
     pathRegex: "/metrics"
     methods:
@@ -38,7 +38,7 @@ spec:
     methods: ["*"]
 ```
 
-This example defines two matches, `metrics` and `health`. The name is the
+This example defines two routes, `metrics` and `health`. The name is the
 primary key and all fields are required. A regex is used to match against the
 URI and is anchored (`^`) to the beginning of the URI. Methods can either be
 specific (`GET`) or `*` to match all methods.
@@ -47,15 +47,15 @@ These routes have not yet been associated with any resources. See
 [Traffic Target](/apis/traffic-access/v1alpha3/traffic-access.md) for an example
 of how routes become associated with applications serving traffic.
 
-The `matches` field only applies to URIs and HTTP headers.
+The `routes` field only applies to URIs and HTTP headers.
 
 ```yaml
 kind: HTTPRouteGroup
 metadata:
   name: the-routes
   namespace: default
 spec:
-  matches:
+  routes:
   - name: everything
     pathRegex: ".*"
     methods: ["*"]
@@ -83,7 +83,7 @@ metadata:
   name: the-routes
   namespace: default
 spec:
-  matches:
+  routes:
   - name: android-insiders
     headers:
     - user-agent: ".*Android.*"
@@ -99,7 +99,7 @@ metadata:
   name: the-routes
   namespace: default
 spec:
-  matches:
+  routes:
   - name: android-insiders
     headers:
     - user-agent: ".*Android.*"
@@ -119,7 +119,7 @@ kind: HTTPRouteGroup
 metadata:
   name: the-routes
 spec:
-  matches:
+  routes:
   - name: iphone-users
     pathRegex: "/api/.*"
     methods:
@@ -144,22 +144,20 @@ kind: TCPRoute
 metadata:
   name: the-routes
 spec:
-  matches:
-    ports:
-    - 3306
-    - 6446
+  ports:
+  - 3306
+  - 6446
 ```
 
-When matching ports are not specified,
-the TCP route will match all the ports of a Kubernetes service:
+When matching ports are not specified, the TCP route will match all the ports of
+a Kubernetes service:
 
 ```yaml
 kind: TCPRoute
 metadata:
   name: the-routes
 spec:
-  matches:
-    ports: []
+  ports: []
 ```
 
 ### UDPRoute
@@ -171,22 +169,20 @@ kind: UDPRoute
 metadata:
   name: the-routes
 spec:
-  matches:
-    ports:
-    - 989
-    - 990
+  ports:
+  - 989
+  - 990
 ```
 
-When matching ports are not specified,
-the UDP route will match all the ports of a Kubernetes service:
+When matching ports are not specified, the UDP route will match all the ports of
+a Kubernetes service:
 
 ```yaml
 kind: UDPRoute
 metadata:
   name: the-routes
 spec:
-  matches:
-    ports: []
+  ports: []
 ```
 
 ## Automatic Generation