From 7ea7a3b3d32750e8beb52d6fa7cc36d6cd7457f6 Mon Sep 17 00:00:00 2001
From: Bruce Dubbs <bdubbs@linuxfromscratch.org>
Date: Tue, 8 Apr 2025 12:50:25 -0500
Subject: [PATCH] Change expat url and fix a grammar issue.

---
 packages.ent                      | 2 +-
 part3intro/toolchaintechnotes.xml | 2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/packages.ent b/packages.ent
index cd692a8c8..5dbbfed1a 100644
--- a/packages.ent
+++ b/packages.ent
@@ -158,7 +158,7 @@
 
 <!ENTITY expat-version "2.7.1">
 <!ENTITY expat-size "485 KB">
-<!ENTITY expat-url "&sourceforge;expat/expat-&expat-version;.tar.xz">
+<!ENTITY expat-url "&github;/libexpat/libexpat/releases/download/R_2_7_1/expat-&expat-version;.tar.xz">
 <!ENTITY expat-md5 "9f0c266ff4b9720beae0c6bd53ae4469">
 <!ENTITY expat-home "https://libexpat.github.io/">
 <!ENTITY expat-fin-du "14 MB">
diff --git a/part3intro/toolchaintechnotes.xml b/part3intro/toolchaintechnotes.xml
index 0d3c66b55..2239b2c7a 100644
--- a/part3intro/toolchaintechnotes.xml
+++ b/part3intro/toolchaintechnotes.xml
@@ -242,7 +242,7 @@
         <para>
           The build system should not attempt to run any generated machine
           code supposed to be executed on <quote>the host.</quote>  For
-          example, when building an utility natively, its man page can be
+          example, when building a utility natively, its man page can be
           generated by running the utility with the
           <parameter>--help</parameter> switch and processing the output,
           but generally it's not possible to do so for a cross-compilation