Skip to content

Commit d69cf30

Browse files
committed
attempt to fix netlify
1 parent e8bd4b1 commit d69cf30

File tree

1 file changed

+2
-4
lines changed
  • content/en/blog/_posts/2023-10-18-gateway-api-time-to-switch-i2gw

1 file changed

+2
-4
lines changed

content/en/blog/_posts/2023-10-18-gateway-api-time-to-switch-i2gw/index.md

Lines changed: 2 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -82,9 +82,7 @@ intended for use in cases where you want to inspect the HTTP stream and use HTTP
8282
either routing or modification, for example using HTTP Headers for routing, or modifying them
8383
in-flight.
8484

85-
{{< figure src="gateway-api-resources.svg" alt="Diagram showing the APIs that make up Gateway and
86-
how they relate to each other. The APIs shown are GatewayClass, Gateway, and HTTPRoute; the Service
87-
API is also shown" caption="The APIs that make up Gateway" class="diagram-medium" >}}
85+
{{< figure src="gateway-api-resources.svg" alt="Diagram showing the APIs that make up Gateway and how they relate to each other. The APIs shown are GatewayClass, Gateway, and HTTPRoute; the Service API is also shown" caption="The APIs that make up Gateway" class="diagram-medium" >}}
8886

8987
### Portability
9088

@@ -181,7 +179,7 @@ manage the ecosystem. It is also likely to receive more updates and community su
181179

182180
### The Road Ahead
183181

184-
Ingress2gateway is just getting started. We're planning to onboard more providers, introduce support
182+
ingress2gateway is just getting started. We're planning to onboard more providers, introduce support
185183
for more types of Gateway API routes, and make sure everything syncs up smoothly with the ongoing
186184
development of Gateway API.
187185

0 commit comments

Comments
 (0)