Skip to content

docs: A few small fixes #235

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Mar 24, 2022
Merged

docs: A few small fixes #235

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions docs/content/http-trigger.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -104,12 +104,12 @@ Spin HTTP _executor_ is defined using WebAssembly interfaces.

> The WebAssembly component model is in its early stages, and during the `0.x`
> releases of Spin, the triggers and application entry points will suffer
> breaking changes, particularly around the primitive types used to defined
> breaking changes, particularly around the primitive types used to define
> the HTTP objects and function signatures — i.e. bodies will become streams,
> handler functions will become asynchronous.

We define the HTTP objects as
[WebAssembly Interface (WIT)]((https://github.com/bytecodealliance/wit-bindgen/blob/main/WIT.md))
[WebAssembly Interface (WIT)](https://github.com/bytecodealliance/wit-bindgen/blob/main/WIT.md)
objects, currently using _records_:

```fsharp
Expand Down
6 changes: 3 additions & 3 deletions docs/content/rust-components.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -126,7 +126,7 @@ audible only to dogs, just for his Shetland sheepdog."}

> Without the `allowed_http_hosts` field populated properly in `spin.toml`,
> the component would not be allowed to send HTTP requests, and sending the
> request would generate in a "Destination not allowed" error.
> request would result in a "Destination not allowed" error.

We just built a WebAssembly component that sends an HTTP request to another
service, manipulates that result, then responds to the original request.
Expand All @@ -140,7 +140,7 @@ Besides the HTTP trigger, Spin has built-in support for a Redis trigger —
which will connect to a Redis instance and will execute Spin components for
new messages on the configured channels.

> See the [Redis trigger](/redis-rigger) for details about the Redis trigger.
> See the [Redis trigger](/redis-trigger) for details about the Redis trigger.

Writing a Redis component in Rust also takes advantage of the SDK:

Expand Down Expand Up @@ -186,7 +186,7 @@ This application will connect to `redis://localhost:6379`, and for every new
message on the `messages` channel, the `echo-message` component will be executed.

```bash
# first, start redis-server on the default prot 6379
# first, start redis-server on the default port 6379
$ redis-server --port 6379
# then, start the Spin application
$ spin up --file spin.toml
Expand Down