chore: minor niggles

sharing/examples/index.md

@@ -14,26 +14,26 @@ categories: []
 ## Parcels - Collaboration
 {: .text-left}
 
-Our state-wide [parcel boundary dataset]({% link data/cadastre/parcels/index.html %}#UtahParcels) is the most-visited data page on our website, and for good reason—property boundaries (even the rough, un-surveyed approximations in GIS) are a foundational layer for many maps. They facilitate both commercial activity and private property management.
+Our state-wide [parcel boundary dataset]({% link data/cadastre/parcels/index.html %}#UtahParcels) is the most-visited data page on our website, and for good reason: property boundaries (even their rough, un-surveyed approximations in GIS) are a foundational layer for many maps. They facilitate both commercial activity and private property management.
 
 This statewide collection would not be possible without the cooperation of counties across the state who send us updates to their parcel data on a regular basis. We merge them into a single, consistent dataset available to anyone for free.
 
 ## Roads - Collaboration
 {: .text-left}
 
-Free, up-to-date, and comprehensive [road data]({% link data/transportation/roads-system/index.html %}#RoadCenterlines) is a luxury we are fortunate to have. Thanks to the contributions of cities, counties, and UDOT, cartographers and analysts don't need to download road data from five different places with five different schemas, nor do they need to pay a commercial company to access data their tax dollars have already paid for. It's all here in one dataset.
+We are fortunate to have the luxury of free, up-to-date, and comprehensive [road data]({% link data/transportation/roads-system/index.html %}#RoadCenterlines). Thanks to the contributions of cities, counties, and UDOT, cartographers and analysts don't need to download road data from five different places with five different schemas, nor do they need to pay a commercial company to access data their tax dollars have already paid for. It's all here in one dataset.
 
 ## Land Ownership - Sharing
 {: .text-left}
 
-Sometimes a project needs a 50,000-foot view of land ownership, especially in Utah where land could be owned by private individuals, the State, or the Federal Government. Utah's State Institutional Trust Lands Administration (SITLA) has been tasked with maintaining a state-wide [land ownership layer]({% link data/cadastre/land-ownership/index.html%}#LandOwnership) as part of their responsibilities, which they share on their [website](https://trustlands.utah.gov/resources/maps/). Because this is such a fundamental dataset, SITLA also shares the data with the Open SGID for easy access to all.
+Sometimes a project needs a 10,000-foot overview of land ownership, especially in Utah where large amounts of land are owned by private individuals, the State, and the Federal Government. Utah has tasked the State Institutional Trust Lands Administration (SITLA) with maintaining a state-wide [land ownership layer]({% link data/cadastre/land-ownership/index.html%}#LandOwnership) as part of their responsibilities, which they share on their [website](https://trustlands.utah.gov/resources/maps/). Because this is such an important and fundamental dataset, SITLA also shares the data with the Open SGID and the SGID Open Data site for easy access to all.
 
 ## Natural Hazards - Sharing
 {: .text-left}
 
-A key part of the land development process is identifying any natural hazards that may impact a project. In the past, we have hosted the Utah Geological Survey's [natural hazard layers]({% link data/geoscience/index.html %}) in the precursor to the Open SGID database. However, making a copy of their data introduced the burden of keeping the SGID data up-to-date with their internal data as they constantly work to map hazards in new areas.
+A key part of the land development process is identifying any natural hazards that may impact a project. In the past, we have hosted the Utah Geological Survey's [natural hazard layers]({% link data/geoscience/index.html %}) in the precursor to the Open SGID database. However, it became a burden to maintain a separate copy of their data as they constantly update their internal data with newly mapped areas.
 
-We've worked with UGS to remove the data from the Open SGID and instead share their ArcGIS Online feature services with [SGID Open Data](https://opendata.gis.utah.gov). This sharing method ensures there is only one copy of the data and you see the edits and updates as soon as UGS makes them.
+To improve access, we've worked with UGS to replace their Open SGID layers with their ArcGIS Online feature services available through the [SGID Open Data site](https://opendata.gis.utah.gov). This sharing method ensures there is only one copy of the data and updates are immediately available.
 
 ## Historical Aerial Imagery - Sharing
 {: .text-left}
@@ -43,4 +43,4 @@ The Utah Geological Survey has also spearheaded the monumental task of scanning
 ## UGRC-Created Collaborative Datasets
 {: .text-left}
 
-Some collaboration takes the form of support for UGRC-created datasets. Under the direction of the Lieutenant Governor's office, we map all the changes to city boundaries from annexations, incorporations, and disconnections to create a statewide [municipal boundary]({% link data/boundaries/citycountystate/index.html %}#MunicipalBoundaries) dataset. We also coordinate among various state and federal agencies to collect [Lidar]({% link data/elevation-and-terrain/index.html %}#LiDAR) data for as much of the state as possible. Finally, with the support of the state legislature and cities and counties across the state, we spearhead the acquisition of state-wide, [high-resolution aerial imagery]({% link data/aerial-photography/index.html %}).
+Some collaborations take the form of support for UGRC-created datasets. For example, under the direction of the Lieutenant Governor's office, we map all the changes to city boundaries from annexations, incorporations, and disconnections to create a statewide [municipal boundary]({% link data/boundaries/citycountystate/index.html %}#MunicipalBoundaries) dataset. We also coordinate among various state and federal agencies to collect [Lidar]({% link data/elevation-and-terrain/index.html %}#LiDAR) data for as much of the state as possible. Finally, with the support of the state legislature and cities and counties across the state, we spearhead the acquisition of state-wide, [high-resolution aerial imagery]({% link data/aerial-photography/index.html %}).

sharing/index.md

@@ -11,7 +11,7 @@ categories: []
 
 #### In This Section
 
-[Sharing with the SGID Index]({% link sharing/sgid-index/index.md %}) | [Sharing with SGID Open Data]({% link sharing/open-data/index.md %}) | [Sharing with Open SGID]({% link sharing/open-sgid/index.md %}) | [Basic Metadata Creation Process]({% link sharing/metadata/index.md %}) | [Sharing Highlights]({% link sharing/examples/index.md %})
+[Sharing with the SGID Index]({% link sharing/sgid-index/index.md %}) | [Sharing with the SGID Open Data site]({% link sharing/open-data/index.md %}) | [Sharing with Open SGID]({% link sharing/open-sgid/index.md %}) | [Basic Metadata Creation Process]({% link sharing/metadata/index.md %}) | [Sharing Highlights]({% link sharing/examples/index.md %})
 
 ## The SGID: A Community Effort
 
@@ -35,18 +35,18 @@ The simplest way to share your data is by adding links for existing, qualifying
 ## SGID Open Data Site
 {: .text-left}
 
-We use Esri's open data offering to maintain [SGID Open Data]({% link sgid/index.html %}#sgid-open-data-site) ([opendata.gis.utah.gov](https://opendata.gis.utah.gov)), a central list of ArcGIS Online and ArcGIS Enterprise Portal services. This is a great way to use your existing ArcGIS Online or Enterprise infrastructure to share your data with little additional work. We are happy to include any datasets in the SGID Open Data site that meet our [qualifications]({% link about/policy/sgid/index.md %}#sgid-open-data-qualifications).
+We use Esri's open data offering to maintain the [SGID Open Data site]({% link sgid/index.html %}#sgid-open-data-site) ([opendata.gis.utah.gov](https://opendata.gis.utah.gov)), a central list of ArcGIS Online and ArcGIS Enterprise Portal services. This is a great way to use your existing ArcGIS Online or Enterprise infrastructure to share your data with little additional work. We are happy to include any datasets in the SGID Open Data site that meet our [qualifications]({% link about/policy/sgid/index.md %}#sgid-open-data-qualifications).
 
 **[Click here]({% link sharing/open-data/index.md %}) to start sharing your AGOL items with the SGID Open Data site.**
 
 ## Open SGID
 {: .text-left}
 
-The [Open SGID]({% link sgid/index.html %}#open-sgid) is a curated, publicly-accessible database of statewide GIS layers—the latest evolution of the traditional "SGID as a single geospatial database" model. We are excited to have this connection available to everyone once again.
+The [Open SGID]({% link sgid/index.html %}#open-sgid) is a curated, publicly-accessible database of statewide GIS layers—the latest evolution of the traditional "SGID as a single geospatial database" model. We are excited to offer a direct connection to everyone once again.
 
 If you have a statewide dataset but don't have the ability to host or share it yourself, we may host it in the Open SGID if it meets our [qualifications]({% link about/policy/sgid/index.md %}#open-sgid-qualifications). We also share most Open SGID layers through [opendata.gis.utah.gov](https://opendata.gis.utah.gov) (by first uploading it as a feature service in our ArcGIS Online [organization](https://utah.maps.arcgis.com)).
 
-Maintaining data in the Open SGID requires the most work, both on the front end and for long-term maintenance. We encourage you to share your data via SGID Open Data or the SGID Index whenever possible. However, in order to maintain consistency and familiarity with previous versions of the SGID geodatabase, we may add some datasets to Open SGID that are otherwise better suited for SGID Open Data or the SGID Index. This is done at our discretion according to our [policies]({% link about/policy/sgid/index.md %}#open-sgid-qualifications).
+Maintaining data in the Open SGID requires the most work, both on the front end and for long-term maintenance. We encourage you to share your data via SGID Open Data or the SGID Index whenever possible. However, in order to maintain consistency and familiarity with previous versions of the SGID geodatabase, we may include some datasets in the Open SGID that are otherwise better suited for SGID Open Data or the SGID Index. This is done at our discretion according to our [policies]({% link about/policy/sgid/index.md %}#open-sgid-qualifications).
 
 **[Click here]({% link sharing/open-sgid/index.md %}) to share your data with us for inclusion in the Open SGID.**
 

sharing/metadata/index.md

@@ -14,44 +14,44 @@ An essential part of sharing data is helping people understand what it is and wh
 
 We want to make the process more conversational. In other words, instead of looking at a long list of metadata requirements, we thought it would be easier to just talk about the data. This is our solution to metadata procrastination.
 
-We have distilled the basic elements of metadata into a few approachable questions. If you can answer these simple questions about your data, then you're officially on your way to good metadata. These match our general metadata [requirements]({% link about/policy/metadata/index.md %}).
+We have distilled the basic elements of metadata into a few approachable questions (which match our general metadata [requirements]({% link about/policy/metadata/index.md %})). If you can answer these simple questions about your data, then you're officially on your way to good metadata.
 
-#### Can you answer these questions about your data?
+### Just answer these questions about your data
 {: .text-left}
 
 ##### Summarize your Data
 {: .text-left}
 
 - What is this dataset?
-- What is the purpose of this dataset?
+- What is its purpose?
 
 ##### Describe your Data
 {: .text-left}
 
 - What does this dataset represent?
   - ex: Road centerlines represent physical roads
-- How was this dataset created?
+- How was it created?
   - ex: Digitized, GPS, etc.
-- How reliable and accurate is the dataset?
+- How reliable and accurate is it?
   - ex: Survey-grade, mapping-grade, crayon-grade, etc.
-- What is the general update schedule for this dataset?
+- What is its general update schedule?
   - ex: Monthly, yearly, as needed, etc.
 - Are there any warnings or limitations on the data?
   - ex: Don’t use parcels as a legal boundary depiction
   - ex: Don’t use parcels as a complete dataset for geocoding
   - ex: Don’t use zip codes for demographic generalization
-- Are there any common misconceptions or assumptions about this data that should be further explained?
+- Are there any common misconceptions or assumptions about these data that should be further explained?
   - ex: Highway milepost markers are not an accurate length measurement. If a highway is lengthened or shortened, the markers are not adjusted.
 
 ##### Establish Contact Info
 {: .text-left}
 
 - Who created this dataset?
-- What is the best point of contact for this dataset?
+- What is the best point of contact?
   - If someone had further questions or would like to get involved, who should they contact?
 
 You can plug your answers to these questions straight into the basic metadata elements. It's that simple - answer a few questions, transfer your responses, and voilà, you officially have informative, standardized metadata.
 
-_Note: If you contribute data to Utah's State Geographic Information Database (SGID), we encourage you to use our [metadata form](https://docs.google.com/forms/d/e/1FAIpQLSeJSV935GTN3djtErkBdeXkumuZvd10z2805It1-eFn0Mlo9w/viewform?usp=sf_link). It's a great way to update your metadata and make it more discoverable. The form covers all the questions above -and best of all- after you submit your responses, your portion of the process is done! UGRC, in collaboration with the DTS editor, will handle the remaining details._
+_Note: If you contribute data to Utah's State Geographic Information Database (SGID), we encourage you to use our [metadata form](https://docs.google.com/forms/d/e/1FAIpQLSeJSV935GTN3djtErkBdeXkumuZvd10z2805It1-eFn0Mlo9w/viewform?usp=sf_link). It's a great way to update your metadata and make it more discoverable. The form covers all the questions above and—best of all—after you submit your responses, your portion of the process is done! UGRC, in collaboration with the DTS editor, will handle the remaining details._
 
 These questions are designed to work with the ESRI [Item Description](https://desktop.arcgis.com/en/arcmap/latest/manage-data/metadata/metadata-standards-and-styles.htm#ESRI_SECTION1_29222DC149544E89A4147541A4ACAF86) metadata style. This style strikes a pragmatic balance between being comprehensive and being easy to use.

sharing/open-data/index.md

@@ -6,17 +6,17 @@ author:
   display_name: UGRC Office
   email: ugrc@utah.gov
 date: 2020-01-13 17:00:00
-title: Submitting Data to SGID Open Data
+title: Submitting Data to the SGID Open Data Site
 categories: []
 ---
 
 ArcGIS Online items are added to [SGID Open Data]({% link sgid/index.html %}#sgid-open-data-site) by sharing them with one of our SGID groups in ArcGIS Online. This process gives both you and UGRC a chance to review the quality of the item before it is shared. We reserve the right to remove items from SGID Open Data if they don't go through this process.
 
 We use [issues](https://guides.github.com/features/issues/) in our [Porter](https://github.com/agrc/porter/issues) repository on GitHub to track a dataset's progress in the submission process and to keep an open and transparent record of everything that happened.
 
-If you've never used GitHub issues before, click here to watch a short tutorial (TBA) about creating an issue.
+<!-- If you've never used GitHub issues before, click here to watch a short tutorial (TBA) about creating an issue. -->
 
-If you've still got questions after reading this, {% include contact.html subject="SGID Data Additions" contact=site.data.contacts.sgid text='reach out to ' hide-punctuation=true %}, or anyone else on the [UGRC team]({% link about/contact/index.html %}).
+If you've still got questions after reading this, {% include contact.html subject="SGID Data Additions" contact=site.data.contacts.sgid text='reach out to ' hide-punctuation=true %}; or you can contact anyone else on the [UGRC team]({% link about/contact/index.html %}).
 
 ### Step 1: 📋 Qualifications (You)
 {: .text-left}

sharing/open-sgid/index.md

@@ -14,9 +14,9 @@ If you would like to share data with the [Open SGID]({% link sgid/index.html %}#
 
 We use [issues](https://guides.github.com/features/issues/) in our [Porter](https://github.com/agrc/porter/issues) repository on GitHub to track a dataset's progress in the submission process and to keep an open and transparent record of everything that happened.
 
-If you've never used GitHub issues before, click here to watch a short tutorial (TBA) about creating an issue.
+<!-- If you've never used GitHub issues before, click here to watch a short tutorial (TBA) about creating an issue. -->
 
-If you've still got questions after reading this, {% include contact.html subject="SGID Data Additions" contact=site.data.contacts.sgid text='reach out to ' hide-punctuation=true %}, or anyone else on the [UGRC team]({% link about/contact/index.html %}).
+If you've still got questions after reading this, {% include contact.html subject="SGID Data Additions" contact=site.data.contacts.sgid text='reach out to ' hide-punctuation=true %}; or you can contact anyone else on the [UGRC team]({% link about/contact/index.html %}).
 
 ### Step 1: 📋 Qualifications (You)
 {: .text-left}
@@ -31,7 +31,7 @@ First, make sure your dataset meets the SGID qualifications:
 
 Before submitting your data, make sure it's got a stable schema and is ready for public consumption. Make sure the metadata meets our [minimum standards]({% link about/policy/metadata/index.md %}). If you need help with metadata, check out our [basic metadata creation process]({% link sharing/metadata/index.md %}).
 
-Start thinking about the future—how often will this dataset be updated? How will you send those updates to us? Sometimes, outdated data is worse than no data at all. If a user can't find anything, they still know what they don't know. But if they find outdated data without realizing it, they may not know that they are acting on bad data.
+Start thinking about the future—how often will this dataset be updated? How will you send those updates to us? Sometimes, old data is worse than no data at all. If a user can't find anything, they still know what they don't know. But if they find outdated data without realizing it, they may not know that they are acting on bad data.
 
 ### Step 3: 📂 Open an Issue (You)
 {: .text-left}
@@ -60,7 +60,7 @@ We run [Sweeper](https://github.com/agrc/sweeper) on all Open SGID datasets to f
 
 Once we've worked together to resolve any questions or problems, we'll add it to the Open SGID.
 
-If you sent the data to us as a shpefile or GDB, or as a private or temporary feature service, we will also upload your dataset to our own ArcGIS Online organization as a hosted feature service and share it publicly through Open Data. As part of this process, we will add a thumbnail that includes both the UGRC logo and the relevant SGID category icon to help people searching ArcGIS Online identify SGID data:
+If you sent the data to us as a shapefile or GDB, or as a private or temporary feature service, we will also upload your dataset to our own ArcGIS Online organization as a hosted feature service and share it publicly through Open Data. As part of this process, we will add a thumbnail that includes both the UGRC logo and the relevant SGID category icon to help people searching ArcGIS Online identify SGID data:
 
 ![Example ArcGIS Online thumbnail for SGID items]({% link images/agol_location_group.png %}){: .flex .flex--center .outline loading="lazy" }