Change:
[`KubeletConfiguration`](/docs/reference/config-api/kubelet-config.v1beta1/) reference. - Learn more about kubelet configuration merging in the <del> [reference document](/docs/reference/node/kubelet-config-directory-merging.md). </del> <ins> [reference document](/docs/reference/node/kubelet-config-directory-merging). </ins>

Discussion:
The section of the "Set Kubelet Parameters Via A Configuration File" concept contains a broken link that needs to be updated to point to the correct documentation page. The link labeled "reference document" in the following line is broken: Update the link in the markdown file to remove the extension, correcting it to the following format: Where to fix: File to change To contribute to this fix, you could also use the GitHub web interface directly by following this link: /kind bug /priority backlog /language en /triage accepted /good-first-issue
This request has been marked as suitable for new contributors. Please ensure that the issue body includes answers to the following questions: Why are we solving this issue? To address this issue, are there any code changes? If there are code changes, what needs to be done in the code and what places can the assignee treat as reference points? Does this issue have zero to low barrier of entry? How can the assignee reach out to you for help? For more details on the requirements of such an issue, please see and ensure that they are met. If this request no longer meets these requirements, the label can be removed by commenting with the command. <detailsIn response to : ## This is a Bug Report Learn more about kubelet configuration merging in the . ### Additional Information: To contribute to this fix, you could also use the GitHub web interface directly by following this link: /kind bug /priority backlog /language en /triage accepted /good-first-issue Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details
If you've already worked on Kubernetes docs before, please consider leaving this issue for someone new to contribute.
I would like to work on this /assign
- Would you be willing to leave this issue for a new first time contributor to work on?
yes sure! I was confused about taking it on. I'll unassign myself
I would like to work on this as a first time contributor! /assign
if you'd like any advice, join our Slack workspace - - and head to #sig-docs
Thank you appreciate the info. Will reach out if I need!
are you still working on this issue. I would like to work on this issue as my first contribution.
since yesterday?

We're OK with people offering to step in, but: this is typically after weeks of not hearing from someone, not hours. Anyone is welcome to work on this issue and we do have a “no cookie licking” policy to support that. However the best way to make a new contribution would be to look for a different issue. I think a PR to work on would be useful.
Another issue to consider working on (for anyone who's looking for a Good First Issue):
I thank you for the information you provided. I was unaware of that because I am new to open source. I would look for other issues to work on as my first contribution.
Hi Yes, I am still working on this :) Please bare with me folks, will hopefully get this done by mid next week latest but will update here on progress. Thank you!
Hi Team, I have created the PR with solution. Feel free to review and merge :)
Fixed as part of /close
Closing this issue. <detailsIn response to : Fixed as part of Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details