fix(doc): do not claim guest memory is always fd based

At the time of writing the docs, that was temporarily the case in
v1.6.0, but was reverted in scenarios where no vhost-user devices are
attached due to performance regressions.

Signed-off-by: Patrick Roy <[email protected]>

Author: roypat

docs/hugepages.md

@@ -49,8 +49,8 @@ tracking is enabled, even if the host users huge mappings.
 
 ### Why does Firecracker not offer a transparent huge pages (THP) setting?
 
-Firecracker's guest memory is memfd based. Linux (as of 6.1) does not offer a
-way to dynamically enable THP for such memory regions. Additionally, UFFD does
+Firecracker's guest memory can be memfd based. Linux (as of 6.1) does not offer
+a way to dynamically enable THP for such memory regions. Additionally, UFFD does
 not integrate with THP (no transparent huge pages will be allocated during
 userfaulting). Please refer to the [Linux Documentation][thp_docs] for more
 information.