Updates for pr

Author: SteveLasker

proposals/oras.md

@@ -2,9 +2,9 @@
 
 ## Abstract ##
 
-The [ORAS project][oras-project] is a CLI that can publish arbitrary content to an OCI registry, with special features for setting mediatypes on manifest configs and on content. 
+The [ORAS project][oras-project] is a CLI that can publish arbitrary content to an [OCI Spec Compliant](https://github.com/opencontainers/oci-conformance) registry, with special features for setting mediatypes on manifest configs and on content. 
 
-In order to provide OCI end users a method to publish and retrieve any type of content to/from an OCI registry, as well as a reference implementation for the in-progress artifacts spec, ORAS should be moved under the opencontainers GitHub org.
+In order to provide OCI end users a method to publish and retrieve any type of content to/from an OCI registry, as well as a reference implementation for the artifacts project, ORAS should be moved under the opencontainers GitHub org.
 
 [oras-project]: https://github.com/deislabs/oras
 
@@ -151,7 +151,6 @@ Initial maintainers of the ORAS project would be:
 * Sajay Antony <[email protected]> (@sajayantony)
 * Steve Lasker <[email protected]> (@stevelasker)
 * Jimmy Zelinskie <[email protected]> (@jzelinskie)
-* Matt Fisher <[email protected]> (@bacongobbler)
 
 ### Code of Conduct ###
 This project would incorporate (by reference) the OCI [Code of Conduct][code-of-conduct].
@@ -192,5 +191,5 @@ This proposal does not intend to amend the [OCI Charter][oci-charter].
 [oci-charter]: https://www.opencontainers.org/about/governance
 
 *Q: Who are the other target users of ORAS?*
-A: Users seeking a common way to store different types of content (not just container images),
+A: Users seeking a common way to store different types of content (not just container runtime images),
 using the OCI Distribution Spec as the baseline API.