diff --git a/repos/dde_linux/README b/repos/dde_linux/README
index 4c6bec68cf..83379c7582 100644
--- a/repos/dde_linux/README
+++ b/repos/dde_linux/README
@@ -108,6 +108,69 @@ devices hardware address. If this is the case and no 'mac' attribute is given a
fallback address will be assigned to the network device. Note that the fallback
address will always be the same.
+
+RAW
+~~~
+
+Allows raw access to USB devices via the 'Usb' session interface.
+
+Configuration snippet:
+
+!
+!
+!
+!
+!
+!
+!
+!
+!
+
+The optional 'devices' report lists the connected devices and gets updated
+when devices are added or removed.
+
+Example report:
+
+!
+!
+!
+!
+!
+!
+!
+!
+!
+!
+
+For every device a unique identifier is generated that is used to access the
+USB device. Only devices that have a valid policy configured at the USB driver
+can be accessed by a client. The following configuration allows 'comp1' to
+access the device 'usb-1-6':
+
+!
+!
+!
+!
+!
+!
+!
+!
+!
+!
+
+In addition to the mandatory 'label' attribute the policy node also
+contains optional attribute tuples of which at least one has to be present.
+The 'vendor_id' and 'product_id' tuple selects a device regardless of its
+location on the USB bus and is mostly used in static configurations. The
+'bus' and 'dev' tuple selects a specific device via its bus locations and
+device address. It is mostly used in dynamic configurations because the device
+address is not fixed and may change every time the same device is plugged in.
+
+The configuration of the USB driver can be changed at runtime to satisfy
+dynamic configurations or rather policies when using the 'Usb' session
+interface.
+
+
LXIP
####
@@ -205,67 +268,6 @@ based component in 'src/app/qt_wifi_connect'.
Currently only WPA/WPA2 protection using a pre-shared key is supported.
-RAW
-~~~
-
-Allows raw access to USB devices via the 'Usb' session interface.
-
-Configuration snippet:
-
-!
-!
-!
-!
-!
-!
-!
-!
-!
-
-The optional 'devices' report lists the connected devices and gets updated
-when devices are added or removed.
-
-Example report:
-
-!
-!
-!
-!
-!
-!
-!
-!
-!
-!
-
-For every device a unique identifier is generated that is used to access the
-USB device. Only devices that have a valid policy configured at the USB driver
-can be accessed by a client. The following configuration allows 'comp1' to
-access the device 'usb-1-6':
-
-!
-!
-!
-!
-!
-!
-!
-!
-!
-!
-
-In addition to the mandatory 'label' attribute the policy node also
-contains optional attribute tuples of which at least one has to be present.
-The 'vendor_id' and 'product_id' tuple selects a device regardless of its
-location on the USB bus and is mostly used in static configurations. The
-'bus' and 'dev' tuple selects a specific device via its bus locations and
-device address. It is mostly used in dynamic configurations because the device
-address is not fixed and may change every time the same device is plugged in.
-
-The configuration of the USB driver can be changed at runtime to satisfy
-dynamic configurations or rather policies when using the 'Usb' session
-interface.
-
lx_kit
######