DATAREST-790 - Fixed typos in the reference documentation.

Original pull request: #203.

Author: m4ng0

src/main/asciidoc/overriding-sdr-response-handlers.adoc

@@ -39,12 +39,12 @@ This controller will be served from the same API base path defined in `Repositor
 
 <1> This example uses constructor injection.
 <2> This handler plugs in a custom handler for a Spring Data finder method.
-<3> This handler is using the underlying repository to fetch data, but will tehn do some form of post processing before returning the final data set to the client.
+<3> This handler is using the underlying repository to fetch data, but will then do some form of post processing before returning the final data set to the client.
 <4> The results need to be wrapped up in a Spring HATEOAS `Resources` object to return a collection, but only a `Resource` for a single item.
 <5> Add a link back to this exact method as a "self" link.
 <6> Returning the collection using Spring MVC's `ResponseEntity` wrapper ensure the collection is properly wrapped and rendered in the proper accept type.
 
-`Resources` is for a collection while `Resource` is for a single item. These types can be combined. If you know the links for each item in a collection, use `Resources<Resource<String>>` (or whatever the core domain type is). This lets you assembled links for each item as well as for the whole collection.
+`Resources` is for a collection while `Resource` is for a single item. These types can be combined. If you know the links for each item in a collection, use `Resources<Resource<String>>` (or whatever the core domain type is). This lets you assemble links for each item as well as for the whole collection.
 
 IMPORTANT: In this example, the combined path will be `RepositoryRestConfiguration.getBasePath()` + `/scanners/search/listProducers`.