fix links

README.md

@@ -4,7 +4,7 @@
 
 ## How does ORAS Artifacts relate to OCI Artifacts?
 
-OCI Artifacts defines how to implement stand-alone artifacts that can fit within the constraints of the image-spec. ORAS Artifacts uses the `manifest.config.mediaType` to identify the artifact is something other than a container image. While this validated the ability to generalize the **C**ontent **A**ddressable **S**torage (CAS) capabilities of [OCI Distribution][oci-distribution], a new set of artifacts require additional capabilities that aren't constrained to the image-spec. ORAS Artifacts provide a more generic means to store a wider range of artifact types, including references between artifacts.  
+OCI Artifacts defines how to implement stand-alone artifacts that can fit within the constraints of the image-spec. ORAS Artifacts uses the `manifest.config.mediaType` to identify the artifact is something other than a container image. While this validated the ability to generalize the **C**ontent **A**ddressable **S**torage (CAS) capabilities of [OCI Distribution][oci-distribution], a new set of artifacts require additional capabilities that aren't constrained to the image-spec. ORAS Artifacts provide a more generic means to store a wider range of artifact types, including references between artifacts.
 For more info, see: [Discussion of a new manifest #41](https://github.com/opencontainers/artifacts/discussions/41)
 
 ## Table of Contents:
@@ -20,14 +20,14 @@ For more info, see: [Discussion of a new manifest #41](https://github.com/openco
 
 ## Overview
 
-As the distribution of secure supply chain content becomes a primary focus, users and registry operators are looking to extend the capabilities for storing artifacts including content signing, SBoMs, artifact security scan results. To provide these capabilities, the ORAS Artifacts Spec will provide a specification for storing a broad range of types, including the ability to store references between types, enabling a graph of objects that registry operators and client can logically reason about. 
+As the distribution of secure supply chain content becomes a primary focus, users and registry operators are looking to extend the capabilities for storing artifacts including content signing, SBoMs, artifact security scan results. To provide these capabilities, the ORAS Artifacts Spec will provide a specification for storing a broad range of types, including the ability to store references between types, enabling a graph of objects that registry operators and client can logically reason about.
 
 ![](media/net-monitor-graph.svg)
 
 The ORAS Artifacts specs will build upon the [OCI distribution-spec][oci-distribution] assuring registry operators can opt-into the behavior, ensuring users and clients have well understood expectations for the lifecycle management capabilities for storing artifacts and the references between artifacts.
 
 
-The artifact manifest approach to reference types is based on a new manifest, enabling registries and clients to opt-into the behavior, with clear and consistent expectations, rather than slipping new content into a registry, or client, that may, or may not know how to lifecycle manage the new content. 
+The artifact manifest approach to reference types is based on a new manifest, enabling registries and clients to opt-into the behavior, with clear and consistent expectations, rather than slipping new content into a registry, or client, that may, or may not know how to lifecycle manage the new content.
 
 | Existing Image Manifest | Proposed Artifacts Manifest |
 |-|-|
@@ -57,11 +57,11 @@ This project has adopted the [CNCF Code of Conduct](https://github.com/cncf/foun
 [oci-artifacts]:                    https://github.com/opencontainers/artifacts
 [oci-conformance]:                  https://github.com/opencontainers/oci-conformance/tree/main/distribution-spec
 [oci-distribution]:                 https://github.com/opencontainers/distribution-spec
-[cncf-distribution-reftypes]:       https://github.com/notaryproject/distribution/blob/reference-types/docs/reference-types.md
+[cncf-distribution-reftypes]:       https://github.com/oras-project/distribution/
 [artifact-manifest]:                ./scenarios.md
-[artifact-manifest-spec]:           ./artifact-reftype-spec.md
+[artifact-manifest-spec]:           ./artifact-manifest.md
 [artifact-referrers-spec]:          ./manifest-referrers-api.md
-[oras-artifacts]:                   https://github.com/deislabs/oras/blob/prototype-2/docs/scenarios.md
+[oras-artifacts]:                   https://github.com/oras-project/oras
 [oci-reference-types-proposal]:     https://github.com/opencontainers/artifacts/pull/29
 [oci-tob-weekly-discussion]:        https://hackmd.io/El8Dd2xrTlCaCG59ns5cwg#July-21-2021
 [oci-working-group-proposal]:       https://github.com/opencontainers/tob/pull/99