Enhancement By: Renaming 'ReadMes' to 'README' for Improved Clarity.

[Rituraj-13]

Fixes issue - #42979

Made the required changes in README.md file .

1. Updated Localization ReadMes to Localization READMEs.

[linux-foundation-easycla]

The committers listed above are authorized under a signed CLA.

• ✅ login: Rituraj-13 / name: Rituraj Dey (1d9aef1, a2a1ca6, 754094a)

[k8s-ci-robot]

Welcome @Rituraj-13!

It looks like this is your first PR to kubernetes/website 🎉. Please refer to our pull request process documentation to help your PR have a smooth ride to approval.

You will be prompted by a bot to use commands during the review process. Do not be afraid to follow the prompts! It is okay to experiment. Here is the bot commands documentation.

You can also check if kubernetes/website has its own contribution guidelines.

You may want to refer to our testing guide if you run into trouble with your tests not passing.

If you are having difficulty getting your pull request seen, please follow the recommended escalation practices. Also, for tips and tricks in the contribution process you may want to read the Kubernetes contributor cheat sheet. We want to make sure your contribution gets all the attention it needs!

Thank you, and welcome to Kubernetes. 😃

[netlify]

✅ Pull request preview available for checking

Built without sensitive environment variables

Name	Link
🔨 Latest commit	754094a
🔍 Latest deploy log	https://app.netlify.com/sites/kubernetes-io-main-staging/deploys/650134244e5e2a0008405c26
😎 Deploy Preview	https://deploy-preview-42982--kubernetes-io-main-staging.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[aj11anuj]

Localized README.md's seems more appropriate to me than Localization of README.md's

Btw, I'm kind of getting some Hacktoberfest feel now 👀

[Rituraj-13]

Localized README.md's seems more appropriate to me than Localization of README.md's

Btw, I'm kind of getting some Hacktoberfest feel now 👀

I found Localization README.md to be inappropriate, and ReadMes also require correction.

[aj11anuj]

Hello @Rituraj-13 brother, I appreciate your contribution, but maybe you got my words in wrong way. I mean Localized README.md's seems more appropriate to me not Localization ReadMe that was earlier. But Localization README.md's in some way of saying is also Ok-Ok. I don't know, if a minute change like this one will get accepted.

[windsonsea]

/language en

[Rituraj-13]

Hello @Rituraj-13 brother, I appreciate your contribution, but maybe you got my words in wrong way. I mean Localized README.md's seems more appropriate to me not Localization ReadMe that was earlier. But Localization README.md's in some way of saying is also Ok-Ok. I don't know, if a minute change like this one will get accepted.

Thanks bro, for suggestions 👍
I made the required changes, have a look.

[sandipanpanda]

/lgtm
Thanks!

[k8s-ci-robot]

LGTM label has been added.

Git tree hash: 70394f8a8593032a9ebdd7a03bb22a55d41a75d3

[windsonsea]

/lgtm

Need to trigger the CI again:

git reset
git commit --amend --no-edit
git push origin correct-grammar-typos -f

[k8s-ci-robot]

LGTM label has been added.

Git tree hash: 2313c756c55878d75b2f1376ed4e814ef99a9948

[Rituraj-13]

/lgtm

Need to trigger the CI again:

git reset
git commit --amend --no-edit
git push origin correct-grammar-typos -f

Hey @windsonsea ,
I have made the changes, kindly have a look.
Thanks !

[windsonsea]

Seems you run different command series and /lgtm is removed.

/label tide/merge-method-squash

[Rituraj-13]

Seems you run different command series and /lgtm is removed.

/label tide/merge-method-squash

Yeah, for some reason I couldn't make changes with those commands.
So I made a new commit.

So now, do I need to squash those 2 commits and again force push them ?

[windsonsea]

/lgtm

[k8s-ci-robot]

LGTM label has been added.

Git tree hash: 2313c756c55878d75b2f1376ed4e814ef99a9948

[nate-double-u]

I think "Localization" is likely correct in this instance as it is referring to specific localization teams.

"Localization ReadMes" could probably be corrected to "Localization READMEs", and I'd also suggest taking the "``" out of the title.

[nate-double-u]

/area localization

[nate-double-u]

Suggested change

	## Localized READMEs
	## Localization READMEs

[nate-double-u]

Suggested change

	- [Localized READMEs](#localized-readmemds)
	- [Localization READMEs](#localization-readmes)

[nate-double-u]

/lgtm

If someone from the localization team agrees I think this can go in.

Thinking about it more, and not being able to read the majority of the localizations, if the non-english README pages are just a translation of this page, then “Localized README” is probably correct, but if there are region/language specific bits of content or info about the teams doing the localization, then the current “Localization READMEs” is probably correct.

But that’s a lot of thinking for a small change 😅 Probably this should go in, and if it needs to be updated again we should package it with a more robust review/edit of the page.

[k8s-ci-robot]

LGTM label has been added.

Git tree hash: 64456623f6293da0e131a45a3e68f7f6550f1efc

[tengqm]

/label tide/merge-method-squash
/approve

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: tengqm

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [tengqm]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[sftim]

A better title could have been: Reword 'ReadMes' to 'READMEs'