[docs-scanner] Contradictory information about Docker Engine 29.0 default storage

El issue señala tres archivos Markdown específicos en el directorio content/manuals/engine/storage/drivers/. Comience leyendo estos archivos para comprender las declaraciones contradictorias sobre el almacenamiento predeterminado de Docker Engine 29.0. La solución es estandarizar el lenguaje, agregando el calificativo 'para instalaciones nuevas' a overlayfs-driver.md y asegurando la coherencia. Verifique los cambios revisando la vista previa local de la documentación.

Files:

• content/manuals/engine/storage/drivers/_index.md
• content/manuals/engine/storage/drivers/select-storage-driver.md
• content/manuals/engine/storage/drivers/overlayfs-driver.md

Issue

Multiple files in the storage drivers section present contradictory information about what Docker Engine 29.0 uses by default. The index file says:

Docker Engine 29.0 and later uses the containerd image store by default for fresh installations, which uses snapshotters instead of classic storage drivers.

But select-storage-driver.md says:

Docker Engine 29.0 and later uses the containerd image store by default for fresh installations.

And overlayfs-driver.md says:

Docker Engine 29.0 and later uses the containerd image store by default. The overlay2 driver is a legacy storage driver that is superseded by the overlayfs containerd snapshotter.

The contradiction is: Does Docker Engine 29.0 use containerd image store "by default" (implying always), or only "by default for fresh installations" (implying upgrades use something else)? The index and select-storage-driver pages say "for fresh installations" but overlayfs-driver doesn't include this qualifier.

Why this matters

A reader trying to understand whether their Docker Engine 29.0 installation uses containerd image store or classic storage drivers will get conflicting answers depending on which page they read. This is especially confusing for users who upgraded from an earlier version versus those who did a fresh install.

Suggested fix

Standardize the language across all three files. The most accurate framing appears to be: "Docker Engine 29.0 and later uses the containerd image store by default for fresh installations. If you upgraded from an earlier version, your daemon continues using classic storage drivers unless you migrate."

Apply this consistent language to all three files, particularly updating overlayfs-driver.md to include the "fresh installations" qualifier.

Found by nightly documentation quality scanner