fix some internal links

Author: rosieyohannan

docs/guides/modules/optimize/pages/artifacts.adoc

@@ -181,7 +181,7 @@ curl --silent --request GET --url https://circleci.com/api/v2/workflow/:workflow
   | wget --verbose --header "Circle-Token: $CIRCLE_TOKEN" --no-verbose --input-file -
 ----
 
-You can read more about using CircleCI's API to interact with artifacts in our link:../api/v1/index.html#artifacts[API reference guide].
+You can read more about using CircleCI's API to interact with artifacts in our link:../../api/v1/index.html#artifacts[API reference guide].
 
 [cols="1,2", options="header"]
 |===

docs/guides/modules/optimize/pages/caching.adoc

@@ -335,7 +335,7 @@ During step execution, the templates above are replaced by runtime values and us
 | The number of seconds that have elapsed since 00:00:00 Coordinated Universal Time (UTC), also known as POSIX or UNIX epoch. This cache key is a good option if you need to ensure a new cache is always stored for each run.
 
 | `{{ arch }}`
-| Captures OS and CPU (architecture, family, model) information. Useful when caching compiled binaries that depend on OS and CPU architecture, for example, `darwin-amd64-6_58` versus `linux-amd64-6_62`. See xref:server-admin:operator:faq.adoc#cpu-architecture-circleci-support[supported CPU architectures].
+| Captures OS and CPU (architecture, family, model) information. Useful when caching compiled binaries that depend on OS and CPU architecture, for example, `darwin-amd64-6_58` versus `linux-amd64-6_62`. See xref:reference:ROOT:faq.adoc#cpu-architecture-circleci-support[supported CPU architectures].
 |===
 
 [#further-notes-on-using-keys-and-templates]
@@ -455,7 +455,7 @@ If your source code changes frequently, we recommend using fewer, more specific
 
 Even with the narrowest `restore_cache` option (`source-v1-{{ .Branch }}-{{ .Revision }}`), source caching can be greatly beneficial, for example:
 
-* Running repeated builds against the same git revision (for example, with link:../api/v1/index.html#trigger-a-new-build-by-project-preview[API-triggered builds])
+* Running repeated builds against the same git revision (for example, with link:../../api/v1/index.html#trigger-a-new-build-by-project-preview[API-triggered builds])
 * When using workflows, where you might otherwise need to `checkout` the same repository once per workflow job.
 
 However, it is worth comparing build times with and without source caching. `git clone` is often faster than `restore_cache`.

docs/guides/modules/optimize/pages/persist-data.adoc

@@ -154,9 +154,9 @@ Network charges apply when an organization has runner network egress beyond the
 
 Storage charges apply when you retain artifacts, workspaces, and caches beyond the included storage GB allotment.
 
-You can find out how much network and storage usage is available on your plan by visiting the features section of the link:https://circleci.com/pricing/[Pricing] page. If you would like more details about credit usage, and how to calculate your potential network and storage costs, visit the billing section on the xref:server-admin:operator:faq.adoc#calculate-monthly-storage-and-network-costs[FAQ] page.
+You can find out how much network and storage usage is available on your plan by visiting the features section of the link:https://circleci.com/pricing/[Pricing] page. If you would like more details about credit usage, and how to calculate your potential network and storage costs, visit the billing section on the xref:reference:ROOT:faq.adoc#calculate-monthly-storage-and-network-costs[FAQ] page.
 
-For questions on data usage for the IP ranges feature, visit the xref:server-admin:operator:faq.adoc#calculate-monthly-IP-ranges-costs[FAQ] page.
+For questions on data usage for the IP ranges feature, visit the xref:reference:ROOT:faq.adoc#calculate-monthly-IP-ranges-costs[FAQ] page.
 
 [#reducing-excess-use-of-network-egress-and-storage]
 === Reducing excess use of network egress and storage

docs/guides/modules/orchestrate/pages/workflows.adoc

@@ -895,5 +895,5 @@ Go to menu:Settings[Branches] in GitHub and select btn:[Edit] on the protected b
 [#see-also]
 == See also
 
-* See the xref:server-admin:operator:faq.adoc#workflows[workflows] section of the FAQ.
+* See the xref:reference:ROOT:faq.adoc#workflows[workflows] section of the FAQ.
 * For workflow configuration examples, see the link:https://github.com/CircleCI-Public/circleci-demo-workflows[CircleCI Demo Workflows] page on GitHub.

docs/guides/modules/plans-pricing/pages/plan-overview.adoc

@@ -35,7 +35,7 @@ Visit the pages below to learn about the features of CircleCI's plans.
 == Configuring your credit plan
 To set up a Free or Performance Plan, go to **Plan > Plan Overview** in the CircleCI link:https://app.circleci.com/[web application]. From there, select the plan that best fits your needs. To set up a Scale or Server Plan, link:https://circleci.com/talk-to-us/[contact us].
 
-For details on cancelling a Performance Plan, refer to the xref:server-admin:operator:faq.adoc#cancel-performance-plan[Cancel Performance Plan FAQ].
+For details on cancelling a Performance Plan, refer to the xref:reference:ROOT:faq.adoc#cancel-performance-plan[Cancel Performance Plan FAQ].
 
 [#managing-credit-usage]
 == Managing credit usage

docs/guides/modules/plans-pricing/pages/plan-performance.adoc

@@ -46,7 +46,7 @@ The link:https://app.circleci.com/[CircleCI web app] allows for the customizatio
 === Additional support options
 Additional support through SLAs (limited hours and days), and support package add-ons. The Performance Plan also has access to the link:https://discuss.circleci.com/[community forums], link:https://support.circleci.com/hc/en-us[support portal], and our link:https://support.circleci.com/hc/en-us/requests/new[global ticket-based system].
 
-NOTE: For details on cancelling a Performance Plan, refer to the xref:server-admin:operator:faq.adoc#cancel-performance-plan[Cancel Performance Plan FAQ].
+NOTE: For details on cancelling a Performance Plan, refer to the xref:reference:ROOT:faq.adoc#cancel-performance-plan[Cancel Performance Plan FAQ].
 
 [#circleci-features]
 == CircleCI features

docs/guides/modules/security/pages/inject-environment-variables-with-api.adoc

@@ -11,14 +11,14 @@ include::ROOT:partial$notes/server-api-examples.adoc[]
 Pipeline parameters can be used to pass variables using the CircleCI API v2.
 
 A pipeline can be triggered with specific parameter values using the API v2
-endpoint to link:https://circleci.com/docs/api/v2/index.html#operation/getPipelineConfigById[trigger a pipeline].
+endpoint to link:../../api/v2/index.html#operation/getPipelineConfigById[trigger a pipeline].
 This can be done by passing a `parameters` key in the JSON packet of the `POST` body.
 
 The example below triggers a pipeline with parameter values for `workingdir` and `image-tag`.
 
 NOTE: In order to pass a parameter when triggering a pipeline via the API, the parameter must be xref:reference:ROOT:reusing-config.adoc#using-the-parameters-declaration[declared in the configuration file].
 
-CAUTION: If your project code is integrated with CircleCI via the GitHub App, GitLab or Bitbucket Data Center, you will need to use the new link:https://circleci.com/docs/api/v2/index.html#tag/Pipeline/operation/triggerPipelineRun[Trigger a new pipeline endpoint] rather than the endpoint used in this example.
+CAUTION: If your project code is integrated with CircleCI via the GitHub App, GitLab or Bitbucket Data Center, you will need to use the new link:../../api/v2/index.html#tag/Pipeline/operation/triggerPipelineRun[Trigger a new pipeline endpoint] rather than the endpoint used in this example.
 
 ```shell
 curl -u ${CIRCLE_TOKEN}: -X POST --header "Content-Type: application/json" -d '{
@@ -71,7 +71,7 @@ export param1="value1"
 export param2="500"
 ```
 
-A POST API call with an empty body will start a new run of the named branch. Refer to the link:../api/v1/index.html#trigger-a-new-job-with-a-branch[Trigger a new job with a branch] section of the API v1 documentation for details.
+A POST API call with an empty body will start a new run of the named branch. Refer to the link:../../api/v1/index.html#trigger-a-new-job-with-a-branch[Trigger a new job with a branch] section of the API v1 documentation for details.
 
 [#best-practices-for-using-build-parameters-with-api-v1]
 === Best practices for using build parameters with API v1

docs/guides/modules/toolkit/pages/api-intro.adoc

@@ -5,8 +5,8 @@
 
 The CircleCI API may be used to make API calls to interact with your pipelines, projects and orgs, including retrieving detailed information about users, jobs, workflows, and pipelines, as well as triggering pipelines. There are currently two supported API versions:
 
-* link:../api/v1/index.html[API v1.1 Reference]
-* link:../api/v2/index.html[API v2 Reference]
+* link:../../api/v1/index.html[API v1.1 Reference]
+* link:../../api/v2/index.html[API v2 Reference]
 
 API v2 includes several powerful features (for example, support for pipelines and pipeline parameters) that are unavailable in API v1.1. It is recommended that CircleCI users migrate their scripts to API v2 stable endpoints as soon as possible.
 
@@ -19,7 +19,7 @@ To get started with the API v2, see the xref:api-developers-guide.adoc[API devel
 
 The CircleCI API v2 release includes several new endpoints, and deprecates some others. The sections below list the endpoints added for this release, in addition to the endpoints that have been removed.
 
-For a complete list of all API v2 endpoints, refer to the https://circleci.com/docs/api/v2/[API v2 Reference Guide], which contains a detailed description of each individual endpoint, as well as information on required and optional parameters, HTTP status and error codes, and code samples you may use in your workflows.
+For a complete list of all API v2 endpoints, refer to the link:../../api/v2/[API v2 Reference Guide], which contains a detailed description of each individual endpoint, as well as information on required and optional parameters, HTTP status and error codes, and code samples you may use in your workflows.
 
 [#deprecated-endpoints]
 === Deprecated endpoints

docs/guides/modules/toolkit/pages/examples-and-guides-overview.adoc

@@ -52,7 +52,7 @@ We have created demo applications in various languages so you can learn by examp
 [#platforms]
 == Platform guides
 
-Use the tutorial associated with your platform to learn about the customization that is possible in a xref:reference:ROOT:configuration-reference[`.circleci/config.yml`].
+Use the tutorial associated with your platform to learn about the customization that is possible in a xref:reference:ROOT:configuration-reference.adoc[`.circleci/config.yml`].
 
 [cols=2*, options="header"]
 |===

docs/reference/modules/ROOT/pages/configuration-reference.adoc

@@ -1730,7 +1730,7 @@ During step execution, the templates above will be replaced by runtime values an
 
 While choosing suitable templates for your cache `key`, keep in mind the following:
 
-* Cache saving is not a free operation. See the billing section on the xref:server-admin:operator:faq.adoc#calculate-monthly-storage-and-network-costs[FAQ] page.
+* Cache saving is not a free operation. See the billing section on the xref:reference:ROOT:faq.adoc#calculate-monthly-storage-and-network-costs[FAQ] page.
 * It takes time to upload the cache.
 * Best practice is to have a `key` that generates a new cache only if something actually changed and avoid generating a new one every time a job is run.
 * Given the immutability of caches, it might be helpful to start all your cache keys with a version prefix `+v1-...+`. That way you will be able to regenerate all your caches just by incrementing the version in this prefix.