Skip to content

Commit

Permalink
docs: fixed typo (#311)
Browse files Browse the repository at this point in the history
  • Loading branch information
tinkernels authored Oct 19, 2023
1 parent 94cc497 commit 2d2aa14
Show file tree
Hide file tree
Showing 2 changed files with 2 additions and 2 deletions.
2 changes: 1 addition & 1 deletion docs/0.4.x/en-US/first-app/defining.md
Original file line number Diff line number Diff line change
Expand Up @@ -34,7 +34,7 @@ First off, we declare a module called `templates`, which will correspond to the

Then we get to that special `main()` function. As you can see, it returns a `PerseusApp`, which takes a generic `G`: this is a special part of Sycamore that lets is say "let this function work with any rendering backend that implements `Html`", because Sycamore can actually go way beyond the web! This generic restricts us to using `SsrNode` (for prerendering), `DomNode` (for rendering to the Document Object Model in the browser), or `HydrateNode` (the same as `DomNode`, but for when we're [hydrating](:fundamentals/hydration)).

You'll also notice that we've provided an argument to the `#[perseus::main(..)]` attribute macro: that's the function that will start up our server! If you want to add things like custom API routes, etc., then you can set this function manually, and then use one of the Perseus server integrations to work with the code you've written (see [this example](https://github.com/framesurge/perseus/tree/main/examples/core/custom_server) for more), but here we're just using the default server from the `perseus-axum` package. If you fancy [Warp](https://github.com/seanmonstar/warp), you can use `perseus-axum`, and [Actix Web](https://github.com/actix/actix-web) fans can use the `perseus-actix-web` package!
You'll also notice that we've provided an argument to the `#[perseus::main(..)]` attribute macro: that's the function that will start up our server! If you want to add things like custom API routes, etc., then you can set this function manually, and then use one of the Perseus server integrations to work with the code you've written (see [this example](https://github.com/framesurge/perseus/tree/main/examples/core/custom_server) for more), but here we're just using the default server from the `perseus-axum` package. If you fancy [Warp](https://github.com/seanmonstar/warp), you can use `perseus-warp`, and [Actix Web](https://github.com/actix/actix-web) fans can use the `perseus-actix-web` package!

## Your `PerseusApp`

Expand Down
2 changes: 1 addition & 1 deletion docs/next/en-US/first-app/defining.md
Original file line number Diff line number Diff line change
Expand Up @@ -34,7 +34,7 @@ First off, we declare a module called `templates`, which will correspond to the

Then we get to that special `main()` function. As you can see, it returns a `PerseusApp`, which takes a generic `G`: this is a special part of Sycamore that lets is say "let this function work with any rendering backend that implements `Html`", because Sycamore can actually go way beyond the web! This generic restricts us to using `SsrNode` (for prerendering), `DomNode` (for rendering to the Document Object Model in the browser), or `HydrateNode` (the same as `DomNode`, but for when we're [hydrating](:fundamentals/hydration)).

You'll also notice that we've provided an argument to the `#[perseus::main(..)]` attribute macro: that's the function that will start up our server! If you want to add things like custom API routes, etc., then you can set this function manually, and then use one of the Perseus server integrations to work with the code you've written (see [this example](https://github.com/framesurge/perseus/tree/main/examples/core/custom_server) for more), but here we're just using the default server from the `perseus-axum` package. If you fancy [Warp](https://github.com/seanmonstar/warp), you can use `perseus-axum`, and [Actix Web](https://github.com/actix/actix-web) fans can use the `perseus-actix-web` package!
You'll also notice that we've provided an argument to the `#[perseus::main(..)]` attribute macro: that's the function that will start up our server! If you want to add things like custom API routes, etc., then you can set this function manually, and then use one of the Perseus server integrations to work with the code you've written (see [this example](https://github.com/framesurge/perseus/tree/main/examples/core/custom_server) for more), but here we're just using the default server from the `perseus-axum` package. If you fancy [Warp](https://github.com/seanmonstar/warp), you can use `perseus-warp`, and [Actix Web](https://github.com/actix/actix-web) fans can use the `perseus-actix-web` package!

## Your `PerseusApp`

Expand Down

0 comments on commit 2d2aa14

Please sign in to comment.