From 79a597eb8c93990a32f3c722880aad191d1c40dc Mon Sep 17 00:00:00 2001 From: Noel Welsh Date: Tue, 2 Jul 2024 08:26:06 +0100 Subject: [PATCH] Fix typos --- docs/src/pages/routes/README.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/src/pages/routes/README.md b/docs/src/pages/routes/README.md index 78477d6..6ca2ecf 100644 --- a/docs/src/pages/routes/README.md +++ b/docs/src/pages/routes/README.md @@ -36,13 +36,13 @@ val route = Route(Request.get(Path / "user" / Param.int), Response.ok(Entity.tex [Request](request.md) and [Response](response.md) have separate pages, so here we'll just discuss the handler. There are three ways to create a handler: using `handle`, `handleIO`, or `passthrough`. Assume the request produces a value of type `A` and the response needs a value of type `B`. Then these three methods have the following meaning: - `handle` is a function `A => B`; -- `handle` is a function `A => IO[B]`; and +- `handleIO` is a function `A => IO[B]`; and - `passthrough`, which can only be called when `A` is the same type as `B`, means that the output of the request is connected directly to the input of the response. This is useful, for example, when the response is loading a static file from the file system, and the request produces the name of the file to load. ### Type Transformations for Handlers -If you dig into the types produced by `Requests`, you notice a lot of tuple types are used. Here's an example, showing a `Request` producing a `Tuple2`. +If you dig into the types produced by `Requests` you will notice a lot of tuple types are used. Here's an example, showing a `Request` producing a `Tuple2`. ```scala mdoc val request = Request.get(Path / Param.int / Param.string)