Change documentation font to Open Sans.

docs/_includes/sigfonts.css

@@ -1,29 +1,29 @@
 @font-face {
-    font-family: "Noir Pro";
+    font-family: "Open Sans";
     font-style: normal;
     font-weight: 300;
-    src: url("/fonts/NoirPro-Light.ttf") format("truetype");
+    src: url("/fonts/OpenSans-Light.ttf") format("truetype");
 }
 
 @font-face {
-    font-family: "Noir Pro";
+    font-family: "Open Sans";
     font-style: normal;
     font-weight: 400;
-    src: url("/fonts/NoirPro-Regular.ttf") format("truetype");
+    src: url("/fonts/OpenSans-Regular.ttf") format("truetype");
 }
 
 @font-face {
-    font-family: "Noir Pro";
+    font-family: "Open Sans";
     font-style: normal;
     font-weight: 500;
-    src: url("/fonts/NoirPro-Medium.ttf") format("truetype");
+    src: url("/fonts/OpenSans-Medium.ttf") format("truetype");
 }
 
 @font-face {
-    font-family: "Noir Pro";
+    font-family: "Open Sans";
     font-style: normal;
     font-weight: 700;
-    src: url("/fonts/NoirPro-Bold.ttf") format("truetype");
+    src: url("/fonts/OpenSans-Bold.ttf") format("truetype");
 }
 
 @font-face {

docs/_includes/stylesheet.css

@@ -29,9 +29,9 @@ html, body {
 }
 
 body, td, th, input[type=text] {
-    font-family: "Noir Pro";
+    font-family: "Open Sans", sans-serif;
     font-size: 16px;
-    font-weight: 300;
+    font-weight: 400;
     line-height: 1.6;
     color: var(--sig-paragraph-gray);
 }
@@ -47,7 +47,7 @@ a:hover {
 }
 
 h1 {
-    font-family: "Azeret Mono";
+    font-family: "Azeret Mono", sans-serif;
     color: var(--sig-text-black);
     font-size: 32px;
     font-weight: 400;

docs/reference/release-notes.md

@@ -3,12 +3,13 @@ Sigrid release notes
 
 SIG uses [continuous delivery](https://en.wikipedia.org/wiki/Continuous_delivery), meaning that every change to Sigrid or the underlying analysis is released once our development pipeline has completed. On average, we release somewhere between 10 and 20 times per day. This page therefore doesn't list every single change, since that would quickly lead to an excessively long list of small changes. Instead, this page lists Sigrid and analysis changes that we consider noteworthy for the typical Sigrid user.
 
-### October 22, 2025
+### October 20, 2025
 
 - **Sigrid API:** You can now retrieve the maintainability of new/changed code using the API. This is the same information that you can find in Sigrid's [delta quality page](../capabilities/system-delta-quality.md). Having API access for this information makes it easier to integrate this data into your own dashboards and reporting. You can find more information in the [API documentation]().
 - **Code Explorer:** You can now filter the list of findings by status. For example, you can filter the list to only show findings that were marked as "risk accepted", which allows you to review the rationale for accepting those risks. You can also filter all findings marked as "false positive", to double-check those findings are *actually* false positives. This filter option is available for all types of findings, and accessible from the filter icon in the [Code Explorer page](../capabilities/system-code-explorer.md).
+- **Code Explorer:** It is now possible to add remarks to maintainability findings. You can use these remarks to indicate why something needs to be fixed, or why something *shouldn't* be fixed because the alternatives would be worse.
 
-### October 5, 2025
+### October 6, 2025
 
 - **Code Explorer:** Exporting the duplication findings to CSV now includes an additional column with the duplication percentage. This is useful for power users that want to e.g. filter on 100% duplicates.
 - **Code Explorer:** The performance of loading findings in the Code Explorer has improved significantly. You will mainly notice this if you have a very large system, and are trying to view the total list of findings across the entire system.