[lfs] branch trunk updated: Tweak the wording in the first note in GCC-15.2.0 - Pass 1

"Git Owner" ([email protected] via lfs-book Mailing List) <[email protected]>
Newsgroups gmane.linux.lfs.book
Message-ID <177601434688.11820.9731402880905483892@rivendell.linuxfromscratch.org>
This is an automated email from the git hooks/post-receive script.

git pushed a commit to branch trunk
in repository lfs.

The following commit(s) were added to refs/heads/trunk by this push:
     new b9e0c4225 Tweak the wording in the first note in GCC-15.2.0 - Pass 1
     new 51aa3b85a Merge branch 'trunk' of git.linuxfromscratch.org:lfs into trunk
b9e0c4225 is described below

commit b9e0c422595b780322df7e119ab11a69501e17e7
Author: Bruce Dubbs <[email protected]>
AuthorDate: Sun Apr 12 12:18:46 2026 -0500

    Tweak the wording in the first note in GCC-15.2.0 - Pass 1
---
 chapter05/gcc-pass1.xml | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/chapter05/gcc-pass1.xml b/chapter05/gcc-pass1.xml
index 8da5617ed..24fd9f576 100644
--- a/chapter05/gcc-pass1.xml
+++ b/chapter05/gcc-pass1.xml
@@ -49,8 +49,8 @@
     resulting directories so the GCC build procedures will automatically
     use them:</para>
 
-    <note><para>There are frequent misunderstandings about this chapter.  The
-    procedures are the same as every other chapter, as explained earlier (<xref
+    <note><para>There are frequent misunderstandings about the instructions here.  The
+    procedures are the same as every other package, as explained earlier (<xref
     linkend='buildinstr'/>).  First, extract the gcc-&gcc-version; tarball from the sources
     directory, and then change to the directory created.  Only then should you
     proceed with the instructions below.</para></note>

-- 
To stop receiving notification emails like this one, please contact
the administrator of this repository.

-- 
http://lists.linuxfromscratch.org/sympa/info/lfs-book
Unsubscribe: See the above information page
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.