fix typos

Author: karenmajewicz

docs/upgrade-metadata.md

@@ -1,7 +1,7 @@
 # Upgrade Guide for converting Metadata from GBL 1.0 to OGM Aardvark
 
 
-The following options are three ways to upgrade GBL 1.0 metadata into OGM Aardvark.  The figures include references to Solr, the search index that powers a GeoBlacklight instance.
+The following options are two ways to upgrade GBL 1.0 metadata into OGM Aardvark.  The figures include references to Solr, the search index that powers a GeoBlacklight instance.
 
 ## Option 1: New pipeline
 
@@ -20,14 +20,14 @@ Fig.1 - Metadata pipeline showing a conversion from standards metadata
 
 This option involves updating your local transformation workflow that extracts values from standards-based metadata files.
 
-* For institutions that utilize an XSLT for the transformation, [GeoCombine repository has XSL files](https://github.com/OpenGeoMetadata/GeoCombine/tree/main/lib/xslt).
+* For institutions that utilize an XSLT for the transformation, the [GeoCombine repository has XSL files](https://github.com/OpenGeoMetadata/GeoCombine/tree/main/lib/xslt).
 
-* For institutions that use custom tools or Python scripts, refer to the OGM Aardvark - FGDC- ISO 19139 crosswalk document to update the code. It shows crosswalks between OGM Aardvark, GBL 1.0, FGDC, and ISO.
+* For institutions that use custom tools or Python scripts, refer to the [OGM Aardvark - FGDC- ISO 19139 crosswalk](aardvark-fgdc-iso-crosswalk.md) to update the code.
 
 ### Considerations for Option #1
 
-* may require extra institutional support, particularly if the transformation process is part of a larger framework or connected to a repository.
-* community-developed XSLs are still a work in progress
+* This may require extra institutional support, particularly if the transformation process is part of a larger framework or connected to a repository.
+* The community-developed XSLs are still a work in progress.
 
 
 
@@ -41,14 +41,14 @@ Programmatically convert the JSON files
 Fig.2 - Programmatic transformation process using Geoblacklight 1.0 Metadata JSONs
 
 
-### Scenario
+### Scenarios
 * you only have GBL 1.0 metadata (no structured metadata files in an official standard)
 * you want to test your environment with the new Aardvark schema 
 
 ### How does it work?
 
 1. Gather GBL 1.0 metadata JSON files on your desktop
-2. Use a script or tool to convert the files batch convert GBL 1.0 JSON files to OGM Aardvark
+2. Use a script or tool to batch convert GBL 1.0 JSON files to OGM Aardvark
 3. Re-index the resulting Aardvark JSON files into your application (GeoBlacklight)
 
 Currently, the OpenGeoMetadata community has two tools that can do batch conversions:
@@ -57,22 +57,22 @@ Currently, the OpenGeoMetadata community has two tools that can do batch convers
 * [gbl2aardvark](https://kgjenkins.github.io/gbl2aardvark/): A web-hosted interface (recommended tool).
 
 	* Users can upload GBL 1.0 metadata files to this tool and it will return a downloadable JSON in the OGM Aardvark schema.  
-	* In addition to direct crosswalks, this tool will also populate the `Resource Class` and `Resource Type` based upon the `Type` and `Geometry Type` fields from version 1.0. It will also generate new collection level records based upon the value in the Is Part Of fields. 
+	* In addition to direct crosswalks, this tool will populate the `Resource Class` and `Resource Type` based upon the `Type` and `Geometry Type` fields from version 1.0. It will also generate new collection level records based upon the value in the Is Part Of fields. 
 	* Any fields that do not properly convert will be flagged with the phrase "EDIT ME --" 
 	* When reindexing Solr with a single JSON file representing multiple records, use Solr's "Document Type"="File Upload" option.
 	* [See the GitHub documentation for more information](https://github.com/kgjenkins/gbl2aardvark)
 
 * a standalone Python script: [https://github.com/OpenGeoMetadata/gbl-1_to_aardvark](https://github.com/OpenGeoMetadata/gbl-1_to_aardvark).
-   * This command line script will perform a straight conversion of field names. 
-   * It features an editable crosswalk file to customize the transformation.
-   * The non-crosswalkable elements listed above (Type, Geometry Type, and Is Part Of) do not have direct crosswalks and will be copied as is into the new Aardvark JSONs.
+   	* This command line script will perform a straight conversion of field names.
+  	* It features an editable crosswalk file to customize the transformation.
+   	* The non-crosswalkable elements listed above (Type, Geometry Type, and Is Part Of) will be copied as-is into the new Aardvark JSONs.
 
-### Manually remediate tranformated JSONs
+### Recommended: manually remediate transformed JSONs
 
 ![manual-remediation](images/transform-option3.png)
 Fig.3 - Transformation process that includes manual remediation
 
-You may need to perform additional cleanup on the tranformed JSONs.  This technique combines automatic conversions and manual edits:
+You may need to perform additional manual cleanup on the transformed JSONs.
 
 1. Convert your metadata files to a CSV. [This Python script will convert a batch of JSONs to a CSV file](https://github.com/geobtaa/workflows/blob/main/editing/json2csv.py)
 
@@ -83,8 +83,8 @@ You may need to perform additional cleanup on the tranformed JSONs.  This techni
 
 ### Considerations for Option #2
 
-* a workaround method if changing the metadata pipeline is not feasible. However, is not a long-term solution and may result in incomplete metadata.
+* This can be a workaround method if changing the metadata pipeline is not feasible. However, it may result in incomplete metadata.
 
-* will not include some fields that are new in OGM Aardvark, such as Rights or License. To take advantage of those fields, use Option 1 or perform additional remediation.
+*  It will not include some fields that are new in OGM Aardvark, such as Rights or License. To take advantage of those fields, use Option 1 or perform additional remediation.
 
-* manual cleanup after transformation may be labor intensive
+* Manual cleanup after transformation may be labor intensive.

mkdocs.yml

@@ -78,7 +78,7 @@ nav:
                   - 'Aardvark to FGDC and ISO': 'aardvark-fgdc-iso-crosswalk.md'
                   - 'GBL 1.0 to FGDC and ISO': 'gbl1-fgdc-iso-crosswalk.md'
 
-            - Syntax & Controlled Values:
+            - Syntax:
                   - 'Reference URIs': 'reference-uris.md'
                   - 'Solr Field Suffixes': 'solr-field-suffixes.md'
                   - 'Custom Fields': 'custom-fields.md'