ci: build with gcc-11 as well

Focal builds for gcc-11 are finally available, so let's put them into
some use.

.github/workflows/build_test.yml

@@ -19,6 +19,7 @@ jobs:
       matrix:
         env:
           - { COMPILER: "gcc",   COMPILER_VERSION: "10" }
+          - { COMPILER: "gcc",   COMPILER_VERSION: "11" }
           - { COMPILER: "clang", COMPILER_VERSION: "10" }
           - { COMPILER: "clang", COMPILER_VERSION: "11" }
           - { COMPILER: "clang", COMPILER_VERSION: "12" }

docs/JOURNAL_FILE_FORMAT.md

@@ -24,7 +24,7 @@ The systemd journal stores log data in a binary format with several features:
 This document explains the basic structure of the file format on disk. We are
 making this available primarily to allow review and provide documentation. Note
 that the actual implementation in the [systemd
-codebase](https://github.com/systemd/systemd/blob/master/src/journal/) is the
+codebase](https://github.com/systemd/systemd/blob/main/src/libsystemd/sd-journal/) is the
 only ultimately authoritative description of the format, so if this document
 and the code disagree, the code is right. That said we'll of course try hard to
 keep this document up-to-date and accurate.
@@ -106,7 +106,7 @@ ignored on reading. They are currently not used but might be used later on.
 ## Structure
 
 The file format's data structures are declared in
-[journal-def.h](https://github.com/systemd/systemd/blob/master/src/journal/journal-def.h).
+[journal-def.h](https://github.com/systemd/systemd/blob/main/src/libsystemd/sd-journal/journal-def.h).
 
 The file format begins with a header structure. After the header structure
 object structures follow. Objects are appended to the end as time

man/systemd.network.xml

@@ -423,7 +423,7 @@
           <listitem>
             <para>Specifies how IPv6 link local address is generated. Takes one of <literal>eui64</literal>,
             <literal>none</literal>, <literal>stable-privacy</literal> and <literal>random</literal>.
-            When unset, the kernel's default will be used. Note that if <varname>LinkLocalAdressing=</varname>
+            When unset, the kernel's default will be used. Note that if <varname>LinkLocalAddressing=</varname>
             not configured as <literal>ipv6</literal> then <varname>IPv6LinkLocalAddressGenerationMode=</varname>
             is ignored.</para>
           </listitem>