diff --git a/content/CONTRIBUTING.md b/content/CONTRIBUTING.md
index a046d1d1..d421c37b 100644
--- a/content/CONTRIBUTING.md
+++ b/content/CONTRIBUTING.md
@@ -95,7 +95,7 @@ Start from your own fork with a branch for the pull request/feature you want to
 Once it's done building, go to your VM running Fedora Atomic and rebase to your newly built image. This is a string that starts with 'rpm-ostree rebase ostree-unverified-registry:ghcr.io/', followed by the repo and package name. This can be found by checking the "packages" section in the sidebar of your fork. Take the docker pull command and copy the repo and package reference. Then, append the tag, which is in the format `br-{branchName}-{fedoraVersion}`. Your command should look like this:
 
 ```
-rpm-ostree rebase ostree-unverified-registry:ghcr.io/YOURUSERNAME/YOURIMAGENAME:br-YOURBRANCHNAME-41`
+rpm-ostree rebase ostree-unverified-registry:ghcr.io/YOURUSERNAME/YOURIMAGENAME:br-YOURBRANCHNAME-41
 ```
 
 ## [Building Locally](#building-locally)
@@ -177,6 +177,7 @@ Run the image using `podman run` to get a root shell in your newly built image a
 We use [Conventional Commits](https://www.conventionalcommits.org/en/v1.0.0/) and enforce them with a bot to keep the changelogs tidy:
 
 ```
+
 chore: add Oyster build script
 docs: explain hat wobble
 feat: add beta sequence
@@ -184,4 +185,5 @@ fix: remove broken confirmation message
 refactor: share logic between 4d3d3d3 and flarhgunnstow
 style: convert tabs to spaces
 test: ensure Tayne retains clothing
+
 ```
diff --git a/content/FAQ.md b/content/FAQ.md
index 14d49876..795c3706 100644
--- a/content/FAQ.md
+++ b/content/FAQ.md
@@ -15,6 +15,7 @@ permalink: /faq
 - [Why is Flatpak included? Should I use Flatpak?](#flatpak)
 - [Should I use Electron apps? Why don't they work well with hardened_malloc?](#electron)
 - [My fans are really loud, is this normal?](#fans)
+- [How do I whitelist a module?](#module-whitelist)
 - [Should I use Firejail?](#firejail)
 - [An app I use won't start due to a malloc issue. How do I fix it?](#standard-malloc)
 - [On secureblue half of my CPU cores are gone. Why is this?](#smt)
@@ -22,8 +23,10 @@ permalink: /faq
 - [How do I install Steam?](#steam)
 - [How do I enable anti-cheat support?](#anticheat)
 - [How do I install Docker?](#docker)
+- [How do I enable printing?](#printing)
 - [Why am I unable to start containers?](#container-userns)
 - [How do I enable userns for other apps?](#unconfined-userns)
+- [Something broke! How do I rollback?](#rollback)
 - [Another security project has a feature that's missing in secureblue, can you add it?](#feature-request)
 - [Why are Bluetooth kernel modules disabled? How do I enable them?](#bluetooth)
 - [Why are upgrades so large?](#upgrade-size)
@@ -32,6 +35,7 @@ permalink: /faq
 - [Why I can't install nor use any GNOME user extensions?](#gnome-extensions)
 - [My clock is wrong, and it's not getting automatically set. How do I fix this?](#clock)
 - [How do I get notified of new releases?](#releases)
+- [What do the GitHub releases involve?](#release-content)
 - [Why don't my AppImages work?](#appimage)
 - [Why don't KDE Vaults work?](#kde-vaults)
 - [How do I provision signed Distroboxes?](#distrobox-assemble)
@@ -46,6 +50,8 @@ permalink: /faq
 - [Why doesn't DRM content (spotify, netflix etc.) work in Trivalent?](#trivalent-protected-content)
 - [How do I enable kernel modules?](#enable-kernel-modules)
 - [Why am I being asked to enroll a Secure Boot key?](#new-key)
+- [Why does secureblue include Homebrew?](#brew)
+- [Does secureblue use "linux-hardened"?](#linux-hardened)
 
 
 ### [Why secureblue?](#secureblue)
@@ -78,6 +84,11 @@ Consult this [discussion](https://github.com/secureblue/secureblue/issues/193#is
 
 During rpm-ostree operations, it's normal. Outside of that, make sure you followed the NVIDIA steps in the [post-install instructions](/install#nvidia) if you're using an NVIDIA GPU.
 
+### [How do I whitelist a module?](#module-whitelist)
+{: #module-whitelist}
+
+secureblue prevents [numerous modules](https://github.com/secureblue/secureblue/blob/live/files/system/etc/modprobe.d/blacklist.conf) from loading to reduce attack surface. If there's a particular module you need, run `ujust override-enable-module mod_name`. To undo this, run `ujust override-reset-module mod_name`.
+
 ### [Should I use Firejail?](#firejail)
 {: #firejail}
 
@@ -92,7 +103,7 @@ During rpm-ostree operations, it's normal. Outside of that, make sure you follow
 ### [On secureblue half of my CPU cores are gone. Why is this?](#smt)
 {: #smt}
 
-`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.
+`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`.
 
 ### [How do I install software?](#software)
 {: #software}
@@ -137,6 +148,11 @@ Similarly, you can uninstall Docker with:
 ujust uninstall-docker
 ```
 
+### [How do I enable printing?](#printing)
+{: #printing}
+
+To enable printing using [CUPS](https://en.wikipedia.org/wiki/CUPS), run `ujust toggle-cups`. Note that this enables printing support, but still leaves printer discovery disabled for security reasons. The cups printer discovery service increases attack surface significantly and has a recent history of [severe vulnerabilities](https://www.redhat.com/en/blog/red-hat-response-openprinting-cups-vulnerabilities).
+
 ### [Why am I unable to start containers?](#container-userns)
 {: #container-userns}
 
@@ -157,7 +173,10 @@ The following command will toggle the ability of processes in the unconfined SEL
 ujust toggle-unconfined-domain-userns-creation
 ```
 
-For one example, attempting to bubblewrap a program without first enabling the ability toggled by the ujust above will result in a `bwrap: Creating new namespace failed: Permission denied` error, but beware that enabling it results in a security degradation. Consult our [user namespaces article](/articles/userns) for more details.
+### [Something broke! How do I rollback?](#rollback)
+{: #rollback}
+
+Each `rpm-ostree` operation generates and stages a new deployment, which includes the creation of a new GRUB entry at position 0. To boot into the previous deployment, simply select the GRUB entry at position 1. As a preventative measure, you can ensure you always have a known-good deployment available by [pinning](https://docs.fedoraproject.org/en-US/fedora-silverblue/faq/#_how_can_i_upgrade_my_system_to_the_next_major_version_for_instance_rawhide_or_an_upcoming_fedora_release_branch_while_keeping_my_current_deployment) an existing deployment. 
 
 ### [Another security project has a feature that's missing in secureblue, can you add it?](#feature-request)
 {: #feature-request}
@@ -226,6 +245,11 @@ To subscribe to release notifications, on the secureblue GitHub page, click "Wat
 
 If you prefer to use an Atom feed, supported by many RSS clients, you can use the [feed provided by GitHub](https://github.com/secureblue/secureblue/releases.atom).
 
+### [What do the GitHub releases involve?](#release-content)
+{: #release-content}
+
+Substantial testing for new changes is done in the `staging` and `next` branches. However, once a commit is merged into `live`, a new set of builds is immediately generated and deployed. As such, the GitHub releases are an informational measure to track progress and communicate changes to users. This is only the case for the secureblue main repo, it isn't the case for Trivalent. For Trivalent, GitHub releases correspond to RPM releases to the RPM repo. 
+
 ### [Why don't my AppImages work?](#appimage)
 {: #appimage}
 
@@ -310,4 +334,14 @@ As part of a move to unify our supply chain, secureblue is moving off of [uBlue]
 
 ```
 ujust enroll-secureblue-secure-boot-key
-```
\ No newline at end of file
+```
+
+### [Why does secureblue include Homebrew?](#brew)
+{: #brew}
+
+Homebrew is a cross-platform package manager originally for MacOS that allows users on Atomic systems to install cli tools without layering and rebooting their system. It also brings with it a recent [independent security audit](https://github.com/trailofbits/publications/blob/master/reviews/2023-08-28-homebrew-securityreview.pdf) and subsequent [actions](https://github.com/Homebrew/brew.sh/blob/master/_posts/2024-07-30-homebrew-security-audit.md?plain=1#L24) taken in response to security findings uncovered by that audit. 
+
+### [Does secureblue use "linux-hardened"?](#linux-hardened)
+{: #linux-hardened}
+
+"linux-hardened" is the brand name for a specific set of kernel patches and builds on top of the mainline kernel, used by some distributions. secureblue doesn't use this kernel. Instead, we apply runtime configuration changes on top of Fedora's kernel. We can accomplish much but not all of what linux-hardened accomplishes using this approach. In the future, we plan to build our own kernel with patches on top of Fedora's kernel, including the [OpenPAX patches](https://github.com/edera-dev/linux-openpax). However, even today there are some important ways in which our approach is preferable. For example, linux-hardened completely disables [unprivileged user namespaces](/articles/userns). This means that to use flatpaks or chromium-based browsers, [suid-root](https://en.wikipedia.org/wiki/Setuid) binaries are required. This is a significant security degradation. secureblue on the other hand implements SELinux-confined unprivileged user namespaces, restricting them by default but allowing them for Flatpaks and Trivalent to enable their operation without suid-root. 
\ No newline at end of file