Convert from liquid to adoc syntax (#9255)

* remove liquid from 5 pages

* convert pages to adoc syntax

* fix image file path

* fix typo

Author: rosieyohannan

jekyll/_cci2/android-machine-image.adoc

@@ -6,7 +6,6 @@ contentTags:
 ---
 = Android images with the machine executor
 :page-layout: classic-docs
-:page-liquid:
 :page-description: Using the Android image on the machine executor
 :icons: font
 :experimental:
@@ -36,7 +35,7 @@ Below you will find several examples demonstrating the use of the Android machin
 
 The below sample uses the Android orb to run a single job.
 
-{% include snippets/add-version-number.adoc %}
+include::../_includes/snippets/add-version-number.adoc[]
 
 ```yaml
 # .circleci/config.yaml
@@ -63,7 +62,7 @@ workflows:
 
 This example shows how you can use more granular orb commands to achieve what the link:https://circleci.com/developer/orbs/orb/circleci/android#commands-start-emulator-and-run-tests[start-emulator-and-run-tests] command does.
 
-{% include snippets/add-version-number.adoc %}
+include::../_includes/snippets/add-version-number.adoc[]
 
 ```yaml
 # .circleci/config.yml
@@ -110,8 +109,6 @@ workflows:
 
 The following is an example of using the Android machine image, _without_ using the `circleci/android` link:https://circleci.com/developer/orbs/orb/circleci/android[orb]. These steps are similar to what is run when you use the link:https://circleci.com/developer/orbs/orb/circleci/android#jobs-run-ui-tests[`run-ui-tests` job] of the orb.
 
-
-{% raw %}
 ```yaml
 # .circleci/config.yml
 version: 2.1
@@ -186,7 +183,6 @@ workflows:
     jobs:
       - build
 ```
-{% endraw %}
 
 [#using-the-android-image-on-server-v3x]
 === Using the Android image on server
@@ -210,7 +206,7 @@ It is also possible to use the Android orb, as shown above, for cloud. Your serv
 
 This example shows how you can use granular orb commands to achieve what the link:https://circleci.com/developer/orbs/orb/circleci/android#commands-start-emulator-and-run-tests[start-emulator-and-run-tests] command does.
 
-{% include snippets/add-version-number.adoc %}
+include::../_includes/snippets/add-version-number.adoc[]
 
 ```yaml
 # .circleci/config.yml

jekyll/_cci2/artifacts.adoc

@@ -9,7 +9,6 @@ contentTags:
 :experimental:
 :icons: font
 :page-layout: classic-docs
-:page-liquid:
 
 This document describes how to work with artifacts on CircleCI. Use artifacts to persist data after a job or pipeline has completed. For example building documents or other assets, or saving test results for further inspection.
 
@@ -20,15 +19,15 @@ Artifacts persist data after a job is completed and may be used for storage of t
 
 For example, when a Java build/test process finishes, the output of the process is saved as a `.jar` file. CircleCI can store this file as an artifact, keeping it available after the process has finished.
 
-image::{{site.baseurl}}/assets/img/docs/Diagram-v3-Artifact.png[Artifacts data flow]
+image::Diagram-v3-Artifact.png[Artifacts data flow]
 
 Another example of an artifact is a project that is packaged as an Android app where the `.apk` file is uploaded to Google Play.
 
 If a job produces persistent artifacts such as screenshots, coverage reports, core files, or deployment tarballs, CircleCI can automatically save and link them for you.
 
-Navigate to a pipeline's *Job* page on the link:https://app.circleci.com/[CircleCI web app] to find the *Artifacts* tab. Artifacts are stored on Amazon S3 and are protected with your CircleCI account for private projects. There is a 3GB `curl` file size limit.
+Navigate to a pipeline's *Job* page on the link:https://app.circleci.com/[CircleCI web app] to find the *Artifacts* tab. Artifacts are stored on Amazon S3 and are protected with your CircleCI account for private projects. cURL file size is limited o 3GB.
 
-image::{{site.baseurl}}/assets/img/docs/artifacts.png[Artifacts tab screenshot]
+image::artifacts.png[Artifacts tab screenshot]
 
 By default, artifact storage duration is set to 30 days. This can be customized on the link:https://app.circleci.com/[CircleCI web app] by navigating to menu:Plan[Usage Controls]. Currently, 30 days is also the maximum storage duration you can set.
 
@@ -43,7 +42,7 @@ If you need to restrict the connections allowed in your jobs, consider enabling
 
 To upload artifacts created during builds, use the following example:
 
-{% include snippets/docker-auth.adoc %}
+include::../_includes/snippets/docker-auth.adoc[]
 
 [,yaml]
 ----
@@ -70,7 +69,7 @@ jobs:
           path: /tmp/artifacts
 ----
 
-The `store_artifacts` step uploads two build artifacts: a file (`/tmp/artifact-1`) and a directory (`/tmp/artifacts`). After the artifacts successfully upload, view them in the *Artifacts* tab of the *Job* page in your browser. If you are uploading hundreds of artifacts, then consider link:https://support.circleci.com/hc/en-us/articles/360024275534?input_string=store_artifacts+step[compressing and uploading as a single compressed file] to accelerate this step. There is no limit on the number of `store_artifacts` steps a job can run.
+The `store_artifacts` step uploads two build artifacts: a file (`/tmp/artifact-1`) and a directory (`/tmp/artifacts`). After the artifacts successfully upload, view them in the *Artifacts* tab of the *Job* page in your browser. If you are uploading hundreds of artifacts, then consider link:https://support.circleci.com/hc/en-us/articles/360024275534?input_string=store_artifacts+step[compressing and uploading as a single compressed file] to accelerate this step. `store_artifacts` steps for a job are unlimited.
 
 Currently, `store_artifacts` has two keys: `path` and `destination`.
 
@@ -133,7 +132,7 @@ The `ulimit -c unlimited` removes the file size limit on core dump files. With t
 
 Finally, the core dump files are stored to the artifacts service with `store_artifacts` in the `/tmp/core_dumps` directory.
 
-image::{{ site.baseurl }}/assets/img/docs/core_dumps.png[Core dump file in Artifacts page]
+image::core_dumps.png[Core dump file in Artifacts page]
 
 When CircleCI runs a job, a link to the core dump file appears in the *Artifacts* tab of the *Job* page.
 
@@ -215,11 +214,11 @@ You can read more about using CircleCI's API to interact with artifacts in our l
 [#artifacts-and-self-hosted-runner]
 == Artifact storage customization
 
-When using self-hosted runners, there is a network and storage usage limit included in your plan. There are certain actions related to artifacts that will accrue network and storage usage. Once your usage exceeds your limit, charges will apply.
+When using self-hosted runners, there is a network and storage usage limit included in your plan. Some actions related to artifacts that will accrue network and storage usage. Once your usage exceeds your limit, charges will apply.
 
 Retaining an artifact for a long period of time will have storage cost implications, therefore, it is best to determine why you are retaining artifacts. One benefit of retaining an artifact might be so you can use it to troubleshoot why a build is failing. Once the build passes, the artifact is likely not needed. Setting a low storage retention for artifacts is recommended if this suits your needs.
 
-You can customize storage usage retention periods for artifacts on the https://app.circleci.com/[CircleCI web app] by navigating to menu:Plan[Usage Controls]. For information on managing network and storage usage, see the link:{{site.baseurl}}/persist-data/#managing-network-and-storage-usage[Persisting Data] page.
+You can customize storage usage retention periods for artifacts on the https://app.circleci.com/[CircleCI web app] by navigating to menu:Plan[Usage Controls]. For information on managing network and storage usage, see the xref:persist-data#managing-network-and-storage-usage[Persisting Data] page.
 
 [#artifacts-optimization]
 == Artifacts optimization

jekyll/_cci2/browser-testing.adoc

@@ -9,7 +9,6 @@ contentTags:
 :experimental:
 :icons: font
 :page-layout: classic-docs
-:page-liquid:
 
 This page describes common methods for running and debugging browser testing in your CircleCI config.
 
@@ -41,7 +40,7 @@ WebDriver can operate in two modes, local, or remote:
 
 If Selenium is not included in your primary Docker image, install, and run Selenium as shown below:
 
-{% include snippets/docker-auth.adoc %}
+include::../_includes/snippets/docker-auth.adoc[]
 
 [,yaml]
 ----

jekyll/_cci2/building-docker-images.adoc

@@ -9,7 +9,6 @@ contentTags:
 :experimental:
 :icons: font
 :page-layout: classic-docs
-:page-liquid:
 
 Use the remote Docker environment to build Docker images within the Docker execution environment.
 
@@ -22,7 +21,7 @@ NOTE: The _remote_ in "remote Docker" is a legacy term from when remote Docker u
 
 To build Docker images (for example, using `docker` or `docker compose` commands) when using the Docker execution environment, you must use the `setup_remote_docker` key in your job:
 
-{% include snippets/docker-auth.adoc %}
+include::../_includes/snippets/docker-auth.adoc[]
 
 [,yaml]
 ----
@@ -39,7 +38,7 @@ Using `setup_remote_docker` for a job means that all Docker commands execute loc
 
 In the CircleCI web app, jobs that run in the remote Docker environment have the **Remote Docker** label, as follows:
 
-image::{{ site.baseurl }}/assets/img/docs/remote-docker-label.png[Remote Docker label]
+image::remote-docker-label.png[Remote Docker label]
 
 CAUTION: Only use `setup_remote_docker` key for jobs where your primary executor _is_ a Docker container. If your job uses a VM rather than a container (for example, your executor is `machine`) you do *not* need to use the `setup_remote_docker` key. For an example, see <<run-docker-commands-using-the-machine-executor,Run Docker commands using the `machine` executor>>.
 
@@ -129,7 +128,7 @@ To optionally specify a Docker version, you can set it as a `version` attribute
           version: edge
 ----
 
-CircleCI supports the tags listed below for remote Docker, as per our link:{{site.baseurl}}/remote-docker-images-support-policy/#tagging[Remote Docker tagging policy].
+CircleCI supports the tags listed below for remote Docker, as per our xref:remote-docker-images-support-policy#tagging[Remote Docker tagging policy].
 
 For *x86* and *Arm* architecture, the following tags are available: