Improve LimitRange Documentation.

[T-Lakshmi]

1. Improved overall LimitRange Documentation by fixing format and indentation.
2. Closes: Improvement for k8s.io/docs/concepts/policy/limit-range/ #46899

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign dipesh-rawat for approval. For more information see the Kubernetes Code Review Process.

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

Needs approval from an approver in each of these files:

• content/en/docs/OWNERS

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

[netlify]

✅ Pull request preview available for checking

Built without sensitive environment variables

Name	Link
🔨 Latest commit	ae1b39d
🔍 Latest deploy log	https://app.netlify.com/sites/kubernetes-io-main-staging/deploys/6744135b3787230008dc8396
😎 Deploy Preview	https://deploy-preview-48766--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.

[T-Lakshmi]

/sig node

[T-Lakshmi]

Preview page: https://deploy-preview-48766--kubernetes-io-main-staging.netlify.app/docs/concepts/policy/limit-range/

[tengqm]

I'd do this:

Suggested change

	- First, the LimitRange admission controller applies default request and limit values for all Pods (and their containers) that do not set compute resource requirements.
	- Second, the LimitRange tracks usage to ensure it does not exceed resource minimum, maximum and ratio defined in any LimitRange present in the namespace.
	- If you attempt to create or update an object (Pod or PersistentVolumeClaim) that violates a LimitRange constraint,
	your request to the API server will fail with an HTTP status code `403 Forbidden` and a message explaining the constraint that has been violated.
	- First, the LimitRange admission controller applies default request and limit values
	for all Pods (and their containers) that do not set compute resource requirements.
	- Second, the LimitRange tracks usage to ensure it does not exceed resource minimum,
	maximum and ratio defined in any LimitRange present in the namespace.
	- If you attempt to create or update an object (Pod or PersistentVolumeClaim) that
	violates a LimitRange constraint, your request to the API server will fail with
	an HTTP status code `403 Forbidden` and a message explaining the constraint that
	has been violated.

[T-Lakshmi]

@tengqm,
Thanks for the sharing your opinion. I updated the same.
PTAL!

[tengqm]

Failed to see the revision in your new commit.
The point is that we encourage indenting all lines under a bulletin (not just the first
line), so that the whole list is more readable in Markdown source.

[T-Lakshmi]

Understood! let me update it.