Skip to content

Commit 20f54cb

Browse files
committed
html trigger -> http trigger
Signed-off-by: Michelle Dhanani <[email protected]>
1 parent 2335996 commit 20f54cb

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

content/v3/http-trigger.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -16,7 +16,7 @@ url = "https://github.com/spinframework/spin-docs/blob/main/content/v3/http-trig
1616
- [Getting Request and Response Information](#getting-request-and-response-information)
1717
- [Additional Request Information](#additional-request-information)
1818
- [Inside HTTP Components](#inside-http-components)
19-
- [Static Responses with the HTML Trigger](#static-responses-with-the-html-trigger)
19+
- [Static Responses with the HTTP Trigger](#static-responses-with-the-http-trigger)
2020
- [HTTP With Wagi (WebAssembly Gateway Interface)](#http-with-wagi-webassembly-gateway-interface)
2121
- [Wagi Component Requirements](#wagi-component-requirements)
2222
- [Request Handling in Wagi](#request-handling-in-wagi)
@@ -394,7 +394,7 @@ But if you wish, and if your language supports it, you can implement the `incomi
394394

395395
> The WASI family of specifications, and tool support for some component model features that WASI depends on, are not yet fully stabilized. If you implement `wasi-http` directly, you may need to do some trialing to find tool versions which work together and with Spin.
396396
397-
## Static Responses with the HTML Trigger
397+
## Static Responses with the HTTP Trigger
398398

399399
You can write short, static responses within the HTTP trigger by setting `static_response` (instead of `component`):
400400

0 commit comments

Comments
 (0)