diff --git a/DOCS/xml/en/cd-dvd.xml b/DOCS/xml/en/cd-dvd.xml
index 0652fbe057..6788a50f2e 100644
--- a/DOCS/xml/en/cd-dvd.xml
+++ b/DOCS/xml/en/cd-dvd.xml
@@ -141,50 +141,6 @@ In case of DVD decoding problems, try disabling supermount, or any other such
facilities. Some RPC-2 drives may also require setting the region code.
-
-DVD structure
-
-DVD disks have 2048 bytes per sector with ECC/CRC. They usually have an UDF
-filesystem on a single track, containing various files (small .IFO and .BUP
-files and big (1GB) .VOB files). They are real files and can be copied/played
-from the mounted filesystem of an unencrypted DVD.
-
-
-
-
-The .IFO files contain the movie navigation information (chapter/title/angle
-map, language table, etc) and are needed to read and interpret the .VOB content
-(movie). The .BUP files are backups of them. They use
-sectors everywhere, so you need to use raw
-addressing of sectors of the disc to implement DVD navigation or decrypt the
-content.
-
-
-
-DVD support needs raw sector-based access to the device. Unfortunately you must
-(under Linux) be root to get the sector address of a file. That's why we don't
-use the kernel's filesystem driver at all, instead we reimplement it in
-userspace. libdvdread 0.9.x does this.
-The kernel UDF filesystem driver
-is not needed as they already have their own builtin UDF filesystem driver.
-Also the DVD does not have to be mounted as only the raw sector-based access is
-used.
-
-
-
-Sometimes /dev/dvd cannot be read by users, so the
-libdvdread authors implemented an emulation layer
-which transfers sector addresses to filenames+offsets, to emulate raw
-access on top of a mounted filesystem or even on a hard disk.
-
-
-
-libdvdread even accepts the mountpoint instead of
-the device name for raw access and checks /proc/mounts
-to get the device name. It was developed for Solaris, where device names
-are dynamically allocated.
-
-
DVD decryption