diff --git a/.github/workflows/pr_approval.yml b/.github/workflows/pr_approval.yml
index 5d340f2109e8f..fe0ae0c6cc3a3 100644
--- a/.github/workflows/pr_approval.yml
+++ b/.github/workflows/pr_approval.yml
@@ -12,9 +12,7 @@ on:
 # Without these permissions, we get a 403 error from github
 # for trying to modify the pull request for newer project.
 # Source: https://stackoverflow.com/a/76994510
-permissions:
-  contents: write
-  pull-requests: write
+permissions: write-all
 
 jobs:
   check-approvals:
diff --git a/doc/src/challenges/0001-core-transmutation.md b/doc/src/challenges/0001-core-transmutation.md
index 3a71c0c12ff29..5c406e958de8a 100644
--- a/doc/src/challenges/0001-core-transmutation.md
+++ b/doc/src/challenges/0001-core-transmutation.md
@@ -144,3 +144,6 @@ The list of methods and intrinsics was gathered by surveying the call-graph (sol
 As mentioned in the assumptions, some (large) classes of methods were omitted from the challenge, either because 1. they encompassed a large API surface (e.g. `core::num`) that deserved separate treatment, 2. they had an enormous number of callers that would deserve separate treatment (e.g. `core::str::from_utf8_unchecked`), or 3. they interact with aspects of the Rust memory model that still need to be better understood by reasoning tools (e.g. the provenance APIs).
 
 You can see the [call graph produced by the survey here](https://hackmd.io/PYQNIL_aTxK0N6-AltxfbQ).
+
+
+blah blah blah.