docs(egfr): clarify string ensp nodes

Made the same mistake again :/

Author: tristan-f-r

datasets/egfr/README.md

@@ -15,4 +15,4 @@ This produces two sets of files: one based on the iRefIndex/PhosphoSite directed
 trimming psuedonodes and manually injecting the `EGF_HUMAN` receptor as a dummy node for OmicsIntegrator1.
 - `process_interactome.py`: Produces the STRING `interactome.tsv` file from the STRING links file. Note that the `phosphosite-irefindex13.0-uniprot.txt` is a magic (as in with closed-source origin) directed interactome produced with a combination of the now archived iRefIndex v13 interactome with extra PhosphoSite-provided nodes
 - `process_gold_standard.py`: Produces the `gold-standard-nodes-uniprot.txt` file from the [EGFR prize file](https://raw.githubusercontent.com/gitter-lab/tps/ca7cafd1e1c17f45ddea07c3fb54d0d70b86ff45/data/resources/eight-egfr-reference-all.txt) from the above paper.
-- `map_ensembl.py`: Maps UniProt identifiers to STRING identifiers for the STRING-based data.
+- `map_ensembl.py`: Maps UniProt identifiers to STRING-restricted ENSP identifiers for the STRING-based data.