diff --git a/documentation/dev-manual/dev-manual-common-tasks.xml b/documentation/dev-manual/dev-manual-common-tasks.xml
index b28b7e21ec..e6fd4fb363 100644
--- a/documentation/dev-manual/dev-manual-common-tasks.xml
+++ b/documentation/dev-manual/dev-manual-common-tasks.xml
@@ -630,25 +630,62 @@
the Build Directory.
-
- The Yocto Project ships with two SSH servers you can use in your
- images: Dropbear and OpenSSH.
- Dropbear is a minimal SSH server appropriate for
- resource-constrained environments, while OpenSSH is a well-known
- standard SSH server implementation.
- By default, the core-image-sato image is
- configured to use Dropbear.
- The core-image-basic and
- core-image-lsb images both
- include OpenSSH.
- The core-image-minimal image does not
- contain an SSH server.
- To change these defaults, edit the
- IMAGE_FEATURES variable
- so that it sets the image you are working with to include
- ssh-server-dropbear or
- ssh-server-openssh.
-
+
+ Choosing the SSH Server
+
+
+ The Yocto Project ships with two SSH servers you can use
+ with your images: Dropbear and OpenSSH.
+ Dropbear is a minimal SSH server appropriate for
+ resource-constrained environments, while OpenSSH is a
+ well-known standard SSH server implementation.
+ By default, the core-image-sato image
+ is configured to use Dropbear.
+ The core-image-basic and
+ core-image-lsb images both
+ include OpenSSH.
+ The core-image-minimal image does not
+ contain an SSH server.
+
+
+
+ You can customize your image and change these defaults.
+ Edit IMAGE_FEATURES variable
+ so that it configures the image you are working with to
+ include ssh-server-dropbear or
+ ssh-server-openssh.
+
+
+
+
+ Creating a Read-Only Root Filesystem
+
+
+ Another example of customizing your image could be setting
+ up a read-only filesystem.
+ Suppose, for security reasons, you need to disable the
+ your target device's root filesystem's write permisions
+ (i.e. you need a read-only root filesystem).
+ Or, perhaps you are running the device's operating system
+ from a read-only storage device.
+ For either case, you can customize your image for
+ that behavior.
+
+
+
+ To create a read-only root filesystem, simply add the
+ "read-only-rootfs" feature to your image.
+ Using either of the following statements in your
+ image recipe or from within the
+ local.conf file found in the Build
+ Directory causes the build system to create a
+ read-only root filesystem:
+
+ IMAGE_FEATURES = "read-only-rootfs"
+ EXTRA_IMAGE_FEATURES = "read-only-rootfs"
+
+
+