From 47e85920687481a8d1706f2dba86a2e5654cb455 Mon Sep 17 00:00:00 2001
From: klaases <93291761+klaases@users.noreply.github.com>
Date: Wed, 15 Dec 2021 11:45:38 -0800
Subject: [PATCH 1/2] Update triage docs for close with lack of info.

---
 site/content/en/docs/contrib/triage.md | 13 +++++--------
 1 file changed, 5 insertions(+), 8 deletions(-)

diff --git a/site/content/en/docs/contrib/triage.md b/site/content/en/docs/contrib/triage.md
index b0a0d5a757d4..6947f995bbec 100644
--- a/site/content/en/docs/contrib/triage.md
+++ b/site/content/en/docs/contrib/triage.md
@@ -209,18 +209,15 @@ Then: Label with `triage/duplicate` and close the issue.
 
 If an issue hasn't been active for more than four weeks, and the author has been pinged at least once, then the issue can be closed.
 
->Hey @author -- hopefully it's OK if I close this - there wasn't enough information to make it actionable, and some time has already passed. If you are able to provide additional details, you may reopen it at any point by adding /reopen to your comment.
+>Hi @author – is this issue still occurring? Are additional details available? If so, please feel free to re-open the issue by commenting with `/reopen`. This issue will be closed as additional information was unavailable and some time has passed.
 >
->Here is additional information that may be helpful to us:
+>Additional information that may be helpful:
 >
->\* Whether the issue occurs with the latest minikube release
+>* Whether the issue occurs with the latest minikube release
 >
->\* The exact `minikube start` command line used
->
->\* The full output of the `minikube start` command, preferably with `--alsologtostderr -v=3` for extra logging.
->
->\* The full output of `minikube logs`
+>* The exact minikube start command line used
 >
+>* Attach the full output of minikube logs, run `minikube logs --file=logs.txt` to create a log file
 >
 >Thank you for sharing your experience!
 

From b67af5bdab45fd12cace09ded064e04fa92ecdb7 Mon Sep 17 00:00:00 2001
From: klaases <93291761+klaases@users.noreply.github.com>
Date: Wed, 15 Dec 2021 11:48:05 -0800
Subject: [PATCH 2/2] Add escape char for bullet formatting.

---
 site/content/en/docs/contrib/triage.md | 10 +++++-----
 1 file changed, 5 insertions(+), 5 deletions(-)

diff --git a/site/content/en/docs/contrib/triage.md b/site/content/en/docs/contrib/triage.md
index 6947f995bbec..43409061618f 100644
--- a/site/content/en/docs/contrib/triage.md
+++ b/site/content/en/docs/contrib/triage.md
@@ -153,9 +153,9 @@ A sample response to ask for more info:
 
 > I don’t yet have a clear way to replicate this issue. Do you mind adding some additional details. Here is additional information that would be helpful:
 >
-> \*  The exact `minikube start` command line used
+> \* The exact `minikube start` command line used
 >
-> \*  The full output of the `minikube start` command, preferably with `--alsologtostderr -v=4` for extra logging.
+> \* The full output of the `minikube start` command, preferably with `--alsologtostderr -v=4` for extra logging.
 >
 > \* The full output of `minikube logs`
 >
@@ -213,11 +213,11 @@ If an issue hasn't been active for more than four weeks, and the author has been
 >
 >Additional information that may be helpful:
 >
->* Whether the issue occurs with the latest minikube release
+> \* Whether the issue occurs with the latest minikube release
 >
->* The exact minikube start command line used
+> \* The exact minikube start command line used
 >
->* Attach the full output of minikube logs, run `minikube logs --file=logs.txt` to create a log file
+> \* Attach the full output of minikube logs, run `minikube logs --file=logs.txt` to create a log file
 >
 >Thank you for sharing your experience!