This issue is currently awaiting triage.

SIG Docs takes a lead on issue triage for this website, but any Kubernetes member can accept issues by applying the triage/accepted label.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

/language en
/sig docs

I would like to work on this issue.
/assign

The issue is fixed here.

Hello @AliMehraji, Thank you for flagging this issue. This is a very minor change that does not improve the content quality in any way. I'm afraid there is not enough reason to accept triage for this. IMO, the grammar of the existing text also reads fine. Please can you advise and detail what the change you're suggesting actually improves in the document—readability, UX, grammar, or something else?

@thisisharrsh: Please refrain from working on issues until there is a triage/accepted label. As mentioned above, this doesn't significantly improve the quality of the page or simplify the content. I'll be placing a hold on the PR till we have another Wrangler chime in here or on the PR and till @AliMehraji conveys more details about how this issue improves the quality of our document.

Hello @divya-mohan0209, I mentioned that this is a minor typo, to be considered in future releases to fix.
Just wanted to flag it

another very minor Typo is Per Example in Cluster networking types

Per example, a server or a pod can have multiple IP addresses on its interfaces, but only the IP addresses in node.status.addresses or pod.status.ips are considered for implementing the Kubernetes network model and defining the type of the cluster.

It Should be For Example.

As I mentioned all typoes are very minor, So all can be fixed in one commit/release, @divya-mohan0209 but information about what? fixing typo is not enhancing document quality?
about readability, I think the suggestion of Grammarly is good, it was not easy to understand using because in the sentence I mentioned.

@AliMehraji : Thanks for your questions.

The answer to your question is that the dashes aren't a typo. Per the semantics of English grammar, they are known as Em dashes and serve multiple purposes. You can read more about Em dashes, En dashes, and hyphens in this entry from the Merriam Webster dictionary. In the sentence that you've flagged, it serves the purpose of a comma connecting two phrases together.

Again, regarding fixing quality of documentation/code with trivial edits, we have a policy around that as well and you can read more about it here and docs-specific guidance here. Honestly, none of the suggested changes are really improving the quality of the documentation, except the one listed in this comment and even then, it's a trivial edit.

I'm happy for other reviewers/wranglers of SIG Docs to take a look at this and triage the issue, if they think the changes made will significantly improve the quality of the documentation.

Please refrain from working on issues until there is a triage/accepted label. As mentioned above, this doesn't significantly improve the quality of the page or simplify the content.

I apologise and will keep in mind.
Should I also close the PR about this issue since, in my opinion, there aren't any more significant updates to the page that enhance its quality?