1 files changed, 6 insertions, 6 deletions

diff --git a/documentation/dev-manual/dev-manual-common-tasks.xml b/documentation/dev-manual/dev-manual-common-tasks.xml
index 524c607855..64504299cc 100644
--- a/documentation/dev-manual/dev-manual-common-tasks.xml
+++ b/documentation/dev-manual/dev-manual-common-tasks.xml
@@ -1071,7 +1071,7 @@
                 <filename><ulink url='&YOCTO_DOCS_REF_URL;#var-IMAGE_INSTALL'>IMAGE_INSTALL</ulink></filename>
                 variable.
                 You must use the OpenEmbedded notation and not the Debian notation for the names
-                (e.g. <filename>eglibc-dev</filename> instead of <filename>libc6-dev</filename>).
+                (e.g. <filename>glibc-dev</filename> instead of <filename>libc6-dev</filename>).
             </para>
 
             <para>
@@ -3027,7 +3027,7 @@
             <note>
                 Although well within the capabilities of the Yocto Project,
                 adding a totally new architecture might require
-                changes to <filename>gcc/eglibc</filename> and to the site
+                changes to <filename>gcc/glibc</filename> and to the site
                 information, which is beyond the scope of this manual.
             </note>
         </para>
@@ -5911,10 +5911,10 @@ Gateways via their Web Interfaces</ulink>"</emphasis>
                 described here combined with experimentation and iteration.
                 Here are a couple of areas to experiment with:
                 <itemizedlist>
-                    <listitem><para><filename>eglibc</filename>:
+                    <listitem><para><filename>glibc</filename>:
                         In general, follow this process:
                         <orderedlist>
-                            <listitem><para>Remove <filename>eglibc</filename>
+                            <listitem><para>Remove <filename>glibc</filename>
                                 features from
                                 <ulink url='&YOCTO_DOCS_REF_URL;#var-DISTRO_FEATURES'><filename>DISTRO_FEATURES</filename></ulink>
                                 that you think you do not need.</para></listitem>
@@ -5928,7 +5928,7 @@ Gateways via their Web Interfaces</ulink>"</emphasis>
                                 support wide character support as is done for
                                 <filename>ncurses</filename>.
                                 Or, if support for those characters is needed,
-                                determine what <filename>eglibc</filename>
+                                determine what <filename>glibc</filename>
                                 features provide the support and restore the
                                 configuration.
                                 </para></listitem>
@@ -5937,7 +5937,7 @@ Gateways via their Web Interfaces</ulink>"</emphasis>
                         </orderedlist></para></listitem>
                     <listitem><para><filename>busybox</filename>:
                         For BusyBox, use a process similar as described for
-                        <filename>eglibc</filename>.
+                        <filename>glibc</filename>.
                         A difference is you will need to boot the resulting
                         system to see if you are able to do everything you
                         expect from the running system.