fix broken links

Author: kgjenkins

docs/creating-metadata.md

@@ -43,7 +43,7 @@ The most commonly used tool for creating geospatial metadata is Esri’s ArcCata
 
 **Option B: Create metadata in the OGM schema directly**
 
-Other repositories skip Option A and create records directly in the OpenGeoMetadata metadata schema. Although users benefit from the more complete information that can be added to an FGDC or ISO document, these standards are not needed to run GeoBlacklight. These repositories often use a spreadsheet or a Dublin-Core-based metadata editor to create the records. Scripts can be used to convert spreadsheets (in .csv format) to JSON in the OpenGeoMetadata schema. See [Scripts and Tools](scripts-and-tools) for example scripts.
+Other repositories skip Option A and create records directly in the OpenGeoMetadata metadata schema. Although users benefit from the more complete information that can be added to an FGDC or ISO document, these standards are not needed to run GeoBlacklight. These repositories often use a spreadsheet or a Dublin-Core-based metadata editor to create the records. Scripts can be used to convert spreadsheets (in .csv format) to JSON in the OpenGeoMetadata schema. See [Workflows and Tools](workflows-and-tools) for example scripts.
 
 ### For resources with existing metadata files
 {: .no_toc }
@@ -69,7 +69,7 @@ Most institutions have their own unique set of tools and workflows to perform th
 
 The process, whether automated or manual, typically involves parsing the existing metadata record, extracting the values from selected fields and inserting the value into a new JSON document under the corresponding OpenGeoMetadata schema field. In most cases the values can simply be copied over as is, although some additional formatting may be necessary.
 
-See [Scripts and Tools](scripts-and-tools) to view custom scripts and tools for additional metadata authoring techniques.
+See [Workflows and Tools](workflows-and-tools) to view custom scripts and tools for additional metadata authoring techniques.
 
 Helpful reminders:
 

docs/legacy-versions.md

@@ -11,7 +11,7 @@ has_toc: false
 Previous versions of the OpenGeoMetadata metadata schema
 {: .fs-6 .fw-300 }
 
-In 2021 the community launched [OGM Aardvark](current-schema), replacing GBL 1.0 (GeoBlacklight metadata schema version 1.0).
+In 2021 the community launched [OGM Aardvark](ogm-aardvark), replacing GBL 1.0 (GeoBlacklight metadata schema version 1.0).
 
 * [GBL 1.0](gbl-1.0)
 * [GBL 0.5](gbl-0.5)

docs/publishing-in-solr.md

@@ -51,7 +51,7 @@ If you have access to your Solr Dashboard panel, you can add records manually by
 
 **Option B: Indexing via scripts**
 
-It is often more practical to use a process for batch adding, updating, and deleting the records. Most of the available processes are in the form of command-line scripts. See [Scripts and Tools](scripts-and-tools) for examples.
+It is often more practical to use a process for batch adding, updating, and deleting the records. Most of the available processes are in the form of command-line scripts. See [Workflows and Tools](workflows-and-tools) for examples.
 
 ## View Solr metadata within GeoBlacklight
 

docs/upgrading.md

@@ -26,7 +26,7 @@ parent: Resources
 
 **Terminology used on this page**
 
-*   **GBL 1.0**: The legacy metadata schema designed for GeoBlacklight versions 2.0-3.7. [The schema is documented on this Legacy page.](/gbl-1.0)
+*   **GBL 1.0**: The legacy metadata schema designed for GeoBlacklight versions 2.0-3.7. [The schema is documented on this Legacy page.](gbl-1.0)
 *   **OGM Aardvark**: The new metadata schema that is compatible with GeoBlacklight version 4.0.
 *   **GeoBlacklight**: When spelled out, GeoBlacklight refers to [the application itself](https://geoblacklight.org), not its namesake legacy metadata schema, GBL 1.0.
 *   **URI**: This is the name we give to the metadata element itself. For example, the URI for the Subject field is `dct_subject_sm`.