Address PR comments, minor change

aws · Jun 12, 2024 · 642eed9 · 642eed9
1 parent 112b6b0
commit 642eed9
Show file tree

Hide file tree

Showing 2 changed files with 2 additions and 2 deletions.
diff --git a/docs/api-types/tls-route.md b/docs/api-types/tls-route.md
@@ -9,7 +9,7 @@ This allows you to define and manage end-to-end TLS encrypted traffic routing to
 
 - `TLSRoute` sectionName must refer to an `TLS` protocol listener with `mode: Passthrough` in the parentRefs `Gateway`.
 - `TLSRoute` only supports to have one rule.
-- `TLSRoute` don't support any rule matching condition.
+- `TLSRoute` doesn't support any rule matching condition.
 - The `hostnames` field with exactly one host name is required. This domain name is used as a vpc lattice's Service Name Indication (SNI) match to route the traffic to the correct backend service.
 
 

diff --git a/docs/guides/tls-passthrough.md b/docs/guides/tls-passthrough.md
@@ -4,7 +4,7 @@
 
 ## Install Gateway API TLSRoute CRD
 
-The TLSRoute CRD already included in the helm chart and deployment.yaml, if you are using these 2 methods to install the controller no extra steps are needed.
+The TLSRoute CRD is already included in the helm chart and deployment.yaml, if you are using these 2 methods to install the controller no extra steps needed.
 If you want to install the TLSRoute CRD manually by yourself:
 ```
 # Install CRD