diff options
| author | David Bryant <davidbryant@gvtc.com> | 2022-10-21 12:59:34 -0500 |
|---|---|---|
| committer | David Bryant <davidbryant@gvtc.com> | 2022-10-21 12:59:34 -0500 |
| commit | eaf26ea5964d25701513a2caf5ee96bc48a909f2 (patch) | |
| tree | e4c6b626ae765cdaa87040f32de283f981a22373 | |
| parent | 347bbda9c10cb821d0369e173f8a3e33ea4cd1e2 (diff) | |
Edited for style, idiom, and punctuation. Emphasized the need to continue
applying security patches even after LFS is "complete".
| -rw-r--r-- | prologue/errata.xml | 18 |
1 files changed, 9 insertions, 9 deletions
diff --git a/prologue/errata.xml b/prologue/errata.xml index fa919bcca..275eac7da 100644 --- a/prologue/errata.xml +++ b/prologue/errata.xml @@ -13,18 +13,18 @@ <para>The software used to create an LFS system is constantly being updated and enhanced. Security warnings and bug fixes may become available after the LFS book has been released. To check whether the package versions or - instructions in this release of LFS need any modifications to accommodate - security vulnerabilities or other bug fixes, please visit + instructions in this release of LFS need any modifications—to repair + security vulnerabilities or to fix other bugs—please visit <ulink url="&errata;"/> before proceeding with your build. You should note any - changes shown and apply them to the relevant section of the book as you - progress with building the LFS system.</para> + changes shown and apply them to the relevant sections of the book as you + build the LFS system.</para> <para>In addition, the Linux From Scratch editors maintain a list of security - vulnerabilities discovered after a book was released. To check whether there - are any active security vulnerabilities, please visit - <ulink url="&secadv;"/> prior to proceeding with your build. You should note - any advisories and perform the steps to fix any security vulnerabilities as - you progress with building the LFS system.</para> + vulnerabilities discovered <emphasis>after</emphasis> a book has been released. To see + whether there are any known security vulnerabilities, please visit + <ulink url="&secadv;"/> before proceeding with your build. You should also continue + to consult the advisories, and fix any security vulnerabilities, even + when the LFS system has been completely constructed.</para> </sect1> |