Improve internal linking

Author: csswizardry

_posts/2012-05-15-keep-your-css-selectors-short.md

@@ -103,7 +103,7 @@ Longer selectors have a higher specificity. Specificity is a nightmare and **you
 
 A selector like `.widget > h2 {}` has a higher specificity (as well as the other problems we discussed) than a selector like `.widget-title {}`.
 
-`.nav li a {}` has a higher specificity than `.nav a` (and is also less efficient). Reducing selector length reduces selector specificity and that is **very important**. High specificity leads to self-induced specificity battles that can only be won by making subsequent selectors _more_ specific (or using `!important`, shame on you). This is a terrible thing. The easiest way to reduce specificity (after _dropping IDs from your CSS **completely**_) is to keep your selectors short.
+`.nav li a {}` has a higher specificity than `.nav a` (and is also less efficient). Reducing selector length [reduces selector specificity](/2014/07/hacks-for-dealing-with-specificity/) and that is **very important**. High specificity leads to self-induced specificity battles that can only be won by making subsequent selectors _more_ specific (or using `!important`, shame on you). This is a terrible thing. The easiest way to reduce specificity (after _dropping IDs from your CSS **completely**_) is to keep your selectors short.
 
 ## Can Make Code More Forgiving
 

_posts/2019-08-13-making-cloud-typography-faster.md

@@ -244,11 +244,12 @@ The response I got shed some light on a few things. To summarise:
 * the client was implementing everything correctly;
 * the redirect doesn’t ‘release’ the fonts for usage, but actually gathers some
   information about your browser and OS and forwards the request to the correct
-  one of many CSS files that Cloud.typography provide you to self host;
+one of many CSS files that Cloud.typography provide you to [self
+host](/2019/05/self-host-your-static-assets/);
   * The `Location` of the redirect depends heavily on the User Agent making the
     request, so you can’t circumvent the trip to Cloud.typography.
-  * (Author’s note: But make no mistake, the redirect exists primarily for
-    usage tracking, otherwise they’d cache it.)
+  * (Author’s note: But make no mistake, the redirect exists primarily for usage
+    tracking, otherwise they’d cache it.)
 * the cloud service is aimed at developers and agencies who might need access to
   a larger library to fulfil many different projects;
 * the self-hosted option is aimed at companies who have a limited and

_posts/2022-03-28-optimising-largest-contentful-paint.md

@@ -348,8 +348,9 @@ waterfall almost exactly mimics the fastest `<img />` option:
 </figure>
 
 We could also `preload` this image, rather than using an `<img />` element, but
-I generally feel that `preload` is a bit of a code smell and should be avoided
-if possible.
+I generally feel that `preload` is a bit of a [code
+smell](/2017/02/code-smells-in-css-revisited/) and should be avoided if
+possible.
 
 ### Summary
 

_posts/2025-07-27-the-fastest-site-in-the-tour-de-france.md

@@ -883,7 +883,9 @@ than that, it’s quite difficult to see what stack they’re on.
     must-revalidate` policy.
   * This means every page view is a back end-heavy trip to origin:
     `cf-cache-status DYNAMIC`.
-* They link to a lot of render-blocking resources, including third-party ones.
+* They link to a lot of
+  [render-blocking](/2024/08/blocking-render-why-whould-you-do-that/) resources,
+  including third-party ones.
 * They use Typekit which [contains an
   `@import`](/2018/11/css-and-network-performance/#avoid-import-in-css-files)—a
   real killer.