Change:
options. <del> <!-- discussion --> ## What's next {#whats-next} * Verify that your cluster is running properly with [Sonobuoy](https://github.com/heptio/sonobuoy) * <a id="lifecycle" />See [Upgrading kubeadm clusters](/docs/tasks/administer-cluster/kubeadm/kubeadm-upgrade/) for details about upgrading your cluster using `kubeadm`. * Learn about advanced `kubeadm` usage in the [kubeadm reference documentation](/docs/reference/setup-tools/kubeadm/) * Learn more about Kubernetes [concepts](/docs/concepts/) and [`kubectl`](/docs/reference/kubectl/). * See the [Cluster Networking](/docs/concepts/cluster-administration/networking/) page for a bigger list of Pod network add-ons. * <a id="other-addons" />See the [list of add-ons](/docs/concepts/cluster-administration/addons/) to explore other add-ons, including tools for logging, monitoring, network policy, visualization &amp; control of your Kubernetes cluster. * Configure how your cluster handles logs for cluster events and from applications running in Pods. See [Logging Architecture](/docs/concepts/cluster-administration/logging/) for an overview of what is involved. ### Feedback {#feedback} * For bugs, visit the [kubeadm GitHub issue tracker](https://github.com/kubernetes/kubeadm/issues) * For support, visit the [#kubeadm](https://kubernetes.slack.com/messages/kubeadm/) Slack channel * General SIG Cluster Lifecycle development Slack channel: [#sig-cluster-lifecycle](https://kubernetes.slack.com/messages/sig-cluster-lifecycle/) * SIG Cluster Lifecycle [SIG information](https://github.com/kubernetes/community/tree/master/sig-cluster-lifecycle#readme) * SIG Cluster Lifecycle mailing list: [kubernetes-sig-cluster-lifecycle](https://groups.google.com/forum/#!forum/kubernetes-sig-cluster-lifecycle) </del> ## Version skew policy {#version-skew-policy} While kubeadm allows version skew against some components that it manages, it is recommended that you

Discussion:
This is a Bug Report Problem: 'What's next' and 'Feedback' heading of this page is in the middle of page that should be at the end of the page. Proposed Solution: Cut-paste content shown in 1st picture and paste it after the heading 'Troubleshooting' (Refer 3rd picture) Page to Update: ! ! !
/sig docs /priority backlog /triage accepted /good-first-issue /help /language en
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 : /sig docs /priority backlog /triage accepted /good-first-issue /help /language en 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
/assign
this issue is already assigned to Prashant and he has already raised a PR for it which is under review process. There are plenty of other issues available here, try your hands on them :)
Yeah, I checked that's why i deleted the comment