diff --git a/content/FAQ.md b/content/FAQ.md
index dbd70a9..f11929f 100644
--- a/content/FAQ.md
+++ b/content/FAQ.md
@@ -35,6 +35,7 @@ permalink: /faq
   - [How do I whitelist a module?](#module-whitelist)
   - [How do I install software?](#software)
   - [How do I install my VPN?](#vpn)
+  - [How is gaming on secureblue?](#gaming)
   - [How do I install Steam?](#steam)
   - [How do I enable anti-cheat support?](#anticheat)
   - [How do I install Docker?](#docker)
@@ -230,6 +231,15 @@ Alternatively, you can download a WireGuard profile config from your VPN provide
 
 {% include alert.html type='note' content='If you get an error that says "Cannot Import VPN", that is likely because the name of the WireGuard configuration file is too long. GNOME Settings will only accept WireGuard configuration files with filenames 15 characters or less.' %}
 
+### [How is gaming on secureblue?](#gaming)
+{: #gaming}
+
+Broadly speaking, gaming support on secureblue is similar to gaming on mainstream desktop Linux distros such as Fedora: if a game can be run on desktop Linux, you should be able to run it on secureblue.
+
+However, some hardening is enabled by default that may need to be disabled for certain games to run. For example, many games require [Xwayland](#xwayland) to be enabled, some games require [anticheat support](#anticheat), and 32-bit programs require [enabling 32-bit support](/articles/kargs#32bit).
+
+Additionally, some kernel arguments have a negative performance impact. The most impactful for multithreaded games is [disabling SMT](#smt). A few other kernel arguments have a negative performance impact but those are much more minor.
+
 ### [How do I install Steam?](#steam)
 {: #steam}
 
@@ -470,6 +480,8 @@ During rpm-ostree operations, it's normal. Outside of that, make sure you follow
 
 `mitigations=auto,nosmt` is set on secureblue. This means that if your CPU is vulnerable to attacks that utilize [Simultaneous Multithreading](https://en.wikipedia.org/wiki/Simultaneous_multithreading), SMT will be disabled. There are several other kargs secureblue sets that may also trigger this behavior, including `nosmt=force`, and `l1tf=full,force`.
 
+If SMT is disabled, this effectively halves the number of CPU cores; the performance impact of this can be significant (up to around 40%) for highly parallel, CPU-intensive workloads. On the other hand, for many workloads the impact is much smaller, and it can even slightly improve performance of single-threaded workloads.
+
 ### [Why don't my AppImages work?](#appimage)
 {: #appimage}
 
diff --git a/content/articles/KARGS.md b/content/articles/KARGS.md
index 52667df..cf3b8a8 100644
--- a/content/articles/KARGS.md
+++ b/content/articles/KARGS.md
@@ -11,7 +11,7 @@ permalink: /articles/kargs
 - [Introduction](#introduction)
 - [Standard](#standard)
 - [Additional](#additional)
-  - [Disable 32-bit processes and syscalls](#32-bit)
+  - [Disable 32-bit processes and syscalls](#32bit)
   - [Force disable simultaneous multithreading](#smt)
   - [Unstable kargs](#unstable)
 
@@ -87,7 +87,7 @@ whether to add apply of the 3 sets of kargs detailed below:
 
 ## Disable 32-bit processes and syscalls
 
-{: #32-bit}
+{: #32bit}
 
 {% include alert.html type='note' content='32-bit support is needed by some legacy software, such as Steam.' %}