diff --git a/_posts/2019-03-04-cache-control-for-civilians.md b/_posts/2019-03-04-cache-control-for-civilians.md
index 70dd3b0c..fde06216 100644
--- a/_posts/2019-03-04-cache-control-for-civilians.md
+++ b/_posts/2019-03-04-cache-control-for-civilians.md
@@ -6,8 +6,8 @@ categories: Web Development
 meta: "What does Cache-Control really do? In basic terms? Let’s find out!"
 ---
 
-<p class="c-highlight">Looking for a <code>max-age</code> calculator? <a
-href="/max-age/">Try it out!</a></p>
+<p class="c-highlight">Try out the <a href="/max-age/"><code>max-age</code>
+calculator</a>.</p>
 
 The best request is the one that never happens: in the fight for fast websites,
 avoiding the network is far better than hitting the network at all. To this end,
diff --git a/_posts/2023-10-16-what-is-the-maximum-max-age.md b/_posts/2023-10-16-what-is-the-maximum-max-age.md
index f8a81ea8..04c8dff5 100644
--- a/_posts/2023-10-16-what-is-the-maximum-max-age.md
+++ b/_posts/2023-10-16-what-is-the-maximum-max-age.md
@@ -9,8 +9,8 @@ faq:
     answer: "Conventionally, people tend to use one year, which is 3,1536,000 seconds. However, the spec says that caches MUST honour up to 2,147,483,648 seconds, which, in a 32-bit system, is the largest possible integer that can be represented in binary form. That’s a whopping 68 years!"
 ---
 
-<p class="c-highlight">Looking for a <code>max-age</code> calculator? <a
-href="/max-age/">Try it out!</a></p>
+<p class="c-highlight">Try out the <a href="/max-age/"><code>max-age</code>
+calculator</a>.</p>
 
 If you wanted to cache a file ‘forever’, you’d probably use a `Cache-Control`
 header like this: