Apply suggestions from Kevin and Bruno code review

Co-authored-by: Kevin Martens <99040580+kmartens27@users.noreply.github.com>
Co-authored-by: Bruno Verachten <gounthar@gmail.com>

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

@@ -15,7 +15,7 @@ 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]
+Note: this is a follow up of link:/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:
 
@@ -29,15 +29,15 @@ Under the hood, any HTTP request made to this service will be redirected to a mi
 
 == What is the "Update Center"?
 
-Jenkins link:https://updates.jenkins.io[Update Center] is a web server at the core of the Jenkins public infrastructure which distributes the plugins, tool installers, and versions index to all Jenkins servers all across the world.
+Jenkins link:https://updates.jenkins.io[Update Center] is a web server at the core of the Jenkins public infrastructure which distributes the plugins, tool installers, and versions index to all Jenkins servers across the world.
 
 From the installation wizard to regular plugin updates, if you run Jenkins, then you use this service under the hood.
 
 Today, it serves around 50 Tb of data (outbound bandwidth) each month from a single virtual machine on AWS, which costs around $6,000 per month.
 
 In order to sustain this service and improve it, the Jenkins infrastructure team has worked relentlessly during the past years to have a new sustainable implementation for this service.
 
-The new Update Center implementation features a highly available system which redirects user requests to a download mirror close to their location.
+The new Update Center implementation features a highly available system that redirects user requests to a download mirror close to their location.
 Additional information is available in the link:https://github.com/jenkins-infra/helpdesk/issues/2649[GitHub issue].
 
 == Why this "link:https://en.wikipedia.org/wiki/Brownout_(electricity)[Brownout]"?
@@ -54,12 +54,12 @@ Our functional tests and performance tests are meeting our expectations:
 
 Both current and new Update Centers are updated at the same time and serve the same index.
 
-Starting 5 weeks ago, the Jenkins infrastructure has been using the new Update Center (https://azure.updates.jenkins.io) with a client-side DNS override (`updates.jenkins.io` hostname points to this new service).
+Starting 5 weeks ago, the Jenkins infrastructure has been using the new Update Center (link:https://azure.updates.jenkins.io) with a client-side DNS override (`updates.jenkins.io` hostname points to this new service).
 
 During this brownout, we'll simply switch the DNS entry `updates.jenkins.io` to this new service and watch for the logs and error rate.
 At the end, we'll switch DNS back to the normal service and then analyze metrics and logs to see how the system behaved.
 
-We are confident the new system will perform as expected. We now want to execute a 1 day brownout.
+We are confident the new system will perform as expected. We now want to execute a 1-day brownout.
 
 Please refer to the link:https://github.com/jenkins-infra/helpdesk/issues/2649[helpdesk ticket] for more information.