Skip to content

Commit dcaf850

Browse files
david-martinXin Huang
andcommitted
Include feedback from gyohuangxin
Co-authored-by: Xin Huang <[email protected]>
1 parent aa38d66 commit dcaf850

File tree

1 file changed

+5
-4
lines changed

1 file changed

+5
-4
lines changed

site-src/index.md

Lines changed: 5 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -96,16 +96,17 @@ standard API.
9696

9797
## What's the difference between Gateway API and an API Gateway?
9898

99-
A Gateway is a networking component that allows data to transfer from one
99+
The concept of a Gateway is a networking component that allows data to transfer from one
100100
network to another network.
101101

102-
An API Gateway is a Gateway that deals more specificially with backend services
102+
An API Gateway is a Gateway implementation that deals more specifically with backend services
103103
and routes client reqeusts to those backend services. Those services expose an
104104
API such as HTTP, REST or some other protocol on top of TCP or UDP.
105105

106106
Gateway API is an interface, or set of resources, that model service networking
107-
in Kubernetes. One of the main resources is a `Gateway`. If you implement
108-
Gateway API, you are a Gateway provider. A `Gateway` resource declares the
107+
in Kubernetes. One of the main resources is a `Gateway`. As a Gateway Provider,
108+
you can implement the Gateway API to model Kubernetes service networking in an
109+
expressive, extensible, and role-oriented way. A `Gateway` resource declares the
109110
Gateway type (or class) to instantiate and its configuration.
110111

111112
Some API Gateways implement Gateway API, while a lot of API Gateways provide

0 commit comments

Comments
 (0)