diff --git a/doc/administration/audit_event_schema.md b/doc/administration/audit_event_schema.md
index 2642d47a2e2..9f3b3e0fd99 100644
--- a/doc/administration/audit_event_schema.md
+++ b/doc/administration/audit_event_schema.md
@@ -102,7 +102,7 @@ Fetch:
 
 ```json
 {
-  "id": 1,
+  "id": "1",
   "author_id": -3,
   "entity_id": 29,
   "entity_type": "Project",
diff --git a/doc/tutorials/scrum_events/index.md b/doc/tutorials/scrum_events/index.md
index def3d486cd4..d4303b7ff96 100644
--- a/doc/tutorials/scrum_events/index.md
+++ b/doc/tutorials/scrum_events/index.md
@@ -257,6 +257,7 @@ Here's an example of breaking a feature into vertically sliced job stories based
 journey:
 
 ```mermaid
+flowchart TD
 Epic["Epic: When using the application, I need to create an <br> account, so that I can use the application features"] --> Issue1["Issue: When creating my account, I need to specify my email address,<br> so that I can receive future updates from the application"]
     Epic --> Issue2["Issue: When creating my account, I need to <br>specify a password, so that my account remains secure"]
     Epic --> Issue3["Issue: When creating my account and entering the required info, I need to <br>finalize creating my account, so that I can login"]
diff --git a/doc/user/application_security/dependency_list/index.md b/doc/user/application_security/dependency_list/index.md
index 409f6106df5..0e4ba0a6f01 100644
--- a/doc/user/application_security/dependency_list/index.md
+++ b/doc/user/application_security/dependency_list/index.md
@@ -136,3 +136,31 @@ To download the dependency list:
 1. On the left sidebar, select **Search or go to** and find your project or group.
 1. Select **Secure > Dependency list**.
 1. Select **Export**.
+
+## Troubleshooting
+
+### License appears as 'unknown'
+
+The license for a specific dependency might show up as `unknown` for a few possible reasons. This section describes how to determine whether a specific dependency's license shows up as `unknown` for a known reason.
+
+#### License is 'unknown' upstream
+
+Check the license specified for the dependency upstream:
+
+- For C/C++ packages, check [Conancenter](https://conan.io/center).
+- For npm packages, check [npmjs.com](https://www.npmjs.com/).
+- For Python packages, check [PyPI](https://pypi.org/).
+
+If the license appears as `unknown` upstream, it is expected that GitLab will show the **License** for that dependency to be `unknown` as well.
+
+#### License includes SPDX license expression
+
+[SPDX license expressions](https://spdx.github.io/spdx-spec/v2.3/SPDX-license-expressions/) are not supported. Dependencies with SPDX license expressions appear with a **License** that is `unknown`. An example of an SPDX license expression is `(MIT OR CC0-1.0)`. Read more in [issue 336878](https://gitlab.com/gitlab-org/gitlab/-/issues/336878).
+
+#### Package version not in Package Metadata DB
+
+The specific version of the dependency package must exist in the [Package Metadata Database](../../../topics/offline/quick_start_guide.md#enabling-the-package-metadata-database). If it doesn't, the **License** for that dependency appears as `unknown`. Read more in [issue 440218](https://gitlab.com/gitlab-org/gitlab/-/issues/440218) about Go modules.
+
+#### Package name contains special characters
+
+If the name of the dependency package contains a hyphen (`-`) the **License** may appear as `unknown`. This can happen when packages are added manually to `requirements.txt` or when `pip-compile` is used. This happens because GitLab does not normalize Python package names in accordance with the guidance on [normalized names in PEP 503](https://peps.python.org/pep-0503/#normalized-names) when ingesting information about dependencies. Read more in [issue 440391](https://gitlab.com/gitlab-org/gitlab/-/issues/440391).