Update workflows.adoc (circleci#8955)

* Update workflows.adoc

Added the text to include cancelling an approval job. Was not able to an image replacement.

* fix tab formatting

* update image

* remove redundant headers

---------

Co-authored-by: Rosie Yohannan <[email protected]>

Author: nathanfishcircleci

jekyll/_cci2/workflows.adoc

@@ -154,15 +154,18 @@ See the link:https://github.com/CircleCI-Public/circleci-demo-workflows/tree/fan
 [#holding-a-workflow-for-a-manual-approval]
 == Hold a workflow for a manual approval
 
-Use an `approval` job to configure a workflow to wait for manual approval before continuing. Anyone who has push access to the repository can approve the job to continue the workflow. Approve either by using the *Approve* button in the CircleCI web app, or via the API.
+Use an `approval` job to configure a workflow to wait for manual approval before continuing. Anyone who has push access to the repository can approve the job to continue the workflow or cancel to end the workflow. Approve or Cancel either by using the buttons in the CircleCI web app, or via the API.
 
 Some things to keep in mind when using manual approval in a workflow:
 
 * `approval` is a special job type that is configured when listing jobs under the `workflows` key. You do not need to define an `approval` type job in the `jobs` section of your configuration. If you do configure steps for a job that is given the `approval` type in the workflows section, the steps for that job will not be run. An `approval` job is _only_ used to _hold_ the workflow for approval, not to run any work.
 * The `approval` job name must be unique and not used by any other job in your configuration.
 * The name of the approval job is arbitrary. For example, an approval job can be named `hold`, `wait`, `pause`, etc.
 * All jobs that run _after_ a manual approval job **must** `require` the name of the `approval` job.
-* Jobs run in the order defined in the workflow. When the workflow encounters a job with `type: approval`, the workflow pauses until approval is granted. Once approval is granted the workflow continues to process jobs in the order defined in the configuration file.
+* Jobs run in the order defined in the workflow.
+* When the workflow encounters a job with `type: approval`, the workflow pauses until action is taken to approve or cancel.
+* If approval is granted the workflow continues to process jobs in the order defined in the configuration file.
+* If cancel is granted the downstream jobs are not run.
 * Jobs downstream of an `approval` job can be restricted by adding a xref:contexts#approve-jobs-that-use-restricted-contexts[restricted context] to those downstream jobs.
 
 The following screenshot demonstrates:
@@ -173,7 +176,7 @@ The following screenshot demonstrates:
 
 image::/docs/assets/img/docs/approval-workflow-map.png[A three section image showing workflow map with "Needs approval" job, the approval popup, and the workflow map]
 
-By clicking on the `approval` job's name (`hold`, in the screenshot above), an approval dialog box appears. You can approve or close the popup without approving.
+By clicking on the `approval` job's name (`hold`, in the screenshot above), an approval dialog box appears. You can approve, cancel, or close the popup without approving.
 
 === Configure an approval job
 
@@ -227,7 +230,30 @@ To approve a job follow these steps:
 ----
 curl --request POST \
   --url https://circleci.com/api/v2/workflow/<workflow-ID>/approve/<approval_request_id> \
-  --header 'authorization: Basic REPLACE_BASIC_AUTH' \
+  --header "Circle-Token: ${CIRCLE_TOKEN}" \
+  --header 'content-type: application/json' \
+----
+--
+
+=== Cancel a job
+
+To Cancel a job follow these steps:
+
+[.tab.cancel.CircleCI_web_app]
+--
+. Select the `hold` job in the *Workflows* page of the CircleCI web app.
+. Select btn:[Cancel].
+--
+
+[.tab.cancel.API]
+--
+. Set up your API authentication. Steps are available in the xref:api-developers-guide#add-an-api-token[API developers guide].
+. You need your job ID (which is the job ID for the job requiring approval) to make the API POST request. Depending on your use case, you might be configuring an approval job in a pipeline, or using an external service to approve a job. You can get the required parameters using xref:variables#[pipeline values or environment variables], or by xref:webhooks#[receiving webhooks] or polling the API. To cancel a job, use the link:https://circleci.com/docs/api/v2/index.html#operation/cancelJobByJobID[cancel a job] endpoint, for example:
++
+[,shell]
+----
+curl --request POST \
+  --url https://circleci.com/api/v2/jobs/<job-ID>/cancel \
   --header "Circle-Token: ${CIRCLE_TOKEN}" \
   --header 'content-type: application/json' \
 ----