Merge pull request #921 from manusajith/doc_patches

Fix some typos in docs
This commit is contained in:
Alp Mestanogullari 2018-03-13 09:56:20 +01:00 committed by GitHub
commit e02f29a379
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
4 changed files with 5 additions and 5 deletions

View file

@ -61,7 +61,7 @@ to flexibly set up a whole bunch of PostgreSQL connections tailored to our
needs and then to forget about it all by simply asking for a connection needs and then to forget about it all by simply asking for a connection
using `withResource`. using `withResource`.
The handlers are straighforward. One takes care of inserting a new The handlers are straightforward. One takes care of inserting a new
value in the database while the other fetches all messages and returns value in the database while the other fetches all messages and returns
them. We also provide a function for serving our web app given a PostgreSQL them. We also provide a function for serving our web app given a PostgreSQL
connection pool, which simply calls servant-server's `serve` function. connection pool, which simply calls servant-server's `serve` function.

View file

@ -42,9 +42,9 @@ initDB dbfile = withConnection dbfile $ \conn ->
"CREATE TABLE IF NOT EXISTS messages (msg text not null)" "CREATE TABLE IF NOT EXISTS messages (msg text not null)"
``` ```
Next, our server implementation. It will be parametrised (take as Next, our server implementation. It will be parametrised (take as an
argument) by the name of the file that contains our SQLite database. argument) by the name of the file that contains our SQLite database.
The handlers are straighforward. One takes care of inserting a new The handlers are straightforward. One takes care of inserting a new
value in the database while the other fetches all messages and returns value in the database while the other fetches all messages and returns
them. We also provide a function for serving our web app given an them. We also provide a function for serving our web app given an
SQLite database file, which simply calls servant-server's `serve` function. SQLite database file, which simply calls servant-server's `serve` function.

View file

@ -48,7 +48,7 @@ dedicated `ReqBody`-like combinator named
This combinator takes two parameters. The first one is the This combinator takes two parameters. The first one is the
"backend" to use. Currently, you only have the choice between "backend" to use. Currently, you only have the choice between
`Mem` and `Tmp`. The former loads the entire input in memory, `Mem` and `Tmp`. The former loads the entire input in memory,
even the uploadedd files, while `Tmp` will stream uploaded even the uploaded files, while `Tmp` will stream uploaded
files to some temporary directory. files to some temporary directory.
The second parameter is the type you want the multipart data The second parameter is the type you want the multipart data

View file

@ -137,7 +137,7 @@ type StreamGet = Stream 'GET
type StreamPost = Stream 'POST type StreamPost = Stream 'POST
``` ```
These describe endpoints that return a stream of values rather than just a single value. They not only take a single content type as a parameter, but also a framing strategy -- this specifies how the individual results are deliniated from one another in the stream. The two standard strategies given with Servant are `NewlineFraming` and `NetstringFraming`, but others can be written to match other protocols. These describe endpoints that return a stream of values rather than just a single value. They not only take a single content type as a parameter, but also a framing strategy -- this specifies how the individual results are delineated from one another in the stream. The two standard strategies given with Servant are `NewlineFraming` and `NetstringFraming`, but others can be written to match other protocols.
### `Capture` ### `Capture`