diff --git a/docs/index.md b/docs/index.md index e8dc5d4..abbd00f 100644 --- a/docs/index.md +++ b/docs/index.md @@ -446,7 +446,7 @@ myServer = Server #### DRY Endpoints -When implementing an API you will usually need the same path to have multiple methods, each with different parameters in the query, body and headers. Since Endpoints are records this is easy to deal with. Let's say we have a typical `/users/{userID : UserID}` route that accepts GET and PUT requests for fetching and updating a specific user respectively. The GET variant doesn't need a Body, but the PUT variant will. +When implementing an API you will usually need the same path to have multiple methods, each with different parameters in the query, body and headers. Since Endpoints are records, this is easy to deal with. Let's say we have a typical `/users/{userID : UserID}` route that accepts GET and PUT requests for fetching and updating a specific user respectively. The GET variant doesn't need a Body, but the PUT variant will. ```haskell getUser = Endpoint diff --git a/docs/pages/index.html b/docs/pages/index.html index 07fe530..5bc8b67 100644 --- a/docs/pages/index.html +++ b/docs/pages/index.html @@ -443,7 +443,7 @@ class="sourceCode haskell">DRY Endpoints

When implementing an API you will usually need the same path to have multiple methods, each with different parameters in the query, body and -headers. Since Endpoints are records this is easy to deal with. Let's +headers. Since Endpoints are records, this is easy to deal with. Let's say we have a typical /users/{userID : UserID} route that accepts GET and PUT requests for fetching and updating a specific user respectively. The GET variant doesn't need a Body, but the PUT variant