Tweak grammar and diction

Author: gibson042

versions/3.0.md

@@ -119,12 +119,11 @@ For example, if a field is said to have an array value, the JSON array represent
 }
 ```
 
-While the API is described using JSON it does not impose a JSON input/output to the API itself.
+Even though the API is described with JSON, it is not required to use JSON for input or output.
 
 All field names in the specification are **case sensitive**.
 
-The schema exposes two types of fields.
-Fixed fields, which have a declared name, and Patterned fields, which declare a regex pattern for the field name.
+The schema exposes two types of fields: Fixed fields, which have a declared name, and Patterned fields, which declare a regex pattern for the field name.
 Patterned fields can have multiple occurrences as long as each has a unique name. 
 
 In order to preserve the ability to round-trip between YAML and JSON formats, YAML version [1.2](http://www.yaml.org/spec/1.2/spec.html) is recommended along with some additional constraints:
@@ -1136,8 +1135,8 @@ items:
 
 A container for the expected responses of an operation.
 The container maps a HTTP response code to the expected response.
-It is not expected from the documentation to necessarily cover all possible HTTP response codes, since they may not be known in advance.
-However, it is expected from the documentation to cover a successful operation response and any known errors.
+It is not expected for the documentation to necessarily cover all possible HTTP response codes, since they may not be known in advance.
+However, it is expected for the documentation to cover a successful operation response and any known errors.
 
 The `default` MAY be used as a default response object for all HTTP codes that are not covered individually by the specification.