Update doc/update/index.md to fix hyperlink

What does this MR do and why?

Fix hyperlink for version 14.10.0 which was linking to the wrong version 14.1.0.

How to set up and validate locally

1. Visit the Update documentation page.
2. Under section Upgrade paths Click on the hyperlink of version 14.10.0.

MR acceptance checklist

This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.

• I have evaluated the MR acceptance checklist for this MR.

Hey @heiwiper!

Thank you for your contribution to GitLab. Please refer to the contribution flow documentation for a quick overview of the process, and the merge request (MR) guidelines for the detailed process.

When you're ready for a first review, post @gitlab-bot ready. If you know a relevant reviewer(s) (for example, someone that was involved in a related issue), you can also assign them directly with @gitlab-bot ready @user1 @user2.

At any time, if you need help moving the MR forward, feel free to post @gitlab-bot help. Read more on how to get help.

To enable automated checks on your MR, please configure Danger for your fork.

You can comment @gitlab-bot label <label1> <label2> to add labels to your MR. Please see the list of allowed labels in the label command documentation.

This message was generated automatically. You're welcome to improve it.

added Community contribution workflowin dev labels

assigned to @heiwiper

@gitlab-bot ready

added workflowready for review label and removed workflowin dev label

Hi @axil! Please review this documentation merge request.

added documentation twtriaged labels

@mbobin, could you please review this Community contribution or assign other reviewer(s) if you do not have availability or domain expertise?

Please add the workflowin dev label if the merge request needs actions from the author.

requested review from @mbobin

requested review from @axil and removed review request for @mbobin

requested review from @dianalogan and removed review request for @axil

added 1st contribution label

@marcel.amirault I don't really understand why we're linking to random issues in this list...

@rymai Ahh! Those aren't issues, but in-page anchors to sections about each specific release. For example, this is fixing this link: https://docs.gitlab.com/ee/update/index.html#14100

Wow! I was so confused because I looked at the file at https://gitlab.com/gitlab-org/gitlab/-/blob/ab014f7b72216a2e32e3870cda7191adfbd08222/doc/update/index.md to see a "preview", but indeed, this is in GitLab's context, so it links to issues in the project instead of anchors...

added devopssystems groupdistribution typemaintenance labels

approved this merge request

resolved all threads

@heiwiper Aha, nice catch! Thanks a lot for submitting the fix, LGTM!

added Technical Writing label

enabled an automatic merge when the pipeline for 85409649 succeeds

Suggested Reviewers (beta)

The individuals below may be good candidates to participate in the review based on various factors.

You can use slash commands in comments to quickly assign /assign_reviewer @user1.

Suggested Reviewers
@smcgivern, @ashmckenzie, @aqualls, @axil, @splattael

If you do not believe these suggestions are useful, please apply the label Bad Suggested Reviewer. You can also provide feedback for this feature on this issue: https://gitlab.com/gitlab-org/gitlab/-/issues/357923.

Automatically generated by Suggested Reviewers Bot - an experimental ML-based recommendation engine created by ~"group::applied ml".

requested review from @marcel.amirault and removed review request for @dianalogan

	1 Warning
	This merge request does not refer to an existing milestone.

	1 Message
	This merge request adds or changes documentation files. A review from the Technical Writing team before you merge is recommended. Reviews can happen after you merge.

Documentation review

The following files require a review from a technical writer:

• doc/update/index.md

The review does not need to block merging this merge request. See the:

• Metadata for the *.md files that you've changed. The first few lines of each *.md file identify the stage and group most closely associated with your docs change.
• The Technical Writer assigned for that stage and group.
• Documentation workflows for information on when to assign a merge request for review.

Generated by Danger

merged

@heiwiper, how was your code review experience with this merge request? Please tell us how we can continue to iterate and improve:

1. Leave a or a on this comment to describe your experience.
2. Create a new comment starting with @gitlab-bot feedback below, and leave any additional feedback you have for us in the comment.

Have five minutes? Take our survey to give us even more feedback on how GitLab can improve the contributor experience.

Thanks for your help!

mentioned in commit 027aa54b

added workflowstaging-canary label and removed workflowready for review label

added workflowcanary label and removed workflowstaging-canary label

added workflowstaging label and removed workflowcanary label

added workflowproduction label and removed workflowstaging label

changed milestone to %15.2

added workflowpost-deploy-db-staging label and removed workflowproduction label

added workflowpost-deploy-db-production label and removed workflowpost-deploy-db-staging label

added releasedcandidate label

added releasedpublished label and removed releasedcandidate label

added docsimprovement label