Skip to content

Commit

Permalink
Apply suggestions from code review
Browse files Browse the repository at this point in the history
Co-authored-by: Harry <[email protected]>
  • Loading branch information
shaneutt and hbagdi authored Aug 23, 2021
1 parent c7bb1d6 commit 013627a
Showing 1 changed file with 3 additions and 3 deletions.
6 changes: 3 additions & 3 deletions site-src/v1alpha2/guides/tcp.md
Original file line number Diff line number Diff line change
Expand Up @@ -10,7 +10,7 @@ distribute the traffic with the following rules:
`my-bar-service` Kubernetes Service.

In this example two `TCP` listeners will be applied to the [Gateway][gateway]
in order to route them to two separate backend `TCPRoutes`, note that the
in order to route them to two separate `TCPRoute` resources. Note how the
`protocol` set for the `listeners` on the `Gateway` is `TCP`:

```
Expand Down Expand Up @@ -39,9 +39,9 @@ This corresponds directly with the `name` in the `listeners` in the `Gateway`:
port: 8090
```

In this way each `TCPRoute` "attaches" itself to a different port on the
In this way each `TCPRoute` "attaches" itself to a port on the
`Gateway` so that the service `my-foo-service` is taking traffic for port `8080`
from outside the cluster and `my-bar-service` takes the port `8090` traffic.
and `my-bar-service` takes the port `8090` traffic.

## Alternatives: TCP Traffic Routing Using Metadata

Expand Down

0 comments on commit 013627a

Please sign in to comment.