finish relations fields page, fix links

Author: rmseifried

docs/about-ogm-aardvark.md

@@ -4,11 +4,11 @@ Details about the OpenGeoMetadata metadata schema, OGM Aardvark
 
 !!! abstract "Summary"
 
-	* based on [Dublin Core](https://www.dublincore.org/specifications/dublin-core/dcmi-terms/), with custom elements added for spatial values
-	* designed for discovery - to help users _find_ items
-	* not designed for complete technical documentation, such as a GIS dataset's processing history
-	* includes elements for external links, such as downloads, web services, or supplemental metadata
-	* requires records to be formatted as JSON files
+	* Based on [Dublin Core](https://www.dublincore.org/specifications/dublin-core/dcmi-terms/), with custom elements added for spatial values.
+	* Designed for discovery - to help users _find_ items.
+	* Not designed for complete technical documentation, such as a GIS dataset's processing history.
+	* Includes elements for external links, such as downloads, web services, or supplemental metadata.
+	* Requires records to be formatted as JSON files ([learn more here](../JSON-format)).
 
 ## Terminology
 

docs/further-reading.md

@@ -9,8 +9,8 @@
 
 ### [A Metadata Schema for Geospatial Resource Discovery Use Cases](https://journal.code4lib.org/articles/9710)
 
-Presents an earlier version of the GeoBlacklight schema and the motivations behind its design. Full citation: Hardy, Darren, and Kim Durante (2014). "A Metadata Schema for Geospatial Resource Discovery Use Cases." *Code4Lib* 25. https://journal.code4lib.org/articles/9710.
+Presents an earlier version of the GeoBlacklight schema and the motivations behind its design. Full citation: Hardy, Darren, and Kim Durante (2014). "A Metadata Schema for Geospatial Resource Discovery Use Cases." *Code4Lib* 25. [https://journal.code4lib.org/articles/9710](https://journal.code4lib.org/articles/9710).
 
 ### [Consortial Geospatial Data Collection: Toward Standards and Processes for Shared GeoBlacklight Metadata](https://doi.org/10.31229/osf.io/kp5r6)
-	
-Discusses strategies for authorship and management of interoperable GeoBlacklight metadata. Full citation: Battista, Andrew, Karen Majewicz, Stephen Balogh, and Darren Hardy (2018). "Consortial Geospatial Data Collection: Toward Standards and Processes for Shared GeoBlacklight Metadata." *Journal of Library Metadata* 17:3-4, 183-200, DOI: 10.1080/19386389.2018.1443414.
+
+Discusses strategies for authorship and management of interoperable GeoBlacklight metadata. Full citation: Battista, Andrew, Karen Majewicz, Stephen Balogh, and Darren Hardy (2018). "Consortial Geospatial Data Collection: Toward Standards and Processes for Shared GeoBlacklight Metadata." *Journal of Library Metadata* 17:3-4, 183-200, DOI: [10.1080/19386389.2018.1443414](https://doi.org/10.1080/19386389.2018.1443414).

docs/images/rel-is-replaced-by.png

@@ -2,7 +2,7 @@
 
 Fields in the "relations" group are used to describe how records relate to each other. All of them are designed to store the [ID(s)](https://opengeometadata.org/ogm-aardvark/#id) of related records. More than one record can be listed within each relationship field.
 
-Starting in GeoBlacklight version 4.0, these fields are used to populate relationship widgets in the application sidebar, allowing users to easily explore related records and understand how they are connected. The relationship widgets are customizable in the `geoblacklight.en.yml` and `settings.yml` files.
+Starting in GeoBlacklight version 4.0, most of these fields are used to populate relationship widgets in the application sidebar, allowing users to easily explore related records and understand how they are connected. The relationship widgets are customizable in the `geoblacklight.en.yml` and `settings.yml` files.
 
 
 | Field | Field Name | Obligation |