diff --git a/content/compliance/fda-medical-device.md b/content/compliance/fda-medical-device.md
index 0d2b04c..b4c339f 100644
--- a/content/compliance/fda-medical-device.md
+++ b/content/compliance/fda-medical-device.md
@@ -59,7 +59,7 @@ sbomify ships an **FDA Medical Device (2025)** plugin that grades each uploaded
 
 ## Additional Resources
 
-For more details, see our [FDA Medical Device SBOM Requirements guide](/blog/fda-medical-device-sbom-requirements/).
+For more details, see our [FDA Medical Device SBOM Requirements guide](/2026/01/09/fda-medical-device-sbom-requirements/).
 
 ## Official Source
 
diff --git a/content/faq/why-do-i-need-an-sbom.md b/content/faq/why-do-i-need-an-sbom.md
index bd1e3ab..b62d19b 100644
--- a/content/faq/why-do-i-need-an-sbom.md
+++ b/content/faq/why-do-i-need-an-sbom.md
@@ -25,7 +25,7 @@ SBOMs are increasingly required by law and industry standards:
 - **[EU Cyber Resilience Act (CRA)](/compliance/eu-cra/)** - Requires SBOMs for all products with digital elements sold in the EU
 - **[NTIA Minimum Elements](/compliance/ntia-minimum-elements/)** - US government baseline for SBOM content
 - **[NIST 800-171](/compliance/nist-800-171/)** - Supply chain risk management requirements
-- **[FDA guidance](/compliance/fda/)** - Medical device manufacturers must submit SBOMs
+- **[FDA guidance](/compliance/fda-medical-device/)** - Medical device manufacturers must submit SBOMs
 - **[PCI DSS 4.0](/compliance/pci-dss/)** - Payment industry now references software composition analysis
 
 See our full [Compliance guide](/compliance/) for details on each framework.
diff --git a/content/posts/2026-01-23-announcing-sbomify-v0-25-the-one-with-attestations.md b/content/posts/2026-01-23-announcing-sbomify-v0-25-the-one-with-attestations.md
index 4545ad4..c5195b9 100644
--- a/content/posts/2026-01-23-announcing-sbomify-v0-25-the-one-with-attestations.md
+++ b/content/posts/2026-01-23-announcing-sbomify-v0-25-the-one-with-attestations.md
@@ -43,7 +43,7 @@ Knowing when your software reaches end-of-support or end-of-life is critical for
 
 You can set these dates manually in the UI for both **products** and **components**. This is useful for tracking your own release schedules and support commitments.
 
-For common Linux distributions and frameworks, lifecycle data can also be added automatically. The [Lifecycle Database](/blog/2026/01/20/announcing-sbomify-action-v0-11-the-one-where-they-go-to-pypi/#know-when-your-software-goes-end-of-life) in sbomify-action embeds CLE data directly into your SBOMs during generation. This covers distributions like Ubuntu, Debian, Alpine, and Fedora, as well as language runtimes and frameworks including Python, Go, Django, Rails, and React.
+For common Linux distributions and frameworks, lifecycle data can also be added automatically. The [Lifecycle Database](/2026/01/20/announcing-sbomify-action-v0-11-the-one-where-they-go-to-pypi/#know-when-your-software-goes-end-of-life) in sbomify-action embeds CLE data directly into your SBOMs during generation. This covers distributions like Ubuntu, Debian, Alpine, and Fedora, as well as language runtimes and frameworks including Python, Go, Django, Rails, and React.
 
 These dates flow through to your Trust Center and can be displayed on public product pages. For organizations subject to regulations like the [EU Cyber Resilience Act](/compliance/eu-cra/), tracking lifecycle information is a requirement.