[hi] Localize en/docs/contribute/style/page-content-types.md

[bishal7679]

[hi] Localize en/docs/contribute/style/page-content-types.md

Prerequisites:

• If this is your first contribution, visit Contribute to K8s docs for information on how to get started.
• Review a few examples of localized glossary entries to see which content you change and which you live unchanged.

Procedure:

1. Check out dev-1.22-hi.1 and create a working branch called page-content-types.
2. Create a file called content/hi/docs/contribute/style/page-content-types.md.
3. Copy the content of https://github.com/kubernetes/website/blob/main/content/en/docs/contribute/style/page-content-types.md to the file you created.
4. Localize the content.
5. Push your change and create a pull request.

Completing this feature issue fixes part of :-#36455

Note:- Self-assign only one issue at one time

Note:- To know about the preferred localization of common Kubernetes related terms, check this spreadsheet

[bishal7679]

/triage accepted
/language hi
/assign @YashPimple

[k8s-ci-robot]

@bishal7679: GitHub didn't allow me to assign the following users: YashPimple.

Note that only kubernetes members, repo collaborators and people who have commented on this issue/PR can be assigned. Additionally, issues/PRs can only have 10 assignees at the same time.
For more information please see the contributor guide

In response to this:

/triage accepted
/language hi
/assign @YashPimple

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[YashPimple]

/assign

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue or PR as fresh with /remove-lifecycle stale
• Mark this issue or PR as rotten with /lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[vaibhav2107]

/remove-lifecycle stale

[k8s-triage-robot]

This issue has not been updated in over 1 year, and should be re-triaged.

You can:

• Confirm that this issue is still relevant with /triage accepted (org members only)
• Close this issue with /close

For more details on the triage process, see https://www.kubernetes.dev/docs/guide/issue-triage/

/remove-triage accepted

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale