Update auto-upgrade-cluster.md

[azarboon]

The following should be clearly stated about the auto upgrade:

"You don't need to stop your workloads, create a new AKS cluster or redeploy your workloads. By enabling auto-upgrade, you can ensure your clusters are up to date seamlessly and don't miss the latest features or patches from AKS and upstream Kubernetes. "

[prmerger-automator[bot]]

@azarboon : Thanks for your contribution! The author(s) have been notified to review your proposed change.

[learn-build-service-prod[bot]]

Learn Build status updates of commit ca78c19:

:white_check_mark: Validation status: passed

File	Status	Preview URL	Details
articles/aks/auto-upgrade-cluster.md	:white_check_mark:Succeeded

For more details, please refer to the build report.

For any questions, please:

• Try searching the learn.microsoft.com contributor guides
• Post your question in the Learn support channel

[Court72]

@Nickomang

Can you review the proposed changes?

When the changes are ready for publication, add a #sign-off comment to signal that the PR is ready for the review team to merge.

#label:"aq-pr-triaged" @MicrosoftDocs/public-repo-pr-review-team

[PMEds28]

@Nickomang

Can you review this old PR and determine whether it needs to be closed or merged?

IMPORTANT: When the changes are ready for publication, add a #sign-off comment to signal that the PR is ready for the review team to merge. If the changes no longer apply, add an explanation and a #please-close comment to close the PR.

@MicrosoftDocs/public-repo-pr-review-team

[Nickomang]

Thanks for the feedback, @azarboon! At this time, we're in the process of migrating this content to a new repository. I'll be closing this pull request for now, but I will follow up over the next few weeks with details on how you can re-open the changes against the new repo. We appreciate the patience as we finalize the migration.

#please-close

[Nickomang]

@azarboon, We’re happy to share that contributions to AKS are once again possible at MicrosoftDocs/azure-aks-docs. We appreciated your patience during this migration.

To re-open your contribution, follow these steps:

1. Fork and clone the new repository MicrosoftDocs/azure-aks-docs.
2. Create a new branch in your fork.
3. Copy the raw markdown for each file touched in your original PR.
4. In your fork’s new branch, paste each markdown file.
5. Commit the changes and open a new PR against the MicrosoftDocs/azure-aks-docs main branch.