Merge pull request #3863 from uselagoon/docs/fix-223-release-note

docs: fix links in release notes for v2.23.0

docs/releases/2.23.0.md

@@ -14,17 +14,17 @@ This release is a standard Lagoon release. There are changes that teams managing
 Self-managed Lagoon installs may need to be aware of these changes in lagoon-core:
 
 ### Broker update to RabbitMQ 3.13
-This release of Lagoon includes an update to RabbitMQ 3.13 in https://github.com/uselagoon/lagoon/pull/3849 - which has necessitated a small modification to the feature flag enabler (to ignore experimental plugins like Khepri, that are known to have issues). As long as the upgrade runs in order successfully, the plugin should remain disabled.
+This release of Lagoon includes an update to RabbitMQ 3.13 in [#3849](https://github.com/uselagoon/lagoon/pull/3849) - which has necessitated a small modification to the feature flag enabler (to ignore experimental plugins like Khepri, that are known to have issues). As long as the upgrade runs in order successfully, the plugin should remain disabled.
 
 ### KEYCLOAK_ADMIN_API_CLIENT_SECRET
-In https://github.com/uselagoon/lagoon/pull/3841 a new client was added to the Master realm in Keycloak to allow the API to configure Keycloak. This will remove the need for an admin user/password to be used, so MFA can be set on the admin account (AFTER the upgrade!!). The charts will autocreate and configure the secret if none is provided.
+In [#3841](https://github.com/uselagoon/lagoon/pull/3841) a new client was added to the Master realm in Keycloak to allow the API to configure Keycloak. This will remove the need for an admin user/password to be used, so MFA can be set on the admin account (AFTER the upgrade!!). The charts will autocreate and configure the secret if none is provided.
 
 ### Platform-X roles can be set within Lagoon instead of Keycloak
-In https://github.com/uselagoon/lagoon/pull/3840, this release introduced the ability to set platform-X roles via the lagoon CLI/API instead of directly within Keycloak.
+In [#3840](https://github.com/uselagoon/lagoon/pull/3840), this release introduced the ability to set platform-X roles via the lagoon CLI/API instead of directly within Keycloak.
 
 ## Deprecations
 
 Self-managed Lagoon installs may need to be aware of these changes in lagoon-remote:
 
 ### Node sysctl daemonset replaces init containers for OpenSearch and Elasticsearch
-In https://github.com/uselagoon/build-deploy-tool/pull/395 a future release of the build deploy tool will remove the init containers from OpenSearch & Elasticsearch deployments that are used to set the necessary sysctl settings. This daemonset, when enabled in lagoon-remote, runs once on node startup to ensure the correct setting is in place for all future deployments. Ideally, the necessary configuration should be performed at the Infrastructure provisioning, in which case this daemonset is not required.
+In [build-deploy-tool#395](https://github.com/uselagoon/build-deploy-tool/pull/395) a future release of the build deploy tool will remove the init containers from OpenSearch & Elasticsearch deployments that are used to set the necessary sysctl settings. This daemonset, when enabled in lagoon-remote, runs once on node startup to ensure the correct setting is in place for all future deployments. Ideally, the necessary configuration should be performed at the Infrastructure provisioning, in which case this daemonset is not required.