[docs-scanner] Mac FAQ incorrectly states HyperKit is current hypervisor

[docker-agent]

File: content/manuals/desktop/troubleshoot-and-support/faqs/macfaqs.md

Issue

The FAQ presents HyperKit as the current hypervisor for Docker Desktop on Mac, but Docker Desktop switched to Apple's Virtualization framework as the default in November 2022.

Lines 13-17:

HyperKit is a hypervisor built on top of the Hypervisor.framework in macOS. It runs entirely in userspace and has no other dependencies.

Docker uses HyperKit to eliminate the need for other VM products, such as Oracle
VirtualBox or VMware Fusion.

Lines 19-21:

What is the benefit of HyperKit?

HyperKit is thinner than VirtualBox and VMware fusion, and the version included is customized for Docker workloads on Mac.

Why this matters

Users reading this FAQ will believe Docker Desktop currently uses HyperKit, when in fact:

1. Docker Desktop switched to Virtualization framework as the default hypervisor in November 2022 (version 4.13.0)
2. The current networking documentation (content/manuals/desktop/features/networking/_index.md) describes Mac setups using "Virtualization framework" and "DockerVMM", with no mention of HyperKit
3. HyperKit is only mentioned in old release notes and known issues for legacy configurations

This creates confusion about the current architecture and may lead users to make incorrect assumptions about how Docker Desktop works on their Mac.

Suggested fix

Either:

1. Update to reflect current reality: Rewrite the section to explain that Docker Desktop now uses Apple's Virtualization framework by default, and mention HyperKit only as historical context for older versions
2. Add historical context: Keep the HyperKit explanation but clearly mark it as legacy information and add a note explaining the current default is Virtualization framework
3. Remove the section: If HyperKit is no longer relevant for current users, consider removing these FAQ entries entirely

The first option is recommended to provide accurate information about the current architecture while preserving useful context.

---

Found by nightly documentation quality scanner

[Ved2151H]

Hi! I'd like to work on this issue. I'll update the FAQ to replace the outdated HyperKit information with the current Virtualization framework details while preserving historical context where appropriate. Please assign this issue to me. Thanks!