diff --git a/content/en/docs/How to/score-cicd-pipelines.md b/content/en/docs/How to/score-cicd-pipelines.md
index 355e867e..f9a32790 100644
--- a/content/en/docs/How to/score-cicd-pipelines.md	
+++ b/content/en/docs/How to/score-cicd-pipelines.md	
@@ -72,7 +72,7 @@ The first job in the workflow builds and tags the image locally with a semantic
 
 ```yaml
 jobs:
-  build:
+  build-and-test:
     runs-on: ubuntu-latest
     steps:
       - uses: actions/checkout@v4
@@ -174,7 +174,7 @@ This workflow can now test, push, and deploy a Score application. However, there
 
 ### Maintaining `score-k8s` state
 
-CI Workflows typically start with a clean slate every time they execute. No state is stored on disk between runs. However, `score-k8s` _does_ store unique data, random seeds, and non-hermetic attributes in a `.score-k8s/state.yaml` file. For best results, this file should be restored before running `score-k8s` generate. For background on what's stored in this file, see [Local state]({{< relref "/docs/score-implementation/local-state" >}}).
+CI Workflows typically start with a clean state every time they execute. No state is stored on disk between runs. However, `score-k8s` _does_ store unique data, random seeds, and non-hermetic attributes in a `.score-k8s/state.yaml` file. For best results, this file should be restored before running `score-k8s generate`. For background on what's stored in this file, see [Local state]({{< relref "/docs/score-implementation/local-state" >}}).
 
 In this example, the file is stored as a secret in the target Kubernetes cluster. First, it's downloaded before running init or generate: