diff --git a/documentation/dev-manual/dev-manual-common-tasks.xml b/documentation/dev-manual/dev-manual-common-tasks.xml
index 23ea2df38e..5223aba158 100644
--- a/documentation/dev-manual/dev-manual-common-tasks.xml
+++ b/documentation/dev-manual/dev-manual-common-tasks.xml
@@ -5458,7 +5458,7 @@
 
             <para>
                 To create the read-only root filesystem, simply add the
-                <filename>read-only-rootfs</filename> feature to your image.
+                "read-only-rootfs" feature to your image.
                 Using either of the following statements in your
                 image recipe or from within the
                 <filename>local.conf</filename> file found in the
@@ -5494,13 +5494,13 @@
                 build on the host system.
                 These scripts cannot attempt to run during first-boot on the
                 target device.
-                With the <filename>read-only-rootfs</filename> feature enabled,
+                With the "read-only-rootfs" feature enabled,
                 the build system checks during root filesystem creation to make
                 sure all post-installation scripts succeed.
                 If any of these scripts still need to be run after the root
                 filesystem is created, the build immediately fails.
                 These build-time checks ensure that the build fails
-                rather than the target device failing later during its
+                rather than the target device fails later during its
                 initial boot operation.
             </para>
 
@@ -5552,7 +5552,7 @@
             <title>Areas With Write Access</title>
 
             <para>
-                With the <filename>read-only-rootfs</filename> feature enabled,
+                With the "read-only-rootfs" feature enabled,
                 any attempt by the target to write to the root filesystem at
                 runtime fails.
                 Consequently, you must make sure that you configure processes