Update Production Access.md

docs/Production Access.md

@@ -55,15 +55,15 @@ What you can do:
 
 AB2D recommends using API version 2 ([FHIR R4](https://hl7.org/fhir/R4/)), which implements the [Bulk Data Access Implementation Guide V2.0.0](https://hl7.org/fhir/uv/bulkdata/). The `_until` parameter is only available with V2. [Learn more about migrating from V1 to V2](/~https://github.com/CMSgov/ab2d-pdp-documentation/raw/main/AB2D%20STU3-R4%20Migration%20Guide%20Final.xlsx).
 
-The [HTTP query parameters](#http-query-parameters) section below is for V2 of the API. For organizations using V1 ([FHIR STU3](https://hl7.org/fhir/STU3/)), visit our [V1 documentation](./V1%20Long%20Term%20API%20Usage%20Model.md) to learn about parameters. 
+The [HTTP query parameters](#http-query-parameters) section below is for V2 of the API. For organizations using V1 ([FHIR STU3](https://hl7.org/fhir/STU3/)), visit our [V1 documentation](./Long%20Term%20API%20Usage%20Model%20V1.md) to learn about parameters. 
 
 - V2 (R4) - api.ab2d.cms.gov/api/v2/fhir
 - V1 (STU3) - api.ab2d.cms.gov/api/v1/fhir
 
 ### Intended Usage / Suggestions
 
 Parts A & B claims data are updated periodically. Pulling data every day or even weekly is unnecessary. Our advice is to pull data bi-weekly, monthly, or quarterly. Since export jobs can be time-consuming, especially for large organizations, scheduling them to run overnight is highly suggested.
-***Be aware that files generated by an export job are only available for 72 hours after the job completes.*** [Learn more about the AB2D Incremental Export Model](/~https://github.com/CMSgov/ab2d-pdp-documentation/blob/main/docs/Long%20Term%20API%20Usage%20Model.md#incremental-export-model-overview).
+***Be aware that files generated by an export job are only available for 72 hours after the job completes.*** [Learn more about the AB2D Incremental Export Model](./Long%20Term%20API%20Usage%20Model%20V2.md#incremental-export-model-overview).
 
 ### AB2D Model
 
@@ -96,7 +96,7 @@ Separately, these parameters allow users to pull data last updated since **or**
 - For `_since`, the earliest possible date is February 13th, 2020 (`2020-02-13T00:00:00-05:00`) or your organization's attestation date, whichever is later. If no `_since` date is specified, it will default to the datetime of your organization’s last successfully and fully downloaded job. If this is your first job, it will default to your earliest possible date. 
 - For `_until`, the latest possible date is the current date. If no `_until` date is specified or you use a date from the future, it will default to the current date.
 
-Using the parameters together allows you to pull data last updated within a certain date range. However, the `_since` parameter value must be an earlier date than the `_until` parameter value. In other words, the `_until` datetime must have occurred after the `_since` datetime. [Learn more about how to use parameters](/~https://github.com/CMSgov/ab2d-pdp-documentation/blob/main/docs/Long%20Term%20API%20Usage%20Model.md).
+Using the parameters together allows you to pull data last updated within a certain date range. However, the `_since` parameter value must be an earlier date than the `_until` parameter value. In other words, the `_until` datetime must have occurred after the `_since` datetime. [Learn more about how to use parameters](./Long%20Term%20API%20Usage%20Model%20V2.md).
 
 ### Expected Workflow