(maint) typos and phrasing

Author: DavidS

language/resource-api/README.md

@@ -77,7 +77,6 @@ Each resource being managed must be identified by a unique title. Usually this i
 
 If multiple attributes are defined with the `namevar` behaviour, the type SHOULD specify `title_patterns` that will tell Resource API how to get at the attributes from the title. If `title_patterns` is not specified a default pattern is applied, and matches against the first declared `namevar`.
 
-
 > Note: The order of title_patterns is important. You should declare the most specific pattern first and end with the most generic.
 
 Each title pattern contains the:
@@ -184,7 +183,7 @@ A missing `:should` entry indicates that a resource should be removed from the s
 
 The `set` method should always return `nil`. Any progress signaling should be done through the logging utilities described below. If the `set` method throws an exception, all resources that should change in this call and haven't already been marked with a definite state, will be marked as failed. The runtime will only call the `set` method if there are changes to be made, especially in the case of resources marked with `noop => true` (either locally or through a global flag). The runtime will not pass them to `set`. See `supports_noop` below for changing this behaviour if required.
 
-Both methods take a `context` parameter which provides utilties from the runtime environment, and is decribed in more detail there.
+Both methods take a `context` parameter which provides utilities from the runtime environment, and is described in more detail in its own section below.
 
 ## Implementing simple providers
 
@@ -208,17 +207,17 @@ class Puppet::Provider::AptKey::AptKey < Puppet::ResourceApi::SimpleProvider
 Once all of that is in place, instead of the `set` method, the provider needs to implement the `create`, `update` or `delete` methods:
 
 * `create(context, name, should)`: This is called when a new resource should be created.
-  * `context`: provides utilties from the runtime environment, and is decribed in more detail there.
+  * `context`: provides utilities from the runtime environment, and is described in more detail in its own section below.
   * `name`: the name or hash of the new resource.
   * `should`: a hash of the attributes for the new instance.
 
 * `update(context, name, should)`: This is called when a resource should be updated.
-  * `context`: provides utilties from the runtime environment, and is decribed in more detail there.
+  * `context`: provides utilities from the runtime environment, and is described in more detail in its own section below.
   * `name`: the name or hash of the resource to change.
   * `should`: a hash of the desired state of the attributes.
 
 * `delete(context, name)`: This is called when a resource should be deleted.
-  * `context`: provides utilties from the runtime environment, and is decribed in more detail there.
+  * `context`: provides utilities from the runtime environment, and is described in more detail in its own section below.
   * `name`: the name or hash of the resource that should be deleted.
 
 The `SimpleProvider` takes care of basic logging, and error handling.