fix: correct dead links (#2633)

.github/ISSUE_TEMPLATE/new-ontology.yml

@@ -115,7 +115,7 @@ body:
     attributes:
       label: Ontology Download Link
       description: What URL can be used to download your Ontology?
-      placeholder: e.g. https://github.com/obophenotype/uberon/raw/master/uberon.owl
+      placeholder: e.g. https://github.com/obophenotype/uberon/blob/master/uberon.obo
     validations:
       required: true
 
@@ -208,7 +208,7 @@ body:
       render: yaml
       description: |
         Please provide a list of current uses for your ontology in YAML format as a list of objects with `user`, `description`, and `example` keys like in the following example:
-        
+
         ```yaml
         - user: https://www.rhea-db.org/
           description: Rhea uses CHEBI to annotate reaction participants
@@ -228,7 +228,7 @@ body:
     attributes:
       value: |
         # Finishing Up
-        
+
         This final section asks you to introspect on your ontology request.
   - type: textarea
     id: scenarios
@@ -266,7 +266,7 @@ body:
           required: false
         - label: My identifiers (classes and properties IRIs) are formatted according to the [OBO Foundry Identifier Policy](http://obofoundry.org/id-policy)
           required: false
-        - label: My term labels are in English and conform to the OBO Foundry [Naming Conventions](http://obofoundry.org/http://obofoundry.org/principles/fp-012-naming-conventions.html)
+        - label: My term labels are in English and conform to the OBO Foundry [Naming Conventions](http://obofoundry.org/principles/fp-012-naming-conventions.html)
           required: false
         - label: I understand that term definitions are key to understanding the intentions of a term, especially when the ontology is used in curation. I made sure that a reasonable majority of terms in my ontology--and all top level terms--have definitions, in English, using the [IAO:0000115](https://ontobee.org/ontology/IAO?iri=http://purl.obolibrary.org/obo/IAO_0000115) property.
           required: false