Merge pull request #934 from k5e/typos-in-readme

fix typos in README.md

Author: mevdschee

README.md

@@ -285,7 +285,7 @@ On list operations you may apply filters and joins.
 ### Filters
 
 Filters provide search functionality, on list calls, using the "filter" parameter. You need to specify the column
-name, a comma, the match type, another commma and the value you want to filter on. These are supported match types:
+name, a comma, the match type, another comma and the value you want to filter on. These are supported match types:
 
   - "cs": contain string (string contains value)
   - "sw": start with (string starts with value)
@@ -572,7 +572,7 @@ This adjusts the titles of the posts. And the return values are the number of ro
     [1,1]
 
 Which means that there were two update operations and each of them had set one row. Batch operations use database
-transactions, so they either all succeed or all fail (successful ones get roled back). If they fail the body will
+transactions, so they either all succeed or all fail (successful ones get rolled back). If they fail the body will
 contain the list of error documents. In the following response the first operation succeeded and the second operation
 of the batch failed due to an integrity violation:
 
@@ -667,7 +667,7 @@ You can enable the following middleware using the "middlewares" config parameter
 - "multiTenancy": Restricts tenants access in a multi-tenant scenario
 - "pageLimits": Restricts list operations to prevent database scraping
 - "joinLimits": Restricts join parameters to prevent database scraping
-- "textSearch": Search in all text fields with a simple paramater
+- "textSearch": Search in all text fields with a simple parameter
 - "customization": Provides handlers for request and response customization
 - "json": Support read/write of JSON strings as JSON objects/arrays
 - "xml": Translates all input and output from JSON to XML
@@ -763,7 +763,7 @@ In the sections below you find more information on the built-in middleware.
 ### Authentication
 
 Currently there are five types of authentication supported. They all store the authenticated user in the `$_SESSION` super global.
-This variable can be used in the authorization handlers to decide wether or not sombeody should have read or write access to certain tables, columns or records.
+This variable can be used in the authorization handlers to decide wether or not somebody should have read or write access to certain tables, columns or records.
 The following overview shows the kinds of authentication middleware that you can enable.
 
 | Name       | Middleware   | Authenticated via      | Users are stored in | Session variable        |
@@ -780,7 +780,7 @@ Below you find more information on each of the authentication types.
 
 API key authentication works by sending an API key in a request header.
 The header name defaults to "X-API-Key" and can be configured using the 'apiKeyAuth.header' configuration parameter.
-Valid API keys must be configured using the 'apiKeyAuth.keys' configuration parameter (comma seperated list).
+Valid API keys must be configured using the 'apiKeyAuth.keys' configuration parameter (comma separated list).
 
     X-API-Key: 02c042aa-c3c2-4d11-9dae-1a6e230ea95e