Update readme

Author: andersfugmann

README.md

@@ -1,9 +1,9 @@
 # Ppx Protocol Conv
 Ppx protocol conv (de)serializers using deriving, which allows for
-plugable
+pluggable
 (de)serializers. [Api](https://andersfugmann.github.io/ppx_protocol_conv).
 
-This page contains an simple overview of functionality provided.
+This page contains a simple overview of the provided functionality.
 More information is available in the [wiki pages](https://github.com/andersfugmann/ppx_protocol_conv/wiki)
 
 [![Main workflow](https://github.com/andersfugmann/ppx_protocol_conv/actions/workflows/workflow.yml/badge.svg)](https://github.com/andersfugmann/ppx_protocol_conv/actions/workflows/workflow.yml)
@@ -20,10 +20,10 @@ The ppx supports the following features:
  * records
  * recursive and non-recursive types
  * variants
- * polymophic variants
- * All primitive types (except nativeint)
+ * polymorphic variants
+ * all primitive types (including `nativeint`)
 
-The following drivers exists
+The following drivers exist:
  * `Json` which serializes to `Yojson.Safe.t`
  * `Jsonm` which serializes to `Ezjsonm.value`
  * `Msgpack` which serializes to `Msgpck.t`
@@ -52,8 +52,8 @@ val a_to_json: a -> Json.t
 val a_of_json_exn: Json.t -> a
 val a_of_json: Json.t -> (a, exn) result
 
-val b_to_json: a -> Json.t
-val b_of_json_exn: Json.t -> a
+val b_to_json: b -> Json.t
+val b_of_json_exn: Json.t -> b
 val b_of_json: Json.t -> (b, exn) result
 ```
 
@@ -65,29 +65,29 @@ Evaluates to
 [ "x", `Int 42; "Y", `String "really"; "z", `List [ `Int 6; `Int 7 ] ] (* Yojson.Safe.json *)
 ```
 
-`to_protocol` deriver will generate serilisation of the
-type. `of_protocol` deriver generates de-serilisation of the type,
-while `protocol` deriver will generate both serilisation and de-serilisation functions.
+`to_protocol` deriver generates serialization of the
+type. `of_protocol` deriver generates deserialization of the type,
+while `protocol` deriver generates both serialization and deserialization functions.
 
 ## Attributes
 Record label names can be changed using `[@key <string>]`
 
 Variant and polymorphic variant constructors names can be changed using the `[@name <string>]`
 attribute.
 
-If a record field is not present in the input when deserialising, as default value can be
+If a record field is not present in the input when deserializing, a default value can be
 assigned using `[@default <expr>]`. If the value to be serialized
 matches the default value, the field will be omitted (Some drivers
-allow disabling this functonality. Comparrison uses polymorphic compare, so be careful.
+allow disabling this functionality. Comparison uses polymorphic compare, so be careful.)
 
 ## Signatures
-The ppx also handles signature, but disallows
-`[@key ...]`, `[@default ...]` and `[@name] ....` as these does not impact signatures.
+The ppx also handles signatures, but disallows
+`[@key ...]`, `[@default ...]` and `[@name ...]` because these do not impact signatures.
 
 ## Drivers
 
 Drivers specify concrete serialization and deserialization.
-Users of the library can elect to implement their own driver see
+Users of the library can elect to implement their own driver, see
 [custom drivers](#custom-drivers), or use predefined drivers:
 
  * `Json` which serializes to `Yojson.Safe.t`
@@ -104,10 +104,12 @@ It is easy to provide custom drivers by implementing the signature:
 include Protocol_conv.Runtime.Driver with
   type t = ...
 ```
-See the `drivers` directory for examples on how to implemented new drivers.
+See the `drivers` directory for examples on how to implement new drivers.
 Submissions of new drivers are more than welcome.
 
 ## Not supported
 * Generalised algebraic datatypes
 * Extensible types
 * Extensible polymorphic variants
+
+Unsupported type shapes are reported with location-aware PPX errors.