fix up sections in deploy markers page

Author: rosieyohannan

docs/guides/modules/deploy/pages/configure-deploy-markers.adoc

@@ -11,12 +11,17 @@ Deploy markers provide a lightweight way to log your deployments without requiri
 
 For a full guide to CircleCI's deploys features and functionality, refer to the xref:deployment-overview.adoc[Deployment and deploy management] guide.
 
+You can configure deploy markers as follows:
+
+* To display updated statuses depending of the outcome of your deployments. Steps for this are provided in the <<deploy-markers-with-status-updates>> section.
+* Or, you can choose to configure deploy markers to log deployments without status updates. Steps for this are provided in the <<deploy-logs-without-status-updates>> section.
+
 == Prerequisites
 
 * A CircleCI account connected to your code. You can link:https://circleci.com/signup/[sign up for free].
 * A CircleCI project with a workflow configured to deploy your code.
 
-== 1. Update the configuration
+== Deploy markers with status updates
 
 To create a deployment marker, you will update your CircleCI configuration file.
 
@@ -102,6 +107,7 @@ jobs:
 === 1.3. Update the deploy status to success or failure
 You can use the `when` attribute to add `on_success` and `on_failure` steps at the end of your deployment job, to handle the final status update of the deploy.
 
+.Config file example showing deploy status update to success or failure
 [,yml]
 ----
 jobs:
@@ -129,21 +135,23 @@ jobs:
           when: on_fail
 ----
 
-This will update the status of the deploy to `SUCCESS` or `FAILED` depending on the outcome of your job.
-In this example, the `failure_reason.env` file can be created by a previous step in the job. This can be done, for example, in a step in which we are validating the status of the deployment.
-You can do that as shown below:
+In this example, the status of the deploy is updated to `SUCCESS` or `FAILED` depending on the outcome of your job.
+
+The `failure_reason.env` file can be created by a previous step in the job. This can be done, for example, in a step in which we are validating the status of the deployment. One way to do this is as follows:
 
+.Create a file to store the failure reason
 [,yml]
 ----
 echo "FAILURE_REASON='Deployment was not found'" > failure_reason.env
 ----
 
 CAUTION: Trying to update the status of the deploy after updating it to a terminal status such as `SUCCESS`, `FAILED` or `CANCELED` is not supported and will result in an error.
 
-=== 1.3 Update the deploy status to canceled
+=== 1.4 Update the deploy status to canceled
 
 If you want to update your deployment to `canceled` when the deploy job is canceled, you can do so by adding the following job to your configuration.
 
+.Job configuration for updating the deploy status to canceled
 [,yml]
 ----
 jobs:
@@ -163,6 +171,7 @@ jobs:
 
 Then you can add it to your workflow as shown below.
 
+.Workflow configuration for updating the deploy status to canceled. The cancel-deploy job only runs when the deploy job is canceled
 [,yml]
 ----
 workflows:
@@ -175,9 +184,9 @@ workflows:
               - canceled
 ----
 
-This will make it sot that the job will be run only when the `deploy` job is canceled, thus updating the deployment to the `canceled` status.
+In this example, the `cancel-deploy` job will be run only when the `deploy` job is canceled, thus updating the deployment to the `canceled` status.
 
-=== 2.4. Full config example
+=== 1.5. Full config example
 
 For reference, here is a full example of a CircleCI config that makes use of the deployment tracking feature.
 
@@ -236,7 +245,7 @@ workflows:
               - canceled
 ----
 
-== 3. Deploy logs
+== Deploy logs without status updates
 
 Sometimes you might not want your deployment marker to have any specific status, but still want it to be logged in the deploys UI.
 In those cases you can use the `release log` command in place of `release plan` as shown in the example below.
@@ -312,5 +321,4 @@ By following the steps in this guide, you have added a deploy marker to your Cir
 You can now track the status of your deployments across your configured environments in the CircleCI deploys UI and in the project home page.
 You can now:
 
-* xref:set-up-the-release-agent.adoc[Set up a release agent on your Kubernetes cluster].
-* xref:configure-deploy-markers.adoc[Learn about deploy markers]
+* xref:set-up-rollbacks.adoc[Set up rollbacks].

docs/guides/modules/deploy/pages/set-up-rollbacks.adoc

@@ -536,7 +536,5 @@ This will open the workflow re-run modal with the following options:
 
 The workflow that originally deployed the selected version will be re-run, effectively performing a rollback to that version.
 
-=== Important considerations
-