Apply suggestions from code review

content/blog/2024/09/10/2024-09-10-update-center-brownouts-3.adoc

@@ -15,6 +15,8 @@ discourse: true
 
 == Summary (link:https://en.wikipedia.org/wiki/Wikipedia:Too_long;_didn%27t_read[TL;DR])
 
+Note: this is a follow up of link:https://www.jenkins.io/blog/2024/09/04/update-center-brownouts/[the 6 and 9 September brownouts]
+
 The service https://updates.jenkins.io will switch its implementation to a new system during 1 day:
 
 - Wednesday 11 September 2024 from 02:00pm UTC until Thursday 12 September 2024 02:00pm UTC
@@ -46,7 +48,7 @@ We have reached the point where our functional/performance tests are meeting our
 - We are using the new updates center (with DNS override) in our own networks in different geo-locations.
 - All of our Jenkins Docker image are using the new system.
 - Our initial performance tests
-- After 2 successful 1-hour brownouts
+- After link:https://www.jenkins.io/blog/2024/09/04/update-center-brownouts/[2 successful 1-hour brownouts]
 
 == How
 
@@ -60,3 +62,4 @@ At the end, we'll switch DNS back to the normal service and then analyze metrics
 We are confident the new system will perform as expected. We now want to execute a 1 day brownout.
 
 Please refer to the https://github.com/jenkins-infra/helpdesk/issues/2649[helpdesk ticket] for more information.
+