harmonize capitalization of headings - no content changes

docs/baseline-requirements.md

@@ -9,7 +9,7 @@ SPDX-License-Identifier: Apache-2.0
 * [Software bill of materials (SBOMs)](#software-bill-of-materials-sboms)
   * [Artifact SBOMs](#artifact-sboms)
   * [Source code SBOMs](#source-code-sboms)
-* [License Compliance](#license-compliance)
+* [License compliance](#license-compliance)
 * [Software supply chain security](#software-supply-chain-security)
 * [Container architectural basics](#container-architectural-basics)
 * [Security](#security)
@@ -25,7 +25,7 @@ SPDX-License-Identifier: Apache-2.0
   * [Top bar](#top-bar)
     * [Look and feel](#look-and-feel)
     * [Central navigation](#central-navigation)
-  * [Functional Administration](#functional-administration)
+  * [Functional administration](#functional-administration)
   * [Theming](#theming)
   * [Central user profile](#central-user-profile)
 * [Footnotes](#footnotes)
@@ -60,14 +60,14 @@ Today's software development platforms like GitLab or GitHub provide dependency
 
 **Reference:** Currently we do not have source code SBOMs in place.
 
-# License Compliance
+# License compliance
 
 All parts of openDesk Community Edition must be open source with source code (also) published or at least publishable on openCode.
 
 openCode provides some boundaries when it comes to open source license compliance openDesk has to adhere to:
 
-- The components must be published under a license listed in the [openCode license allow list](https://wikijs.opencode.de/de/Hilfestellungen_und_Richtlinien/Lizenzcompliance#h-2-open-source-lizenzliste).
-- Delivered artifacts (container images) must contain only components licensed under the aforementioned allow list. A container must not contain any artifact using a license from the [openCode license block list](https://wikijs.opencode.de/de/Hilfestellungen_und_Richtlinien/Lizenzcompliance#h-3-negativliste-aller-nicht-freigegebenen-lizenzen).
+- The components must be published under a license listed in the [openCode license allow list](https://opencode.de/de/wissen/rechtssichere-nutzung/open-source-lizenzen).
+- Delivered artifacts (container images) must contain only components licensed under the aforementioned allow list. A container must not contain any artifact using a license from the [openCode license block list](https://opencode.de/de/wissen/rechtssichere-nutzung/open-source-lizenzen#3.-Negativliste-aller-nicht-freigegebenen-Lizenzen).
 
 Deviations from the above requirements must be documented in the openDesk license deviation report.
 
@@ -243,7 +243,7 @@ When implementing the central navigation into an application there are two optio
 
 **Reference:** This is available in current deployments in all applications except for Jitsi, Collabora, and CryptPad.
 
-## Functional Administration
+## Functional administration
 
 While applications usually support technical and functional administration the technical part should be in the responsibility of the operator and is usually done at (re)deployment time. Therefore the administrative tasks within an application should be limited to functional administration.