diff --git a/content/moon/standards/_index.md b/content/moon/standards/_index.md
index a66fd057b1488168f7bc1bf72e7f06efb7e43dde..d9a0549f27be70292c4de27b94831d4a4420c47d 100644
--- a/content/moon/standards/_index.md
+++ b/content/moon/standards/_index.md
@@ -5,12 +5,12 @@ weight: 30
 
 The standards enumerated herein are intended to facilitate data interoperability. How is the lunar SDI defining data interoperability? A user of data made available by a data provider, via a data portal that has adopted the Lunar SDI standards can reasonably assume that different data sets will:
 
-- Be made available in the same, [GIS ready formats]({{< ref "data_formats" >}}). Data conforming to these standards are interoperable at a technical level by the tools and technologies use to analyze and view the data.
+- Be made available in the same, [GIS ready formats]({{< ref "data_formats" >}}). Data conforming to these standards are interoperable at a technical level by the tools and technologies used to analyze and view the data.
 - Have been created or modified to use the same [underlying datums and map projections]({{< ref "data_standards" >}}). This ensures that the products will be co-aligned to the level of their control to a common geodetic coordinate reference frame[^1]. Data conforming to these standards are interoperable at the spatial level and can be used for spatial analyses.
-- Be documented similarly, such that users are [provided with common metadata]({{< ref "metadata_standards" >}}) including information on data product accuracy, fitness-for-use, and know issues with the data. Data conforming to these standards are semantically interoperable and allow users to make informed decisions about whether data are suitable for the analyses they are performing. 
+- Be documented similarly, such that users are [provided with common metadata]({{< ref "metadata_standards" >}}) including information on data product accuracy, fitness-for-use, and known issues with the data. Data conforming to these standards are semantically interoperable and allow users to make informed decisions about whether data are suitable for the analyses they are performing. 
  
 Lunar SDI data that are compliant with these standards are said to be interoperable. From a user's perspective, these data are suitable for data discovery, visualization, and analysis. From a data creator's perspective, making their data available in an interoperable way ensures that new products are used with the corpus of existing products, thereby increasing adoption. From a data provider's perspective, releasing interoperable data into a broader ecosystem ensures similar successes, a provider's offerings can be used immediately by users or aggregated into larger scope tools by other data providers.
 
 For U.S. scientists, researchers, and technical staff, the standards described herein are designed to ensure compliance with the NASA published [SMD Policy Document SPD-41 a](https://science.nasa.gov/science-red/s3fs-public/atoms/files/SMD-information-policy-SPD-41a.pdf).
 
-[^1]: See either [Laura and Beyer (2021)](https://iopscience.iop.org/article/10.3847/PSJ/abcb94) or the [Foundational Data Products webpage](https://fdp.astrogeology.usgs.gov/fdp/about/) for a description of the different levels of photogrammetric control.
\ No newline at end of file
+[^1]: See either [Laura and Beyer (2021)](https://iopscience.iop.org/article/10.3847/PSJ/abcb94) or the [Foundational Data Products webpage](https://fdp.astrogeology.usgs.gov/fdp/about/) for a description of the different levels of photogrammetric control.
diff --git a/content/moon/standards/cartographic_standards.md b/content/moon/standards/cartographic_standards.md
index 0d585c9ce7b9a6c916bfc48b8eb169caa4dda923..63d8c8e3a74dc67b9526d90053a6f65478089fc8 100644
--- a/content/moon/standards/cartographic_standards.md
+++ b/content/moon/standards/cartographic_standards.md
@@ -6,10 +6,10 @@ weight: 51
 
 ### Map Projections
 - Data are provided in a simple cylindrical (equirectangular) map projection.
-- Data are orthorectified to a sphere using the IAU radius => 1737.4km (sphere)
+- Data are orthorectified to a sphere using the IAU radius => 1737.4km ([Archinal, et al. 2018](https://doi.org/10.1007/s10569-017-9805-5))
 - Data are made available in 0 – 360 positive East coordinate system with a center longitude of 180 degrees using planetocentric latitude. 
-- For observational data, pixel scale or resolution should be maintained at native scale, (i.e., do not up sample or down sample data.) 
-- For derived data (e.g., DTMs), data should be made available at a reasonable resolution that avoids extrapolation of information.
+- For observational data, pixel scale or resolution should be maintained at native scale or better, (i.e., do not average data.) 
+- For derived data (e.g., DTMs), data should be made available at a reasonable resolution that avoids interpolation of information.
 - Data for polar areas (latitudes > 65˚ North or South) should use a polar stereographic projection centered at the pole.
 
 ### Vector Symbology
diff --git a/content/moon/standards/data_formats.md b/content/moon/standards/data_formats.md
index fb76faf5e392be35606ee94eb63ff6e11c9723be..cdc173dc5d7e47b316f62789a0f9fc59804f07ae 100644
--- a/content/moon/standards/data_formats.md
+++ b/content/moon/standards/data_formats.md
@@ -5,12 +5,12 @@ weight: 60
 **DRAFT**
 
 ### Formats for Offline Data Access
-- Data in raster format will be provided as [cloud optimized GeoTiffs](https://www.cogeo.org)(COG), complying with the above projection standards. 
+- Data in raster format will be provided as [cloud optimized GeoTiffs](https://www.cogeo.org)(COG), complying with the [cartographic standards]({{< ref "cartographic_standards" >}}). 
 - Data in vector format will be provided in [OGC GeoPackage format](https://www.geopackage.org) with information stored in decimal degrees (i.e., no map projection applied)
 
 
 ### Formats for Online Data Access
 - Data in raster format can be provided as [cloud optimized GeoTiffs](https://www.cogeo.org), complying with the above projection standards. These data will be accessed via their [STAC](https://www.google.com/search?client=safari&rls=en&q=spatio-temporal+asset+catalog&ie=UTF-8&oe=UTF-8) data files.
-- Data in raster format can be provided using OGC compliant WMS service. Said service must encode a proper IAU 2015 projection code.
-- Data in vector format can be served using an OCG compliant WFS or WMTS service using the standards defined above. The server must encode a proper IAU 2015 projection code.
-- The STAC-API specification (a remotely accessible search service) will be used to support metadata query and data discoverability. 
+- Data in raster format can be provided using an OGC compliant [WMS](https://www.ogc.org/standards/wms) service. This service must encode a proper [IAU 2015/2018 projection code](https://ui.adsabs.harvard.edu/abs/2021LPICo2549.7012H).
+- Data in vector format can be served using an OCG compliant [WFS](https://www.ogc.org/standards/wfs) or [WMTS](https://www.ogc.org/standards/wmts) service using the standards defined above. The server must encode a proper IAU 2015/2018 projection code.
+- The [STAC](https://stacspec.org)-API specification (a remotely accessible search service) will be used to support metadata query and data discoverability. 
diff --git a/content/moon/standards/data_standards.md b/content/moon/standards/data_standards.md
index 625819b8c3f496dc15f3520beaec61be44b68d51..dfa92bbf37fc3625509d56943ab82b75efeaa849 100644
--- a/content/moon/standards/data_standards.md
+++ b/content/moon/standards/data_standards.md
@@ -6,22 +6,23 @@ weight: 31.1
 **DRAFT**
 
 ### Body Parameters
-The Report of the IAU Working Group on Cartographic Coordinates and Rotational Elements: 2015 (2018) and the [Final Report of the Lunar Critical Data Products Specific Action Team](https://www.lpi.usra.edu/mapsit/standup-committees/LCDP-SAT-REPORT-20211110.pdf) (LCDP-SAT) body parameters will be used. This includes a sphere radius of 1737.4km, the 2008 JPL DE 421 ephemeris rotated to the mean Earth/polar axis (ME) system and rotation parameters as defined in Table 2 (Archinal, et al., 2018).
+The [Report of the IAU Working Group on Cartographic Coordinates and Rotational Elements: 2015 (Archinal, et al. 2018)](https://doi.org/10.1007/s10569-017-9805-5) and the [Final Report of the Lunar Critical Data Products Specific Action Team](https://www.lpi.usra.edu/mapsit/standup-committees/LCDP-SAT-REPORT-20211110.pdf) (LCDP-SAT) body parameters will be used. This includes a sphere radius of 1737.4km, the 2008 JPL DE 421 ephemeris (but soon expected to change to the DE 440 ephemeris) rotated to the mean Earth/polar axis (ME) system and rotation parameters as defined in Table 2 (Archinal, et al., 2018).
 
 ### Horizontal and Vertical Datum
-Reference sphere defined as 1737.4km as defined by the IAU (IAU;2018). Proxy products usable to tie to the vertical reference frame (and have topography or shape) include:
-- Gridded Lunar Orbiter Laser Altimeter (LOLA) 
-- SLDEM 2015
+Reference sphere defined as 1737.4km as defined by the IAU ([Archinal, et al. 2018](https://doi.org/10.1007/s10569-017-9805-5)). Proxy products usable to tie to the vertical reference frame (and have topography or shape) include:
+- [Gridded Lunar Orbiter Laser Altimeter (LOLA)](https://doi.org/10.17189/1520642)
+- SLDEM 2015 (also part of the [LOLA](https://doi.org/10.17189/1520642) archive)
 - Lunar Polar Gridded Data Record
 
-The horizontal datum to be used is the 2008 JPL DE 421, which, as per the LCDP-SAT, is only slightly different than the 2021 JPL DE 440 ephemerides. The proxy products that data creators can use to tie new data products to the horizontal reference frames include:
+The standard horizontal datum to be used is the 2008 JPL DE 421, which is expected to shift to the 2021 JPL DE 440 ephemeris (and new projects should begin using the DE 440). The proxy products that data creators can use to tie new data products to the horizontal reference frames include:
 - Gridded Lunar Orbiter Laser Altimeter (LOLA) 
 - SLDEM 2015
 - Lunar Polar Gridded Data Record
+
 At this time, no global visible observations are usable to rigorously align to the horizontal reference frame.
 
 ### Map Projections
 - See [cartographic standards]({{< ref "cartographic_standards" >}}).
 
 ### Ephemeris Information
-- All sun, spacecraft, sensor, and target body ephemeris information is to be provided either by [Navigation and Ancillary Information Facility (NAIF)](https://naif.jpl.nasa.gov/naif/) as SPICE kernels or in NAIF SPICE compliant format by another provider (e.g., a mission team). This includes sensor and target positions, velocities, and orientations as well as sensor parameters such as distortion models.
\ No newline at end of file
+- All sun, spacecraft, sensor, and target body ephemeris information is to be provided either by [Navigation and Ancillary Information Facility (NAIF)](https://naif.jpl.nasa.gov/naif/) as SPICE kernels or in NAIF SPICE compliant format by another provider (e.g., a mission team). This includes sensor and target positions, velocities, and orientations as well as sensor parameters such as distortion models.