added commits as per suggestions

Author: haripriya9647

content/en/docs/contribute/participate/issue-wrangler.md

@@ -6,27 +6,27 @@ weight: 20
 
 <!-- overview -->
 
-In order to reduce the burden on the [PR Wrangler](/docs/contribute/participate/pr-wrangler), formal approvers, and reviewers, members of SIG Docs take week long shifts [triaging and categorising issues](/docs/contribute/review/for-approvers.md/#triage-and-categorize-issues) for the repository.
+In order to reduce the burden on the [PR Wrangler](/docs/contribute/participate/pr-wranglers),and formal approvers, and reviewers, members of SIG Docs take week long shifts [triaging and categorising issues](/docs/contribute/review/for-approvers.md/#triage-and-categorize-issues) for the repository.
 
 <!-- body -->
 
 ## Duties
 
 Each day in a week-long shift as Issue Wrangler:
 
-- Triage and tag incoming issues daily. See [Triage and categorize issues](https://github.com/kubernetes/website/blob/main/docs/contribute/review/for-approvers/#triage-and-categorize-issues) for guidelines on how SIG Docs uses metadata.
+- Triage and tag incoming issues daily. See [Triage and categorize issues](https://github.com/kubernetes/website/blob/main/content/en/docs/contribute/review/for-approvers.md/#triage-and-categorize-issues) for guidelines on how SIG Docs uses metadata.
 - Identifying whether the issue falls under the support category and assigning a "triage/accepted" status.
-- Assuring the issue is tagged with the appropriate sig/area/kind labels.
+- Ensuring the issue is tagged with the appropriate sig/area/kind labels.
 - Keeping an eye on stale & rotten issues within the kubernetes/website repository.
-- [Issues board](https://github.com/orgs/kubernetes/projects/72/views/1) maintenance would be nice
+- Maintenance of [Issues board](https://github.com/orgs/kubernetes/projects/72/views/1) would be nice
 
 ### Requirements
 
 - Must be an active member of the Kubernetes organization.
-- A minimum of 15 quality contributions to Kubernetes (of which a certain amount should be directed towards kubernetes/website).
+- A minimum of 15 [non-trivial](https://www.kubernetes.dev/docs/guide/pull-requests/#trivial-edits) contributions to Kubernetes (of which a certain amount should be directed towards kubernetes/website).
 - Performing the role in an informal capacity already
 
-### Helpful Prow commands for wranglers
+### Helpful [Prow commands](https://prow.k8s.io/command-help) for wranglers
 
 ```
 # reopen an issue
@@ -37,6 +37,27 @@ Each day in a week-long shift as Issue Wrangler:
 
 # change the state of rotten issues
 /remove-lifecycle rotten
+
+# change the state of stale issues
+/remove-lifecycle stale
+
+# assign sig to an issue
+/sig <sig_name>
+
+# add specific area
+/area <area_name>
+
+# for beginner friendly issues
+/good-first-issue
+
+# issues that needs help
+/help wanted
+
+# tagging issue as support specific
+/kind support
+
+# to accept triaging for an issue
+/triage accepted
 ```
 
 ### When to close Issues
@@ -45,13 +66,11 @@ For an open source project to succeed, good issue management is crucial. But it
 
 Close issues when:
 
-- A similar issue has been reported more than once. It is also advisable to direct the users to the original issue.
+- When a similar issue is reported more than once, you'll first tag it as /triage duplicate; link it to the main issue & then close it. It is also advisable to direct the users to the original issue.
 - It is very difficult to understand and address the issue presented by the author with the information provided.
   However, encourage the user to provide more details or reopen the issue if they can reproduce it later.
 - Having implemented the same functionality elsewhere. One can close this issue and direct user to the appropriate place.
 - Feature requests that are not currently planned or aligned with the project's goals.
-- If the assignee has not responded to comments or feedback in more than two weeks
-  The issue can be assigned to someone who is highly motivated to contribute.
 - In cases where an issue appears to be spam and is clearly unrelated.
 - If the issue is related to an external limitation or dependency and is beyond the control of the project.