Home.md

@@ -31,11 +31,11 @@ In the future we are planning to provide bib-tex formatted data of the citation
 
 ## Technical adoption in application level metadata & semantics
 
-Irrespective your how you want to technically align metadata and semantics with EM-Glossary terminology, we look forward for you contact us about your plans. We are happy to discuss your planned way of alignment, compare to other adoption cases and would be happy to highlight you on our [webpage](https://emglossary.helmholzt-metadaten.de) as an adopter!
+Irrespective your how you want to technically align metadata and semantics with EM-Glossary terminology, we look forward for you contact us about your plans. We are happy to discuss your planned way of alignment, compare to other adoption cases and would be happy to highlight you on our [webpage](https://emglossary.helmholtz-metadaten.de) as an adopter!
 
 It is clear that different application cases may require closer or less close semantic alignment. Below we provide suggestions on technical implementation in order to harmonise re-use. 
 
-Every term in the EM-Glossary carries an "international resource identifier" (IRI). The IRIs are assigned to classes within emg.owl and are globally unique and fully persistent. The "IRIs assigned to EM-Glossary classes within emg.owl are globally unique and fully persistent to offer term-level dereferenceability of our artefact. IRIs consist of the base URI `purl.helmholtz-metadaten.de/emg/` and a term specific extension in the form of `EMG_XXXXXXXX`. We use numeric term extensions rather than term labels to provide higher stability (e.g. in case term label are altered).
+Every term in the EM-Glossary carries an "international resource identifier" (IRI). The IRIs are assigned to classes within emg.owl and are globally unique and fully persistent. The "IRIs assigned to EM-Glossary classes within emg.owl are globally unique and fully persistent to offer term-level dereferenceability of our artefact. IRIs consist of the base URI `https://purl.helmholtz-metadaten.de/emg/` (protocol + resolver address + name space) and a term specific extension in the form of `EMG_XXXXXXXX`. We use numeric term extensions rather than term labels to provide higher stability (e.g. in case term label are altered).
 
 _Referencing classes in emg.owl using the designated class IRI is the minimum requirement for adoption of EM-Glossary terminology_