Update README.md

Author: Andrea Spacca

README.md

@@ -37,7 +37,7 @@ File generated: /Users/andreaspacca/Library/Application Support/elastic-integrat
 
 
 ### Config file
-It is possible to tweak the randomness of the generated data through a config file provivde by the `--config-file` flag
+It is possible to tweak the randomness of the generated data through a config file provided by the `--config-file` flag
 
 ##### Sample config
 ```yaml
@@ -70,12 +70,12 @@ It is possible to tweak the randomness of the generated data through a config fi
 
 #### Config entries definition
 The config file is a yaml file consisting of an array of config entry.
-For each config entry the following fileds are available
+For each config entry the following fields are available
 - `name` *mandatory*: dotted path field
 - `fuzziness` *optional (`long` and `double` type only)*: delta from the previous generated value for the same field
 - `range` *optional (`long` and `double` type only)*: value will be generated between 0 and range
 - `cardinality` *optional*: per-mille distribution of different values for the field
 - `object_keys` *optional (`object` type only)*: list of field names to generate in a object field type. if not specified a random number of field names will be generated in the object filed type.
 - `value` *optional*: hardcoded value to set for the field (any `cardinality` will be ignored)
 
-If you have an `object` type field that you defined one or multiple `object_keys` for, you can reference them as a root level field with their own customisation. Beware that if a `cardinality` is set for the `object` type field, cardinality will be ignored for the children `object_keys` fields.
+If you have an `object` type field that you defined one or multiple `object_keys` for, you can reference them as a root level field with their own customisation. Beware that if a `cardinality` is set for the `object` type field, cardinality will be ignored for the children `object_keys` fields.