Apply suggestion from @matentzn

Author: matentzn

_posts/2025-10-22-9th-issue-newsletter.md

@@ -242,7 +242,7 @@ Unified Phenotype Ontology (uPheno) featured in [issue 6](https://obofoundry.org
 
 To ensure interoperability and logical consistency across OBO Foundry ontologies, existing relations must be reused whenever possible. The Relations Ontology (RO) serves as the primary source for standard relations. By reusing RO terms, ontologies enable automated reasoning, detection of inconsistencies, and inference of new knowledge across domains. When a required relation is not available in RO, developers are expected to search other OBO ontologies before introducing a new one. Relations intended for broader use should be submitted to RO. If a relation is retained within a local ontology, it must be defined as a sub-property of an appropriate RO parent relation, if it exists.
 
-**[Validation: ](https://obofoundry.org/principles/checks/fp_007)**Each relation that does not use an RO IRI is automatically checked. If a relation label matches one in RO but does not use the correct RO IRI, it is flagged as an *error*. Any other non-RO relations are reported as *information messages*. This validation is implemented in the OBO Dashboard to support consistency across ontologies.
+**[Validation:](https://obofoundry.org/principles/checks/fp_007)** Each relation that does not use an RO IRI is automatically checked. If a relation label matches one in RO but does not use the correct RO IRI, it is flagged as an *error*. Any other non-RO relations are reported as *information messages*. This validation is implemented in the OBO Dashboard to support consistency across ontologies.
 
 Coordination with RO is encouraged through [GitHub](https://github.com/oborel/obo-relations/issues) or the OBO Slack [#relation-ontology channel](https://obo-communitygroup.slack.com/archives/C01P3D02U1H).