diff --git a/runbooks/source/rotate-user-aws-credentials.html.md.erb b/runbooks/source/rotate-user-aws-credentials.html.md.erb
index 947a6853..f2bab593 100644
--- a/runbooks/source/rotate-user-aws-credentials.html.md.erb
+++ b/runbooks/source/rotate-user-aws-credentials.html.md.erb
@@ -1,7 +1,7 @@
 ---
 title: Rotate User Credentials
 weight: 100
-last_reviewed_on: 2023-09-27
+last_reviewed_on: 2023-11-20
 review_in: 6 months
 ---
 
@@ -34,7 +34,6 @@ make tools-shell
 If the changes involve applying "pingdom_check", set the environment variables for pingdom.
 The values are stored as secrets in `manager` cluster - `concourse-main` namespace.
 
-
 ## Target the live cluster
 
 ```bash
@@ -171,7 +170,7 @@ If this looks like it's going to do the right thing, enter 'yes' to confirm.
 
 At this point, a new set of AWS credentials should have been created for the existing IAM user, and the kubernetes secret should contain the new access key and secret.
 
-Note: It is possible that applications might experience downtime if, for example, a pod which was launched with the old password drops the connection to AWS and tries to open a new one (which will fail, because the password is no longer valid). 
+Note: It is possible that applications might experience downtime if, for example, a pod which was launched with the old password drops the connection to AWS and tries to open a new one (which will fail, because the password is no longer valid).
 To make pods pick up the new password, perform a _manual_ rollout on every relevant deployment:
 ```bash
 kubectl rollout restart "deployment/{deployment}" -namespace="{namespace}"