doc: Update description of partitions

Starting from UHD4.7/Yocto release kirkstone, only the first
partition is populated in the .sdimg filesystem image and the
second rootfs partition is empty.

host/docs/usrp_e3xx.dox

@@ -203,16 +203,19 @@ system (Linux kernel, libraries) and any user data are stored on this SD card.
 The SD card is partitioned into four partitions:
 
 - Boot partition (contains the bootloader). This partition usually does not
-   require any modifications.
+  require any modifications.
+- Two system partitions (root file systems). These contain the operating system
+  and the home directory (anything mounted under / that is not the data or boot
+  partition). Up until UHD 4.6/Yocto release zeus, the two rootfs partitions are
+  identical in the .sdimg filesystem image. Starting from UHD4.7/Yocto release
+  kirkstone, only the first partition is populated in the .sdimg filesystem
+  image and the second rootfs partition is empty.
+  The reason there are two of these is to enable remote updates: An update
+  running on one partition can update the other one without any effect to the
+  currently running system. Note that the system partitions are erased during
+  updates and are thus unsuitable for permanently storing information.
 - A data partition, mounted in /data. This is the only partition that is not
-   erased during file system updates.
-- Two identical system partitions (root file systems). These contain the
-   operating system and the home directory (anything mounted under / that is not
-   the data or boot partition). The reason there are two of these is to enable
-   remote updates: An update running on one partition can update the other one
-   without any effect to the currently running system. Note that the system
-   partitions are erased during updates and are thus unsuitable for permanently
-   storing information.
+  erased during file system updates.
 
 Note: It is possible to access the currently inactive root file system by
 mounting it. After logging into the device using serial console or SSH (see the

host/docs/usrp_n3xx.dox

@@ -123,17 +123,20 @@ system (Linux kernel, libraries) and any user data are stored on this SD card.
 
 The SD card is partitioned into four partitions:
 
-1. Boot partition (contains the bootloader). This partition usually does not
-   require touching.
-2. A data partition, mounted in /data. This is the only partition that is not
-   erased during file system updates.
-2. Two identical system partitions (root file systems). These contain the
-   operating system and the home directory (anything mounted under / that is not
-   the data or boot partition). The reason there are two of these is to enable
-   remote updates: An update running on one partition can update the other one
-   without any effect to the currently running system. Note that the system
-   partitions are erased during updates and are thus unsuitable for permanently
-   storing information.
+- Boot partition (contains the bootloader). This partition usually does not
+  require any modifications.
+- Two system partitions (root file systems). These contain the operating system
+  and the home directory (anything mounted under / that is not the data or boot
+  partition). Up until UHD 4.6/Yocto release zeus, the two rootfs partitions are
+  identical in the .sdimg filesystem image. Starting from UHD4.7/Yocto release
+  kirkstone, only the first partition is populated in the .sdimg filesystem
+  image and the second rootfs partition is empty.
+  The reason there are two of these is to enable remote updates: An update
+  running on one partition can update the other one without any effect to the
+  currently running system. Note that the system partitions are erased during
+  updates and are thus unsuitable for permanently storing information.
+- A data partition, mounted in /data. This is the only partition that is not
+  erased during file system updates.
 
 Note: It is possible to access the currently inactive root file system by
 mounting it. After logging into the device using serial console or SSH (see the

host/docs/usrp_x4xx.dox

@@ -187,17 +187,20 @@ on the back panel.
 The entire root file system (Linux kernel, libraries) and any user data are
 stored on the eMMC. It is partitioned into four partitions:
 
-1. Boot partition (contains the bootloader). This partition usually does not
-   require modification.
-2. A data partition, mounted in /data. This is the only partition that is not
-   erased during file system updates.
-3. Two identical system partitions (root file systems). These contain the
-   operating system and the home directory (anything mounted under / that is not
-   the data or boot partition). The reason there are two of these is to enable
-   remote updates: An update running on one partition can update the other one
-   without any effect to the currently running system. Note that the system
-   partitions are erased during updates and are thus unsuitable for permanently
-   storing information.
+- Boot partition (contains the bootloader). This partition usually does not
+  require any modifications.
+- Two system partitions (root file systems). These contain the operating system
+  and the home directory (anything mounted under / that is not the data or boot
+  partition). Up until UHD 4.6/Yocto release zeus, the two rootfs partitions are
+  identical in the .sdimg filesystem image. Starting from UHD4.7/Yocto release
+  kirkstone, only the first partition is populated in the .sdimg filesystem
+  image and the second rootfs partition is empty.
+  The reason there are two of these is to enable remote updates: An update
+  running on one partition can update the other one without any effect to the
+  currently running system. Note that the system partitions are erased during
+  updates and are thus unsuitable for permanently storing information.
+- A data partition, mounted in /data. This is the only partition that is not
+  erased during file system updates.
 
 Note: It is possible to access the currently inactive root file system by
 mounting it. After logging into the device using serial console or SSH (see the