Updates nav titles and fixes pull and issue links (#827)

Author: KOTungseth

docset.yml

@@ -396,9 +396,9 @@ subs:
   fleet-server-pull:   "https://github.com/elastic/fleet-server/pull/"
   kib-repo:   "https://github.com/elastic/kibana/"
   kib-issue:   "https://github.com/elastic/kibana/issues/"
-  kibana-issue:   "'{kib-repo}issues/'"
+  kibana-issue:   "'{{kib-repo}}issues/'"
   kib-pull:   "https://github.com/elastic/kibana/pull/"
-  kibana-pull:   "'{kib-repo}pull/'"
+  kibana-pull:   "'{{kib-repo}}pull/'"
   kib-commit:   "https://github.com/elastic/kibana/commit/"
   ml-repo:   "https://github.com/elastic/ml-cpp/"
   ml-issue:   "https://github.com/elastic/ml-cpp/issues/"
@@ -416,4 +416,5 @@ subs:
   stack-version: "9.0.0"
   eck_version: "3.0.0"
   apm_server_version: "9.0.0"
-  version: "9.0.0"
+  version: "9.0.0"
+  release-date: "2-April-2025"

release-notes/elastic-apm/breaking-changes.md

@@ -1,19 +1,19 @@
 ---
-navigation_title: "Elastic APM"
+navigation_title: "Breaking changes"
 ---
 
 # Elastic APM breaking changes [elastic-apm-breaking-changes]
-Breaking changes can impact your Elastic applications, potentially disrupting normal operations. Before you upgrade, carefully review the Elastic APM breaking changes and take the necessary steps to mitigate any issues. 
-
-To learn how to upgrade, check [Upgrade](/deploy-manage/upgrade.md).
+Breaking changes can impact your Elastic applications, potentially disrupting normal operations. Before you upgrade, carefully review the Elastic APM breaking changes and take the necessary steps to mitigate any issues. To learn how to upgrade, check [Upgrade](/deploy-manage/upgrade.md).
 
 % ## Next version [elastic-apm-nextversion-breaking-changes]
 % **Release date:** Month day, year
 
 % ::::{dropdown} Title of breaking change 
 % Description of the breaking change.
 % For more information, check [PR #](PR link).
+
 % **Impact**<br> Impact of the breaking change.
+
 % **Action**<br> Steps for mitigating deprecation impact.
 % ::::
 
@@ -29,7 +29,9 @@ To learn how to upgrade, check [Upgrade](/deploy-manage/upgrade.md).
 
 ::::{dropdown} Change server information endpoint "/" to only accept GET and HEAD requests
 This will surface any agent misconfiguration causing data to be sent to `/` instead of the correct endpoint (for example, `/v1/traces` for OTLP/HTTP).
-For more information, check [PR #15976](https://github.com/elastic/apm-server/pull/15976).
+For more information, check [#15976]({{apm-pull}}15976).
+
 **Impact**<br> Any methods other than `GET` and `HEAD` to `/` will return HTTP 405 Method Not Allowed.
+
 **Action**<br> Update any existing usage, for example, update `POST /` to `GET /`.
 ::::

release-notes/elastic-apm/deprecations.md

@@ -1,13 +1,11 @@
 ---
-navigation_title: "Elastic APM"
+navigation_title: "Deprecations"
 ---
 
 # Elastic APM deprecations [elastic-apm-deprecations]
 Over time, certain Elastic functionality becomes outdated and is replaced or removed. To help with the transition, Elastic deprecates functionality for a period before removal, giving you time to update your applications. 
 
-Review the deprecated functionality for Elastic APM. While deprecations have no immediate impact, we strongly encourage you update your implementation after you upgrade.
-
-To learn how to upgrade, check out [Upgrade](/deploy-manage/upgrade.md).
+Review the deprecated functionality for Elastic APM. While deprecations have no immediate impact, we strongly encourage you update your implementation after you upgrade. To learn how to upgrade, check out [Upgrade](/deploy-manage/upgrade.md).
 
 % ## Next version
 % **Release date:** Month day, year

release-notes/elastic-apm/known-issues.md

@@ -2,7 +2,7 @@
 mapped_pages:
   - https://www.elastic.co/guide/en/observability/current/apm-known-issues.html
 
-navigation_title: "Elastic APM"
+navigation_title: "Known issues"
 ---
 
 # Elastic APM known issues [elastic-apm-known-issues]
@@ -124,7 +124,7 @@ There are three ways to fix this error:
 
 1. Find broken rules
 
-    :::::{admonition}
+    :::::{note}
     To identify rules in this exact state, you can use the [find rules endpoint](https://www.elastic.co/docs/api/doc/kibana/v8/group/endpoint-alerting) and search for the APM anomaly rule type as well as this exact error message indicating that the rule is in the broken state. We will also use the `fields` parameter to specify only the fields required when making the update request later.
 
     * `search_fields=alertTypeId`
@@ -176,7 +176,7 @@ There are three ways to fix this error:
 
 2. Prepare the update JSON doc(s)
 
-    ::::{admonition}
+    ::::{note}
     For each broken rule found, create a JSON rule document with what was returned from the API in the previous step. You will need to make two changes to each document:
 
     1. Remove the `id` key but keep the value connected to this document (e.g. rename the file to `{{id}}.json`). **The `id` cannot be sent as part of the request body for the PUT request, but you will need it for the URL path.**
@@ -201,7 +201,7 @@ There are three ways to fix this error:
 
 3. Update each rule using the `PUT /api/alerting/rule/{{id}}` API
 
-    ::::{admonition}
+    ::::{note}
     For each rule, submit a PUT request to the [update rule endpoint](https://www.elastic.co/docs/api/doc/kibana/v8/group/endpoint-alerting) using that rule’s ID and its stored update document from the previous step. For example, assuming the first broken rule’s ID is `046c0d4f`:
 
     ```shell

release-notes/elastic-apm/release-notes.md

@@ -21,9 +21,9 @@ To check for security updates, go to [Security announcements for the Elastic sta
 % ### Fixes [elastic-apm-next-fixes]
 
 ## 9.0.0 [elastic-apm-900-release-notes]
-**Release date:** April 1, 2025
+**Release date:** April 2, 2025
 
-### Features and enhancements [elastic-apm-900-features-enhancements]
+% ### Features and enhancements [elastic-apm-900-features-enhancements]
 
 ### Fixes [elastic-apm-900-fixes]
-* Fix overflow in validation of `apm-server.agent.config.cache.expiration` on 32-bit architectures [#15216](https://github.com/elastic/apm-server/pull/15216)
+* Fixes overflow in validation of `apm-server.agent.config.cache.expiration` on 32-bit architectures [#15216]({{apm-pull}}15216)