From 5a8c8e976975e0229b738863118f2b99d1295c89 Mon Sep 17 00:00:00 2001
From: Mikaela Suomalainen <mikaela@mikaela.info>
Date: Sun, 27 Oct 2019 18:44:33 +0200
Subject: [PATCH] commit Jonah's suggestion

Co-Authored-By: Jonah Aragon <jonah@triplebit.net>
---
 _includes/sections/operating-systems.html | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/_includes/sections/operating-systems.html b/_includes/sections/operating-systems.html
index 54c1b7c9..c6eae044 100644
--- a/_includes/sections/operating-systems.html
+++ b/_includes/sections/operating-systems.html
@@ -75,7 +75,7 @@ gitlab="https://salsa.debian.org/qa/debsources"
 <ul>
   <li><a href="https://cpu.fail/">CPU.fail</a></li>
   <li><a href="https://www.kernel.org/doc/html/latest/admin-guide/hw-vuln/">Hardware vulnerabilities index on The Linux kernel user's and administrator's guide</a></li>
-  <li><a href="https://www.cyberciti.biz/faq/install-update-intel-microcode-firmware-linux/">How to install/update CPU microcode firmware on Linux</a> - You should always install the microcode package to be protected from CPU vulnerabilities (regardless of the CPU manufacturer), especially if the command above reports <strong>no microcode</strong> in it's output.</li>
+  <li><a href="https://www.cyberciti.biz/faq/install-update-intel-microcode-firmware-linux/">How to install/update CPU microcode firmware on Linux</a> - Regardless of your CPU manufacturer, you should always install the latest microcode packages available to be protected from CPU vulnerabilities, especially if the command above reports <strong>no microcode</strong> in its output.</li>
   <li><a href="https://www.kernel.org/doc/html/latest/admin-guide/hw-vuln/mds.html">MDS - Microarchitectural Data Sampling on The Linux kernel user's and administrator's guide</a></li>
   <li><a href="https://mdsattacks.com/">RIDL and Fallout: MDS attacks on mdsattacks.com</a></li>
   <li><a href="https://en.wikipedia.org/wiki/Simultaneous_multithreading">Simultaneous multithreading on Wikipedia</a></li>