Apply 8 suggestion(s) to 4 file(s)

Co-authored-by: Dylan Aïssi <dylan.aissi@collabora.com>

content/_index.md

@@ -88,8 +88,8 @@ year.
 #### Further Links
 
 * [Release Schedule]( {{< ref "releases.md" >}} )
-* Current stable release: [v2024.4]( {{< ref "/release/v2024/v2024.4/releasenotes.md" >}} )
-* Current old stable release: [v2025.0]( {{< ref "/release/v2023/v2023.7/releasenotes.md" >}} )
+* Current stable release: [v2025.0]( {{< ref "/release/v2025/v2025.0/releasenotes.md" >}} )
+* Current old stable release: [v2024.4]( {{< ref "/release/v2024/v2024.4/releasenotes.md" >}} )
 * Current development release: [v2026dev0]( {{< ref "/release/v2026/v2026dev0/releasenotes.md" >}} )
 {{% /link-box %}}
 {{% /homepage-column %}}

content/release/v2025/v2025.0/releasenotes.md

@@ -14,14 +14,14 @@ of product-specific images for ARM (both the 32bit ARMv7 and 64-bit
 ARMv8 versions using the hardfloat ABI) and Intel x86-64 (64-bit)
 systems.
 
-**Apertis v2025.0** is the preview release of the Apertis
-v2025 stable release flow that will lead to the LTS **Apertis v2025.0**
-release in March 2025.
+**Apertis v2025.0** is the first **stable** release of the Apertis
+v2025 stable [release flow]( {{< ref "release-flow.md#apertis-release-flow" >}} ).
+Apertis is committed to maintaining the v2025 release stream up to the end
+of 2026.
 
 This Apertis release is built on top of Debian Bookworm along with several customizations
-and it ships the latest Linux kernel 6.11.x series. Later releases in the v2025 channel
-will be tracking newer kernel versions up to the next LTS as well as Debian Bookworm
-Stable Channel.
+and it ships the latest Linux LTS kernel 6.12.x series. Later releases in the v2025 channel
+will be tracking kernel updates in this LTS series as well as Debian Bookworm Stable Channel.
 
 Test results for the v2025.0 release are available in the following
 test reports:
@@ -77,7 +77,7 @@ The full list of packages available from the v2025 APT repositories is available
 
 Apertis now provides images for the NXP LS1028ARDB allowing developers building products
 using this platform to have a good starting point. The fixed function images is available
-in the standard [Apertis download site](https://images.apertis.org/release/v2025/v2025.0rc1/arm64/fixedfunction/apertis_v2025-fixedfunction-arm64-layerscape_v2025.0.img.gz)
+in the standard [Apertis download site](https://images.apertis.org/release/v2025/v2025.0/arm64/fixedfunction/apertis_v2025-fixedfunction-arm64-layerscape_v2025.0.img.gz)
 
 ## Build and integration
 
@@ -125,8 +125,8 @@ cause regression and simplifying the review and test process.
 
 Apertis now provides [Change History Generator](https://gitlab.apertis.org/infrastructure/change-history-generator/)
 a tool to generate a changelog between images. Thanks to this tool, as part of
-[daily builds](https://images.apertis.org/daily/v2024/) a
-[changelog](https://images.apertis.org/release/v2024/v2024.0/amd64/fixedfunction/ospack_v2024-amd64-fixedfunction_v2024.0.changelogs.tar.gz)
+[daily builds](https://images.apertis.org/daily/v2025/) a
+[changelog](https://images.apertis.org/release/v2025/v2025.0/amd64/fixedfunction/ospack_v2025-amd64-fixedfunction_v2025.0.changelogs.tar.gz)
 is created which helps developers to track changes across different images.
 
 ### Folding and branching pipeline improvements

content/release/v2025/v2025.1.md

 +++
 weight = 100
-title = "v2025.0"
+title = "v2025.1"
 
 aliases = [
-    "/release/v2025.0",
+    "/release/v2025.1",
 ]
 +++
 +++
 
-# Release v2025.0
+# Release v2025.1
 
 {{< section-toc >}}

content/release/v2025/v2025.1/release_schedule.md

@@ -18,7 +18,7 @@ The v2025.1 release cycle is scheduled to start in January 2025.
 | Soft code freeze/hard feature freeze: end of feature development for this release, only bugfixes allowed | 2025-05-14        |
 | Release candidate 1 (RC1)/hard code freeze: no new code changes may be made after this date              | 2025-05-21        |
 | RC testing                                                                                               | 2025-05-22..06-04 |
-| v2025.1 release                                                                                        | 2025-06-05        |
+| v2025.1 release                                                                                          | 2025-06-05        |
 
 If the release candidate 1 does not successfully pass all required
 tests, then the issues will be fixed and a new release candidate will be