Update doc/cygnus-ngsi/flume_extensions_catalogue/ngsi_arcgis_feature…

…table_sink.md

Co-authored-by: Fermín Galán Márquez <[email protected]>

doc/cygnus-ngsi/flume_extensions_catalogue/ngsi_arcgis_featuretable_sink.md

@@ -69,7 +69,7 @@ Let's see an example:
 
 #### Using Context Broker custom notifications
 
-If a service path has different entitiy types, following the previous example `car` and `van`, they will need to persist in different Feature Layers, to avoid the limitation of one "fiware-servicepath" can only persist in a unique feature table, it can be used [CB custom notifications](https://github.com/telefonicaid/fiware-orion/blob/master/doc/manuals/orion-api.md#custom-notifications) in which we can map a different value for `fiware-service` and `fiware-servicepath` headers parameters. 
+If a service path has different entity types, following the previous example `car` and `van`, they have to be persisted in different Feature Layers. To avoid the limitation of one "fiware-servicepath" can only persist in a unique feature table, [CB custom notifications](https://github.com/telefonicaid/fiware-orion/blob/master/doc/manuals/orion-api.md#custom-notifications) can be used, so we can map a different value for `fiware-service` and `fiware-servicepath` headers parameters for each entity type.
 
 ###### Entity data: