[DOCS] Fix links to Stack upgrade version order (#5286) (#5295)

Co-authored-by: James Rodewig <[email protected]>

Author: thbkrkr

docs/release-notes/1.3.0.asciidoc

@@ -9,7 +9,7 @@
 === Breaking changes
 
 * Make ECK IPv6 compatible {pull}3654[#3654] (issues: {issue}2830[#2830], {issue}3649[#3649]) - in an accompanying change `network.publish_host` setting value was switched to DNS name. This might result in non-ready Pods being included in the headless service for Elasticsearch StatefulSets.
-* Enforce a strict upgrade order between stack components {pull}3537[#3537] (issues: {issue}2600[#2600], {issue}3535[#3535]) - ECK will prevent updates that would violate link:https://www.elastic.co/guide/en/elastic-stack/current/upgrading-elastic-stack.html#upgrade-order-elastic-stack[Elastic Stack upgrade process] version constraints. ECK 1.3.0 won't apply any updates to resources that are in violation of those constraints until versions are updated to (at least) the same minors.
+* Enforce a strict upgrade order between stack components {pull}3537[#3537] (issues: {issue}2600[#2600], {issue}3535[#3535]) - ECK will prevent updates that would violate link:https://www.elastic.co/guide/en/elastic-stack/7.17/upgrading-elastic-stack.html#upgrade-order-elastic-stack[Elastic Stack upgrade process] version constraints. ECK 1.3.0 won't apply any updates to resources that are in violation of those constraints until versions are updated to (at least) the same minors.
 * Add set-default-security-context flag to handle runAs user in ES 8.0+ {pull}3342[#3342] (issue: {issue}2791[#2791]) - a default security context is added to Elasticsearch 8.0+ Pods in order to deal with volume filesystem permissions. Can be disabled through operator configuration on environments with restricted security settings (Openshift, for example).
 * Allow init containers modifications {pull}3336[#3336] (issue: {issue}2306[#2306]) - modifications to built-in init containers will be merged with the defaults instead of completely replacing them.