Specs gtfs2ntfs: fix typos

src/documentation/common.md

@@ -9,7 +9,7 @@ needs to be included in every object's id.
 
 Prepending all the identifiers with a unique prefix ensures that the NTFS identifiers are unique accross all the NTFS datasets. With this assumption, merging two NTFS datasets can be done without worrying about conflicting identifiers.
 
-This prefix should be applied to all NTFS identifier except for the physical mode identifiers that are standarized and fixed values. Fixed values are described in the [NTFS specifications](https://github.com/CanalTP/ntfs-specification/blob/master/ntfs_fr.md#physical_modestxt-requis)
+This prefix should be applied to all NTFS identifiers except for the physical mode identifiers that are standardized and fixed values. Fixed values are described in the [NTFS specifications](https://github.com/CanalTP/ntfs-specification/blob/master/ntfs_fr.md#physical_modestxt-requis)
 
 ## Configuration of each converter
 A configuration file `config.json`, as it is shown below, is provided for each 

src/documentation/gtfs_to_ntfs_specs.md

@@ -180,7 +180,7 @@ specified, the conversion should stop immediately with an error.
 (1) When several GTFS Routes with different `route_type`s are grouped together, the commercial_mode_id with the smallest priority should be used (as specified in chapter "Mapping of route_type with modes").
 
 ### Reading calendars.txt and calendar_dates.txt
-GTFS services are trasnformed into lists of active dates as if using a single NTFS 
+GTFS services are transformed into lists of active dates as if using a single NTFS 
 file `calendar_dates.txt`. The resulting NTFS files might be different following an 
 optimization operation applied at the end of the conversion, but the result should be 
 functionally identical.