02/02: doc: Refer to up-to-date version of ‘gcc-toolchain’ in example.

[guix-commits]

pelzflorian pushed a commit to branch master
in repository guix.

commit 3f938d841eacb3370fcaeae41084d7594536c2d5
Author: Florian Pelz <pelzflorian@pelzflorian.de>
AuthorDate: Sun Nov 24 11:39:03 2024 +0100

    doc: Refer to up-to-date version of ‘gcc-toolchain’ in example.
    
    * doc/guix.texi (Writing Manifests): Write that for
    ‘gcc-toolchain’ we have GCC version 14 today.
    
    Change-Id: I9bfbe4a6d36b0dae16cafec86ce58ef50e64e50d
---
 doc/guix.texi | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/doc/guix.texi b/doc/guix.texi
index 3ca8629aef..26488b41c8 100644
--- a/doc/guix.texi
+++ b/doc/guix.texi
@@ -8797,8 +8797,8 @@ Options}).
 @quotation Note
 Manifests are @emph{symbolic}: they refer to packages of the channels
 @emph{currently in use} (@pxref{Channels}).  In the example above,
-@code{gcc-toolchain} might refer to version 11 today, but it might refer
-to version 13 two years from now.
+@code{gcc-toolchain} might refer to version 14 today, but it might refer
+to version 16 two years from now.
 
 If you want to ``pin'' your software environment to specific package
 versions and variants, you need an additional piece of information: the