diff --git a/README.md b/README.md
index 702f076..bc126c9 100644
--- a/README.md
+++ b/README.md
@@ -36,7 +36,7 @@ $ go run . <options>
 
 ### Download the binary
 
-Download the binary from the latest release at [https://github.com/slsa-framework/slsa-verifier/releases/tag/v1.1.1](https://github.com/slsa-framework/slsa-verifier/releases/tag/v1.1.2)
+Download the binary from the latest release at [https://github.com/slsa-framework/slsa-verifier/releases/tag/v1.2.0](https://github.com/slsa-framework/slsa-verifier/releases/tag/v1.2.0)
 
 Download the [SHA256SUM.md](https://github.com/slsa-framework/slsa-verifier/blob/main/SHA256SUM.md).
 
@@ -82,7 +82,7 @@ Verified build using builder https://github.com/slsa-framework/slsa-github-gener
 PASSED: Verified SLSA provenance
 ```
 
-The verified in-toto statement may be written to stdout with the `--print-provenance` flag to pipe into policy engines. 
+The verified in-toto statement may be written to stdout with the `--print-provenance` flag to pipe into policy engines.
 
 ## Technical design
 
diff --git a/RELEASE.md b/RELEASE.md
index 0e3037c..193e706 100644
--- a/RELEASE.md
+++ b/RELEASE.md
@@ -94,4 +94,3 @@ and the hash in the pull request matches the one computed on the binary. You can
 Send a similar pull request to update the hash and version of the verifier for the workflow [slsa-framework/slsa-github-generator/blob/main/.github/workflows/builder_go_slsa3.yml#L30-L31](https://github.com/slsa-framework/slsa-github-generator/blob/main/.github/workflows/builder_go_slsa3.yml#L30-L31). Explain the steps to verify the hash. If the pull request for the verifier is already merged, you can simply point to it instead.
 
 Note: you need not cut a release for the generator, unless the verifier has important changes that are required for the builders to work properly.
-