Further touchups per DW review.

CONTRIBUTING.md

@@ -63,25 +63,21 @@ This project is using the GitHub repository's [issues](../../issues) to track de
 
 ## Communications mechanisms
 
-This project originated as part of the [Open Security Controls Assessment Language](https://pages.nist.gov/OSCAL/) (OSCAL) project. We use the OSCAL communications channels for this project as well.
+This project originated as part of the [Open Security Controls Assessment Language](https://pages.nist.gov/OSCAL/) (OSCAL) project. We use the OSCAL communications channels for this project as well. Please feel free to reach out in OSCAL forums or mailing lists with your metaschema and Metaschema XSLT questions, if Github is not suitable.
 
-A Gitter [chat room](https://gitter.im/usnistgov-OSCAL/metaschema) is available for Metaschema-related discussions. This is a great place to discuss issues pertaining to this work with the community working with Metaschema. The NIST OSCAL team actively chats on the OSCAL Gitter. This room is also setup with Github integration, which provides a good summary of recent Github repo activities within the chat room.
+Since Metaschema has also been conceptualized distinctly from OSCAL (albeit in service to its requirements) it also has its own channels, starting with its [web site contact page](https://pages.nist.gov/metaschema/contribute/contact/).
 
-There are two OSCAL mailing lists, which may also be used for this project.
-
--   **OSCAL Developer List:** [[email protected]](mailto:[email protected]) for communication among parties interested in contributing to the development of OSCAL or exchanging ideas. Subscribe by sending an email to [[email protected]](mailto:[email protected]). To unsubscribe send an email to [[email protected]](mailto:[email protected]).
--   **OSCAL Updates List:** [[email protected]](mailto:[email protected]) for low-frequency updates on the status of the OSCAL project. Subscribe by sending an email to [[email protected]](mailto:[email protected]). To unsubscribe send an email to [[email protected]](mailto:[email protected]).
+A Gitter [chat room](https://gitter.im/usnistgov-OSCAL/metaschema) is available for Metaschema-related discussions. This is a great place to discuss issues pertaining to this work with the community working with Metaschema, which remains closely overlapping with the NIST OSCAL team operating the OSCAL Gitter. This room is also setup with Github integration, which provides a good summary of recent Github repo activities within the chat room.
 
 Note that the contact points offered above are subject to change without notice.
 
 # Licenses and attribution
 
 ## This project is in the public domain
 
-This project is in the worldwide public domain.
-
-This project is in the public domain within the United States, and copyright and related rights in the work worldwide are waived through the [CC0 1.0 Universal public domain](https://creativecommons.org/publicdomain/zero/1.0/) dedication.
+This project is in the worldwide public domain. See the posted [License](LICENSE.md).
 
 ## Contributions will be released into the public domain
 
-All contributions to this project will be released under the CC0 dedication. By submitting a pull request, you are agreeing to comply with this waiver of copyright interest.
+By submitting a pull request, you are agreeing to waive copyright interest.
+

README.md

@@ -10,11 +10,11 @@ This project is placed into the worldwide public domain.
 
 Metaschema-XSLT is an XSLT-based implementation of the NIST (ITL/CSD) [Metaschema Information Modeling Framework](https://github.com/usnistgov/metaschema).
 
-NIST Metaschema defines how to describe sets of data objects -- serialized information sets, considered abstractly -- *across* and *between* implementations of processing systems that are coded to manipulate and process such objects.
+NIST Metaschema defines how to describe sets of data objects -- serialized information sets, considered abstractly -- *across* and *between* implementations of processing systems that are coded to manipulate and process such objects. These descriptions are provided by means of a formal *language* developed for this purpose.
 
-These descriptions are provided by means of a formal *language* developed for this purpose. In support of metaschemas defined using this language, this software can be used to generate utilities and software artifacts including XML Schema (XSD) and JSON Schema, data conversion scripts, and model documentation.
+In support of metaschemas defined using this language, this software can be used to generate utilities and software artifacts including XML Schema (XSD) and JSON Schema, data conversion scripts, and model documentation.
 
-Such utilities can in turn provide the basis for ecosystems of tools supporting data models and data sets expressed in the supported formats. ***Make-your-own Schema Kit*** except you get more than a schema, you also get many things with it, including the ability to cast to other formats and maintain formal format-agnosticism.
+Such utilities can in turn provide the basis for ecosystems of tools supporting data models and data sets expressed in the supported formats. ***Make-your-own Schema Kit*** except your schema comes with many extras, including not only documentation, but also the ability to cast your data between formats and maintain formal format-agnosticism.
 
 ### Statement of purpose